To Add Music

Get music-backed videos ready to post, without touching a single slider. Upload your video files (MP4, MOV, AVI, WebM, up to 500MB), say something like "add...

Security Scan

The skill mostly behaves like a cloud video/music service connector (it only needs a single NEMO_TOKEN), but there are small inconsistencies in its metadata and a couple of runtime behaviors that deserve attention before installing.

Purpose & Capability

The name/description (add background music to videos) matches the runtime instructions (upload video, call nemo API, render/export). Requesting a single NEMO_TOKEN is proportionate. However, the skill's SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch should be resolved so you know whether the skill intends to write/read local config.

Instruction Scope

The SKILL.md instructs the agent to perform network calls to an external API (mega-api-prod.nemovideo.ai) for anonymous-token generation, session creation, SSE messaging, upload, and export — all expected for this purpose. The instructions also say to 'save session_id' and to detect an install path to populate X-Skill-Platform; that implies the agent may read its install path or write session state to disk. There are no instructions to read unrelated system files or other credentials, but the install-path auto-detection and unspecified storage location for tokens/sessions are scope items to clarify.

Install Mechanism

There is no install spec and no code files; this is instruction-only, so nothing is downloaded or written by an installer. That minimizes install-time risk.

Credentials

Only one environment variable (NEMO_TOKEN) is declared as required and as the primary credential, which is appropriate for an API-driven video service. The SKILL.md offers a flow to generate anonymous tokens if none are supplied. The earlier-noted metadata/configPath mismatch raises the question of whether tokens/session state will be persisted to ~/.config/nemovideo/ (which would justify requiring that path) — this should be clarified.

Persistence & Privilege

The skill is not always-enabled and is user-invocable; it does not request elevated or persistent platform privileges in the registry. Autonomous invocation is allowed (platform default) but not combined with 'always: true' or broad credential access.

What to consider before installing

This skill appears to do what it says (upload video, call a cloud API that adds background music). Before installing or enabling it: 1) confirm whether you want the skill to store session tokens locally — SKILL.md mentions saving session_id and its frontmatter references ~/.config/nemovideo/ even though the registry showed no config paths; ask the author where tokens/sessions will be saved and how long. 2) If you already have a NEMO_TOKEN, provide it only if you trust the nemo endpoint; otherwise the skill can create an anonymous token (7-day expiry). 3) Be aware the skill will make network requests to mega-api-prod.nemovideo.ai and require upload of your video files — don’t use it for videos you don’t want to send to a third-party service. 4) If you need stronger assurance, request the maintainer to remove the install-path auto-detection (or document exactly what filesystem reads/writes are required) and to reconcile the configPath declaration with the registry metadata.

Getting Started

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

Try saying:

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

Add Music — Add Background Music to Videos

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

Here's a typical use: you send a a 60-second travel montage clip, ask for add background music that matches the mood of my video, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips sync music faster and more accurately.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	to-add-music
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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 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 → "add background music that matches the mood of my video" → Download MP4. Takes 20-40 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 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.