Merge Video

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...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based video-merge service: it needs a NEMO_TOKEN (or will obtain an anonymous one), uploads media to nemovideo.ai, and has no install step or unrelated credential requests.

Purpose & Capability

Name/description (merge videos) match the runtime instructions and required credential (NEMO_TOKEN). No unrelated binaries or unrelated service credentials are requested.

Instruction Scope

Instructions direct the agent to call nemovideo.ai APIs (auth, session, upload, SSE, render polling) and to include attribution headers read from this skill's YAML frontmatter. It also asks the agent to detect install path (~/.clawhub, ~/.cursor) to set X-Skill-Platform — this requires limited filesystem checks but is scoped to determining runtime context. The skill does not instruct reading arbitrary user files beyond the user-supplied media to upload.

Install Mechanism

No install spec and no code files (instruction-only). This is low-risk: nothing is downloaded or written by an installer.

Credentials

Only one credential is required (NEMO_TOKEN), which is appropriate for a cloud API. The skill provides a fallback anonymous-token flow (POST to nemovideo.ai) if no token is present. Minor inconsistency: the skill frontmatter metadata references a config path (~/.config/nemovideo/) whereas the registry metadata listed 'Required config paths: none' — this appears informational but should be checked if you want the skill to read or persist local config.

Persistence & Privilege

always is false and the skill is user-invocable. It asks to save session_id for ongoing interactions, which is normal for session-driven cloud APIs and does not request elevated or permanent platform privileges.

Assessment

This skill implements a cloud-render workflow: it will upload any video files you give it to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (or obtain a temporary anonymous token) to authenticate. Before installing or using it: (1) confirm you are comfortable uploading your media to an external service and check that service's privacy/retention policy; (2) if you have a paid/enterprise NEMO_TOKEN, supply it instead of using the anonymous flow to avoid accidental credit use; (3) note the skill may perform small filesystem checks to determine its install path and will store a session_id for active jobs — review any local config if you prefer not to persist session state; (4) the lack of an install step means no code will be written to disk by the skill itself. If you need stronger guarantees, ask the provider for a privacy/data-retention statement or use locally-run video tools instead.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "combine three separate 30-second MP4 clips into a 1080p MP4"
• "combine these three clips into one continuous video with smooth transitions"
• "combining multiple video clips into one seamless video for content creators"

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.

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-video
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> 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":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — 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_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> 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:

• "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

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 normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Tips 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.