Merge Video
by @mory128
Get merged MP4 video ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "combine...
clawhub install merge-videoπ About This Skill
name: merge-video version: "1.0.0" displayName: "Merge Video β Combine Clips Into One Video" description: > Get merged MP4 video ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "combine these three clips into one continuous video with smooth transitions", and download 1080p MP4 when it's done. Built for content creators who move fast and want to join multiple clips quickly without complex editing software. metadata: {"openclaw": {"emoji": "π¬", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "greeting_v2"}}
Getting Started
> Ready when you are. Drop your video clips here or describe what you want to make.
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.
Merge Video β Combine Clips Into One Video
This tool takes your video clips and runs AI video merging through a cloud rendering pipeline. You upload, describe what you want, and download the result.
Say you have three separate 30-second MP4 clips and want to combine these three clips into one continuous video with smooth transitions β the backend processes it in about 30-60 seconds and hands you a 1080p MP4.
Tip: keeping individual clips under 2 minutes each speeds up the merge process.
Matching Input to Actions
User prompts referencing merge video, 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.
Skill attribution β read from this file's YAML frontmatter at runtime:
X-Skill-Source: merge-videoX-Skill-Version: from frontmatter versionX-Skill-Platform: detect from install path (~/.clawhub/ β clawhub, ~/.cursor/skills/ β cursor, else unknown)Include Authorization: Bearer and all attribution headers on every request β omitting them triggers a 402 on export.
API base: https://mega-api-prod.nemovideo.ai
Create session: POST /api/tasks/me/with-session/nemo_agent β body {"task_name":"project","language":" β returns task_id, session_id.
Send message (SSE): POST /run_sse β body {"app_name":"nemo_agent","user_id":"me","session_id":" with Accept: text/event-stream. Max timeout: 15 minutes.
Upload: POST /api/upload-video/nemo_agent/me/ β file: multipart -F "files=@/path", or URL: {"urls":["
Credits: GET /api/credits/balance/simple β returns available, frozen, total
Session state: GET /api/state/nemo_agent/me/ β key fields: data.state.draft, data.state.video_infos, data.state.generated_media
Export (free, no credits): POST /api/render/proxy/lambda β body {"id":"render_. Poll GET /api/render/proxy/lambda/ every 30s until status = completed. Download URL at output.url.
Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.
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 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)
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 three clips into one continuous video with smooth transitions" β concrete instructions get better results.
Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.
Export as MP4 for widest compatibility across platforms and devices.
Common Workflows
Quick edit: Upload β "combine these three clips into one continuous video with smooth transitions" β 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
> Ready when you are. Drop your video clips here or describe what you want to make.
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.
Merge Video β Combine Clips Into One Video
This tool takes your video clips and runs AI video merging through a cloud rendering pipeline. You upload, describe what you want, and download the result.
Say you have three separate 30-second MP4 clips and want to combine these three clips into one continuous video with smooth transitions β the backend processes it in about 30-60 seconds and hands you a 1080p MP4.
Tip: keeping individual clips under 2 minutes each speeds up the merge process.