- name
- generation-maker
- version
- 1.0.0
- displayName
- Generation Maker — Generate Videos from Prompts
- description
- >
- metadata
- {"openclaw": {"emoji": "🎬", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "greeting_v2"}}
Getting Started
Got text prompts or clips to work with? Send it over and tell me what you need — I'll take care of the AI video generation.
Try saying:
- "generate a short text prompt describing a product demo scene into a 1080p MP4"
- "generate a 30-second video from my script about a new sneaker launch"
- "generating videos from text prompts or reference media for content creators and marketers"
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: <uuid>. 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.
Generation Maker — Generate Videos from Prompts
This tool takes your text prompts or clips and runs AI video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.
Say you have a short text prompt describing a product demo scene and want to generate a 30-second video from my script about a new sneaker launch — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.
Tip: shorter and more specific prompts tend to produce more accurate results.
Matching Input to Actions
User prompts referencing generation 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:
- Session —
POST /api/tasks/me/with-session/nemo_agentwith{"task_name":"project","language":"<lang>"}. Gives you asession_id. - Chat (SSE) —
POST /run_ssewithsession_idand your message innew_message.parts[0].text. SetAccept: text/event-stream. Up to 15 min. - Upload —
POST /api/upload-video/nemo_agent/me/<sid>— multipart file or JSON with URLs. - Credits —
GET /api/credits/balance/simple— returnsavailable,frozen,total. - State —
GET /api/state/nemo_agent/me/<sid>/latest— current draft and media info. - Export —
POST /api/render/proxy/lambdawith render ID and draft JSON. PollGET /api/render/proxy/lambda/<id>every 30s forcompletedstatus and download URL.
Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.
Headers are derived from this file's YAML frontmatter. X-Skill-Source is generation-maker, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).
Every API call needs Authorization: Bearer <NEMO_TOKEN> 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:
- "click" or "点击" → execute the action via the relevant endpoint
- "open" or "打开" → query session state to get the data
- "drag/drop" or "拖拽" → send the edit command through SSE
- "preview in timeline" → show a text summary of current tracks
- "Export" or "导出" → run the export workflow
Reading the SSE Stream
Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.
About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.
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=<id> (get <id> 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 "generate a 30-second video from my script about a new sneaker launch" — concrete instructions get better results.
Max file size is 500MB. Stick to MP4, MOV, WebM, JPG for the smoothest experience.
Export as MP4 for widest compatibility.
Common Workflows
Quick edit: Upload → "generate a 30-second video from my script about a new sneaker launch" → 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.