Free Video Music

add video clips into music-backed videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for adding royalty-free b...

Security Scan

The skill's declared purpose (adding royalty‑free music to videos) matches the actions it instructs (uploading media and calling a cloud render API), but there are a few small inconsistencies and privacy-risk details you should understand before installing.

Purpose & Capability

The skill is an instruction-only integration with a cloud rendering API for adding music to videos. Requesting a single API token (NEMO_TOKEN) and providing endpoints for upload, session, SSE, and export are coherent with the stated purpose.

Instruction Scope

Runtime instructions are focused on session creation, SSE-based editing, uploads, and export polling — all appropriate for a cloud video render service. It explicitly instructs uploading user video files to the third‑party endpoint (expected for this feature) and to avoid printing tokens/raw JSON. It also tells the agent to derive an X-Skill-Platform value from local install paths (e.g., ~/.clawhub/), which would require the agent to inspect its filesystem or environment; that is not strictly necessary for core functionality and is an unexpected data point to include in requests.

Install Mechanism

There is no install spec and no code files (instruction-only), so nothing will be written to disk by a package installer. This is the lowest‑risk install pattern.

Credentials

The skill requires a single credential NEMO_TOKEN (declared as primary), which matches the API usage. It also describes an anonymous-token flow (POST to the service to obtain a temporary token) — reasonable but means the skill will create/use credentials on your behalf. The SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) even though the registry metadata summary above listed no required config paths; that inconsistency is minor but worth noting.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It is user-invokable and allows autonomous invocation (the platform default) but does not ask to modify other skill configs or persist beyond its own session state.

What to consider before installing

This skill appears to do what it claims (upload your videos to a third‑party cloud service and return a rendered MP4), but before installing consider: 1) Uploads: your video/audio files are sent to https://mega-api-prod.nemovideo.ai — do not upload sensitive or private content unless you trust that domain and have reviewed its privacy/terms. 2) Credentials: it requires/stores a NEMO_TOKEN (and can mint an anonymous token for you); keep that token private and prefer short‑lived/anonymous tokens if possible. 3) Metadata inconsistency: the SKILL.md references a local config path and instructs deriving an X-Skill-Platform value from install paths — this may cause the agent to inspect local paths/environment; be cautious about filesystem access. 4) No install code reduces the risk of arbitrary code execution, but networked file uploads and token management are the primary risks. If you plan to use it, verify the service domain/owner, review its privacy policy, and avoid uploading sensitive media.

Getting Started

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

Try saying:

• "add a 60-second travel montage clip into a 1080p MP4"
• "add free background music that matches the mood of my video"
• "adding royalty-free background music to videos 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.

Free Video Music — Add Music to Videos Free

This tool takes your video clips and runs AI music addition through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second travel montage clip and want to add free background music that matches the mood of my video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips let you preview multiple music tracks faster before committing.

Matching Input to Actions

User prompts referencing free video music, 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-music, 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).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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)

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

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 → "add free background music that matches the mood of my video" → 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 "add free background music that matches the mood of my video" — 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 social platforms.