Merger Free

combine multiple video clips into seamlessly joined MP4 with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for combin...

Security Scan

This skill's behavior (upload clips to a remote rendering service using a NEMO_TOKEN) matches its description and requirements, but it uploads your media and manages short-lived tokens on an external backend so you should confirm the service and privacy before use.

Purpose & Capability

The name/description (join multiple clips into one MP4) matches the instructions: all heavy work is done by a remote API and the skill only requires a NEMO_TOKEN to authenticate. Requiring a single service token is appropriate for a cloud-based render service.

Instruction Scope

The SKILL.md is explicit about creating sessions, uploading files, starting renders, and streaming SSE responses to the user. It also contains logic to generate an anonymous token if NEMO_TOKEN is missing and to detect install paths for an X-Skill-Platform header. Those actions are consistent with a cloud render flow, but they do mean user media and generated tokens are transmitted to an external endpoint (https://mega-api-prod.nemovideo.ai).

Install Mechanism

No install spec or code is included (instruction-only). Nothing will be written to disk or downloaded at install time by the skill itself, which lowers installation risk.

Credentials

The only declared credential is NEMO_TOKEN, which is proportional for a remote service. However the skill metadata also references a config path (~/.config/nemovideo/) and uses install-path detection for headers — the registry summary earlier reported no required config paths, so there is a minor metadata inconsistency worth checking. Be aware that the token (anonymous or provided) grants the backend access to uploaded files and job state.

Persistence & Privilege

The skill does not request always:true and does not request elevated privileges. It describes maintaining a session token for its own operations but does not indicate modifying other skills or system-wide settings.

Assessment

This skill uploads your video files to an external rendering service and either uses a NEMO_TOKEN you provide or will obtain a short-lived anonymous token on your behalf. Before installing: (1) verify the service domain/owner (mega-api-prod.nemovideo.ai) and privacy/retention policies; (2) avoid uploading sensitive or private videos unless you trust the service; (3) if you supply your own NEMO_TOKEN, understand it grants the skill access to your account/credits—revoke it if you stop using the skill; (4) note the metadata mentions a config path (~/.config/nemovideo/) — check whether the skill actually writes to or reads that location and whether you are comfortable with that; (5) test first with small, non-sensitive clips. If you need higher assurance, ask the publisher for an official homepage or source repository before use.

Getting Started

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

Try saying:

• "combine three separate MP4 clips from a travel shoot into a 1080p MP4"
• "join these clips into one continuous video without any merge artifacts or transitions"
• "combining multiple video clips into one file without watermarks or forced transitions for content creators"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Merger Free — Join Clips Into One Video

Send me your multiple video clips and describe the result you want. The AI clip joining runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload three separate MP4 clips from a travel shoot, type "join these clips into one continuous video without any merge artifacts or transitions", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: keep individual clips under 200MB each for the fastest processing.

Matching Input to Actions

User prompts referencing merger free, 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":"<lang>"}. 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/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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 merger-free, 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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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.

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

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 → "join these clips into one continuous video without any merge artifacts or 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "join these clips into one continuous video without any merge artifacts or 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.