Video Merger Free

Skip the learning curve of professional editing software. Describe what you want — merge these clips into one continuous video with smooth transitions — and...

Security Scan

The skill's requirements and runtime instructions are coherent for a cloud-based video-merging service, but it talks to an external API of unknown provenance and will upload user files and obtain/hold an anonymous token if one isn't provided.

Purpose & Capability

Name/description (cloud video merging) match the declared requirement for a NEMO_TOKEN and the SKILL.md's API calls for session creation, upload, and render. There are no unrelated environment variables or binaries requested.

Instruction Scope

Instructions focus on session creation, SSE messaging, uploads, and export polling — all expected. They also instruct reading the skill's YAML frontmatter and detecting install paths (~/.clawhub, ~/.cursor/skills/) to set an X-Skill-Platform header; this requires probing user home paths. That filesystem probing is unnecessary for core functionality but is limited in scope.

Install Mechanism

No install spec or code files — instruction-only skill. Nothing will be written to disk by an installer as part of a package install step.

Credentials

Only NEMO_TOKEN is declared (primary credential), which fits a cloud API client. The instructions also include an anonymous-token flow (POST to /api/auth/anonymous-token) if NEMO_TOKEN is absent; that is consistent with providing ephemeral access but means the skill can obtain credentials on its own. A config path (~/.config/nemovideo/) is referenced in metadata; the SKILL.md itself does not clearly require reading/writing that path but may do so for persistent tokens.

Persistence & Privilege

always is false and there is no installer. The skill can be invoked autonomously (platform default) and will make outbound network calls to the specified API; this is expected for a cloud processing skill and does not itself indicate excessive privilege.

Assessment

This skill will upload any video files you give it to https://mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (you can provide one or it will obtain an anonymous token that expires in ~7 days). Before installing/using: (1) verify you trust the mega-api-prod.nemovideo.ai service and its privacy/terms for any sensitive video content, (2) be aware the skill may probe a few home-directory paths to set an attribution header (not full system access, but it reads those paths), (3) avoid uploading sensitive personal data unless you accept that it will be transmitted to that third party, and (4) if you prefer, provide your own NEMO_TOKEN or decline to use the skill. If you want higher assurance, ask the publisher for a privacy/security statement or a canonical homepage/source before proceeding.

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"
• "merge these clips into one continuous video with smooth transitions"
• "combining multiple video clips into one seamless file 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.

Video Merger Free — Merge Clips Into One Video

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

Here's a typical use: you send a three separate 30-second MP4 clips, ask for merge these clips into one continuous video with smooth transitions, 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 clips in order before uploading to avoid manual reordering.

Matching Input to Actions

User prompts referencing video 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.

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-merger-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "merge these 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.

Common Workflows

Quick edit: Upload → "merge these 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.