Add Music Ai

Skip the learning curve of professional editing software. Describe what you want — add background music that matches the mood of my video — and get music-enh...

Security Scan

The skill's requirements and runtime instructions are internally consistent with a cloud-based video music-adding service, but there are a few metadata inconsistencies and privacy considerations you should understand before use.

Purpose & Capability

The skill is named and described as a cloud-based 'add music to video' tool and only requests an API token (NEMO_TOKEN) and access to a nemo API — this is proportionate and expected for that purpose. No unrelated binaries or credentials are requested. Note: the frontmatter also lists a config path (~/.config/nemovideo/) even though the registry metadata above said no config paths; this is an inconsistency but plausibly used for local token/cache storage.

Instruction Scope

Runtime instructions focus on authenticating (use NEMO_TOKEN or request an anonymous token), opening a session, uploading video files, streaming SSE messages, and exporting processed video — all consistent with the described task. Important runtime behaviors: user video files are uploaded to an external domain (mega-api-prod.nemovideo.ai); the agent is instructed to read this file's YAML frontmatter and to detect an install path to set X-Skill-Platform headers (this requires checking agent runtime paths). The instructions do not ask to read unrelated user files or arbitrary environment variables, but they do require transmitting potentially sensitive media to a third-party service.

Install Mechanism

No install spec or code files are present — the skill is instruction-only. This is the lowest-risk install mechanism; nothing is written to disk by an installer as part of skill setup. (However, the skill does instruct network activity at runtime.)

Credentials

Only one credential is declared (NEMO_TOKEN) and that fits the API usage. The skill will generate an anonymous token via the service if NEMO_TOKEN is absent, which is reasonable. The frontmatter also lists a config path (~/.config/nemovideo/) which implies the agent may read or write local config/cache there; this was not reflected in the top-level registry metadata and should be clarified. Ensure NEMO_TOKEN does not contain broader privileges than intended before supplying it.

Persistence & Privilege

The skill is not marked always:true and does not request elevated platform-wide privileges. It does instruct saving session_id from the API responses for session management, but that is scoped to the service and expected for functionality. Autonomous invocation is allowed by default (normal) and not by itself a concern.

Assessment

This skill sends your video files (up to 500 MB) and session/auth tokens to an external service (mega-api-prod.nemovideo.ai) to perform AI music addition — that is expected for this functionality but has privacy implications. Before installing: (1) confirm you trust the service operator (no homepage or clear owner info is provided in the registry entry), (2) avoid uploading sensitive or private video unless you accept third-party processing, (3) if providing an existing NEMO_TOKEN, ensure it has only the permissions needed (avoid using high-privilege tokens), (4) ask the publisher to clarify the metadata inconsistency about ~/.config/nemovideo/ (does the skill read/write local config?), and (5) consider using the anonymous token flow for one-off tests. If any of those answers are unsatisfactory, do not install or use the skill.

Getting Started

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

Try saying:

• "add a 90-second travel video clip into a 1080p MP4"
• "add background music that matches the mood of my video"
• "adding AI-selected 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 AI — Add AI Music to Videos

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

Say you have a 90-second travel video clip and want to add 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 get better music sync results from the AI.

Matching Input to Actions

User prompts referencing add music ai, 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.

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

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

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

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

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.

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

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)

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.

Common Workflows

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