Slideshow Automation
by @francemichaell-15
Turn ten vacation photos in JPG format into 1080p automated slideshow video just by typing what you need. Whether it's turning photo collections into polishe...
clawhub install slideshow-automationπ About This Skill
name: slideshow-automation version: "1.0.0" displayName: "Slideshow Automation β Convert Photos Into Slideshow Videos" description: > Turn ten vacation photos in JPG format into 1080p automated slideshow video just by typing what you need. Whether it's turning photo collections into polished slideshow videos or quick social content, drop your images or clips and describe the result you want. No timeline dragging, no export settings β 30-60 seconds from upload to download. metadata: {"openclaw": {"emoji": "πΌοΈ", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "short_prompts"}}
Getting Started
> Share your images or clips and I'll get started on automated slideshow creation. Or just tell me what you're thinking.
Try saying:
Quick Start Setup
This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").
Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:
https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id headerdata.token from the response β this is your NEMO_TOKEN (100 free credits, 7-day expiry)Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.
Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.
Slideshow Automation β Convert Photos Into Slideshow Videos
Send me your images or clips and describe the result you want. The automated slideshow creation runs on remote GPU nodes β nothing to install on your machine.
A quick example: upload ten vacation photos in JPG format, type "turn my photos into a slideshow with transitions and background music", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.
Worth noting: keeping image count under 20 speeds up processing noticeably.
Matching Input to Actions
User prompts referencing slideshow automation, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.
| User says... | Action | Skip SSE? | |-------------|--------|----------| | "export" / "ε―ΌεΊ" / "download" / "send me the video" | β Β§3.5 Export | β | | "credits" / "η§―ε" / "balance" / "δ½ι’" | β Β§3.3 Credits | β | | "status" / "ηΆζ" / "show tracks" | β Β§3.4 State | β | | "upload" / "δΈδΌ " / user sends file | β Β§3.2 Upload | β | | Everything else (generate, edit, add BGMβ¦) | β Β§3.1 SSE | β |
Cloud Render Pipeline Details
Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.
All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:
1. Session β POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":". Gives you a session_id.
2. Chat (SSE) β POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload β POST /api/upload-video/nemo_agent/me/ β multipart file or JSON with URLs.
4. Credits β GET /api/credits/balance/simple β returns available, frozen, total.
5. State β GET /api/state/nemo_agent/me/ β current draft and media info.
6. Export β POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/ every 30s for completed status and download URL.
Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.
Skill attribution β read from this file's YAML frontmatter at runtime:
X-Skill-Source: slideshow-automationX-Skill-Version: from frontmatter versionX-Skill-Platform: detect from install path (~/.clawhub/ β clawhub, ~/.cursor/skills/ β cursor, else unknown)All requests must include: Authorization: Bearer , X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.
Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.
Example timeline summary:
Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)
Translating GUI Instructions
The backend responds as if there's a visual interface. Map its instructions to API calls:
SSE Event Handling
| Event | Action |
|-------|--------|
| Text response | Apply GUI translation (Β§4), present to user |
| Tool call/result | Process internally, don't forward |
| heartbeat / empty data: | Keep waiting. Every 2 min: "β³ Still working..." |
| Stream closes | Process final response |
~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.
Error Handling
| Code | Meaning | Action |
|------|---------|--------|
| 0 | Success | Continue |
| 1001 | Bad/expired token | Re-auth via anonymous-token (tokens expire after 7 days) |
| 1002 | Session not found | New session Β§3.0 |
| 2001 | No credits | Anonymous: show registration URL with ?bind= (get from create-session or state response when needed). Registered: "Top up credits in your account" |
| 4001 | Unsupported file | Show supported formats |
| 4002 | File too large | Suggest compress/trim |
| 400 | Missing X-Client-Id | Generate Client-Id and retry (see Β§1) |
| 402 | Free plan export blocked | Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export." |
| 429 | Rate limit (1 token/client/7 days) | Retry in 30s once |
Tips and Tricks
The backend processes faster when you're specific. Instead of "make it look better", try "turn my photos into a slideshow with transitions and background music" β concrete instructions get better results.
Max file size is 200MB. Stick to JPG, PNG, MP4, MOV for the smoothest experience.
Export as MP4 for widest compatibility across social platforms.
Common Workflows
Quick edit: Upload β "turn my photos into a slideshow with transitions and background music" β Download MP4. Takes 30-60 seconds for a 30-second clip.
Batch style: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.
Iterative: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.
π‘ Examples
> Share your images or clips and I'll get started on automated slideshow creation. Or just tell me what you're thinking.
Try saying:
Quick Start Setup
This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").
Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:
https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id headerdata.token from the response β this is your NEMO_TOKEN (100 free credits, 7-day expiry)Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.
Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.
Slideshow Automation β Convert Photos Into Slideshow Videos
Send me your images or clips and describe the result you want. The automated slideshow creation runs on remote GPU nodes β nothing to install on your machine.
A quick example: upload ten vacation photos in JPG format, type "turn my photos into a slideshow with transitions and background music", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.
Worth noting: keeping image count under 20 speeds up processing noticeably.