Free Generation Maker
by @mory128
generate text prompts into AI generated videos with this skill. Works with MP4, MOV, WebM, GIF files up to 500MB. content creators use it for generating vide...
clawhub install free-generation-makerπ About This Skill
name: free-generation-maker version: "1.0.0" displayName: "Free Generation Maker β Generate Videos from Text Prompts" description: > generate text prompts into AI generated videos with this skill. Works with MP4, MOV, WebM, GIF files up to 500MB. content creators use it for generating videos from text prompts without filming β processing takes 1-2 minutes on cloud GPUs and you get 1080p MP4 files. metadata: {"openclaw": {"emoji": "π¬", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "short_prompts"}}
Getting Started
> Share your text prompts and I'll get started on AI video generation. Or just tell me what you're thinking.
Try saying:
First-Time Connection
When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").
Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.
1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN β 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer , Content-Type: application/json, and body {"task_name":"project","language":". Store the returned session_id for all subsequent requests.
Keep setup communication brief. Don't display raw API responses or token values to the user.
Free Generation Maker β Generate Videos from Text Prompts
Drop your text prompts in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs β you don't need anything installed locally.
Here's a typical use: you send a a short text description of a product launch scene, ask for generate a 30-second video from my script about a coffee brand, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.
One thing worth knowing β shorter, more specific prompts produce more accurate results.
Matching Input to Actions
User prompts referencing free 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.
Base URL: https://mega-api-prod.nemovideo.ai
| Endpoint | Method | Purpose |
|----------|--------|---------|
| /api/tasks/me/with-session/nemo_agent | POST | Start a new editing session. Body: {"task_name":"project","language":". Returns session_id. |
| /run_sse | POST | Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min. |
| /api/upload-video/nemo_agent/me/ | POST | Upload a file (multipart) or URL. |
| /api/credits/balance/simple | GET | Check remaining credits (available, frozen, total). |
| /api/state/nemo_agent/me/ | GET | Fetch current timeline state (draft, video_infos, generated_media). |
| /api/render/proxy/lambda | POST | Start export. Body: {"id":"render_. Poll status every 30s. |
Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.
Three attribution headers are required on every request and must match this file's frontmatter:
| Header | Value |
|--------|-------|
| X-Skill-Source | free-generation-maker |
| X-Skill-Version | frontmatter version |
| X-Skill-Platform | auto-detect: clawhub / cursor / unknown from install path |
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.
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 |
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.
Translating GUI Instructions
The backend responds as if there's a visual interface. Map its instructions to API calls:
Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.
Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)
Common Workflows
Quick edit: Upload β "generate a 30-second video from my script about a coffee brand" β 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.
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 coffee brand" β concrete instructions get better results.
Max file size is 500MB. Stick to MP4, MOV, WebM, GIF for the smoothest experience.
Export as MP4 for widest compatibility.
π‘ Examples
> Share your text prompts and I'll get started on AI video generation. Or just tell me what you're thinking.
Try saying:
First-Time Connection
When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").
Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.
1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN β 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer , Content-Type: application/json, and body {"task_name":"project","language":". Store the returned session_id for all subsequent requests.
Keep setup communication brief. Don't display raw API responses or token values to the user.
Free Generation Maker β Generate Videos from Text Prompts
Drop your text prompts in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs β you don't need anything installed locally.
Here's a typical use: you send a a short text description of a product launch scene, ask for generate a 30-second video from my script about a coffee brand, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.
One thing worth knowing β shorter, more specific prompts produce more accurate results.