Free Video Merger

Turn three separate MP4 clips from a vacation into 1080p merged MP4 video just by typing what you need. Whether it's joining multiple video clips into a sing...

Security Scan

The skill's code-free instructions, required token, and API endpoints are coherent with a cloud-based video-merge service, but users should be aware that their video files and a short-lived anonymous token are uploaded to an external backend and verify privacy/retention policies before using it.

Purpose & Capability

The name and description match the actions described in SKILL.md: uploading clips, creating a render session, and exporting a merged MP4 via the nemovideo.ai endpoints. Requesting a service token (NEMO_TOKEN) is appropriate for a cloud render service.

Instruction Scope

Instructions tell the agent to upload user-provided video files and interact with multiple backend endpoints (auth, session, upload, SSE, export). This is expected for cloud rendering but means user media is transmitted off-device; the skill also instructs the agent to auto-request an anonymous token if none is provided and to hide raw API responses/tokens from users, which is operationally reasonable but worth surfacing to users (it reduces transparency).

Install Mechanism

No install spec or code is present; the skill is instruction-only and performs network calls at runtime. This is the lowest install risk (nothing is written to disk by an installer).

Credentials

Only NEMO_TOKEN is required, which aligns with the declared primary credential. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry 'Required config paths' field is empty — a metadata mismatch but not itself dangerous. The skill will also create a short-lived anonymous token if none is present.

Persistence & Privilege

always:false and no install behavior are appropriate. The skill asks to store a session_id for subsequent API calls (normal session state); it does not request system-wide configuration changes or other skills' credentials.

Assessment

This skill uploads your video files to an external service (mega-api-prod.nemovideo.ai) and uses or creates a short-lived NEMO_TOKEN (anonymous tokens have ~100 free credits and expire in ~7 days). Before installing or using it: confirm you are comfortable with your videos leaving your device, check the provider's privacy/retention policy, and prefer supplying your own token if you want control over access. Note the SKILL.md asks the agent to hide raw API responses/tokens from users and includes a config path in its frontmatter that isn't declared elsewhere — this metadata mismatch is not critical but worth confirming with the skill author. If you handle sensitive footage, test with non-sensitive files or use a disposable/limited token.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the video merging.

Try saying:

• "combine three separate MP4 clips from a vacation into a 1080p MP4"
• "merge all three clips into one continuous video in order"
• "joining multiple video clips into a single file for content creators"

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 <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. 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 Video Merger — Combine Clips Into One Video

Drop your video clips in the chat and tell me what you need. I'll handle the video merging on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a three separate MP4 clips from a vacation, ask for merge all three clips into one continuous video in order, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — arrange your clips in the correct order before uploading to save re-processing time.

Matching Input to Actions

User prompts referencing free video merger, 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":"<lang>"}. 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/<sid> — 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/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status 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 free-video-merger, 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 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)

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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

Common Workflows

Quick edit: Upload → "merge all three clips into one continuous video in order" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "merge all three clips into one continuous video in order" — 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.