Video Maker
by @mory128
Get polished MP4 videos ready to post, without touching a single slider. Upload your video clips or images (MP4, MOV, AVI, WebM, up to 500MB), say something...
clawhub install video-makerπ About This Skill
name: video-maker version: "1.0.0" displayName: "Video Maker β Create and Export Finished Videos" description: > Get polished MP4 videos ready to post, without touching a single slider. Upload your video clips or images (MP4, MOV, AVI, WebM, up to 500MB), say something like "combine these clips into a 60-second promo video with text overlays and transitions", and download 1080p MP4 when it's done. Built for content creators and marketers who move fast and want to produce finished videos quickly without learning complex editing software. metadata: {"openclaw": {"emoji": "π¬", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "short_prompts"}}
Getting Started
> Share your video clips or images and I'll get started on AI video creation. Or just tell me what you're thinking.
Try saying:
Automatic Setup
On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".
Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.
Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: . The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).
Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.
Confirm to the user you're connected and ready. Don't print tokens or raw JSON.
Video Maker β Create and Export Finished Videos
Send me your video clips or images and describe the result you want. The AI video creation runs on remote GPU nodes β nothing to install on your machine.
A quick example: upload five product photos and a background music file, type "combine these clips into a 60-second promo video with text overlays and transitions", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.
Worth noting: shorter source clips under 2 minutes process significantly faster and give the AI more precise control.
Matching Input to Actions
User prompts referencing video maker, 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: video-makerX-Skill-Version: from frontmatter versionX-Skill-Platform: detect from install path (~/.clawhub/ β clawhub, ~/.cursor/skills/ β cursor, else unknown)Every API call needs Authorization: Bearer plus the three attribution headers above. If any header is missing, exports return 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 Codes
0 β success, continue normally1001 β token expired or invalid; re-acquire via /api/auth/anonymous-token1002 β session not found; create a new one2001 β out of credits; anonymous users get a registration link with ?bind=, registered users top up4001 β unsupported file type; show accepted formats4002 β file too large; suggest compressing or trimming400 β missing X-Client-Id; generate one and retry402 β free plan export blocked; not a credit issue, subscription tier429 β rate limited; wait 30s and retry onceTips and Tricks
The backend processes faster when you're specific. Instead of "make it look better", try "combine these clips into a 60-second promo video with text overlays and transitions" β concrete instructions get better results.
Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.
Export as MP4 with H.264 codec for the widest compatibility across platforms and devices.
Common Workflows
Quick edit: Upload β "combine these clips into a 60-second promo video with text overlays and transitions" β Download MP4. Takes 1-2 minutes 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 video clips or images and I'll get started on AI video creation. Or just tell me what you're thinking.
Try saying:
Automatic Setup
On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".
Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.
Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: . The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).
Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.
Confirm to the user you're connected and ready. Don't print tokens or raw JSON.
Video Maker β Create and Export Finished Videos
Send me your video clips or images and describe the result you want. The AI video creation runs on remote GPU nodes β nothing to install on your machine.
A quick example: upload five product photos and a background music file, type "combine these clips into a 60-second promo video with text overlays and transitions", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.
Worth noting: shorter source clips under 2 minutes process significantly faster and give the AI more precise control.