Add Music To Video Android

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

Security Scan

The skill's requirements and runtime instructions are coherent with its stated purpose (cloud-based video + audio rendering) and do not request unexplained credentials or installs, though it will upload user media to a third-party API and create a short-lived anonymous token if no NEMO_TOKEN is provided.

Purpose & Capability

The name/description map to the declared primary credential (NEMO_TOKEN) and the SKILL.md endpoints for a cloud render service, so the requested credential is appropriate. Minor inconsistency: the registry metadata listed no required config paths, but the SKILL.md frontmatter references a config path (~/.config/nemovideo/); the instructions themselves do not describe reading that path. This is a small mismatch but worth confirming.

Instruction Scope

SKILL.md limits activity to connecting to a single backend (https://mega-api-prod.nemovideo.ai), creating/using a session, uploading media, SSE-based editing, and polling for exports. It does not instruct reading unrelated local files, other env vars, or sending data to other endpoints. It does instruct generating an anonymous token if NEMO_TOKEN is absent (network call) and to include specific attribution headers on each request — both expected for this workflow.

Install Mechanism

There is no install spec and no code files — this is instruction-only. Nothing will be written to disk or downloaded as part of an install step per the provided metadata.

Credentials

Only a single credential (NEMO_TOKEN) is required and is appropriate for a hosted rendering API. The skill will also obtain a short-lived anonymous token via an API call if NEMO_TOKEN is missing; that behavior is documented. Consider whether you want the agent to use an anonymous token (which grants the service limited access to your uploaded media) versus providing your own token.

Persistence & Privilege

always is false and the skill does not request elevated platform presence or modification of other skills. Autonomous invocation is allowed (platform default) but not combined with any unusual privileges.

Assessment

This skill uploads your video and audio to a third-party API (mega-api-prod.nemovideo.ai) for cloud rendering and requires a service token (NEMO_TOKEN). If you don't provide a token it will request an anonymous starter token on your behalf. Before installing: confirm you trust that external service with your media, review its privacy/data-retention policy, and avoid uploading sensitive content. Also note the minor metadata mismatch (SKILL.md references a config path) — if you are concerned, ask the skill author whether the agent will read ~/.config/nemovideo/ or any other local files.

Getting Started

Send me your video clips and I'll handle the audio track addition. Or just describe what you're after.

Try saying:

• "add a 60-second Android phone recording into a 1080p MP4"
• "add background music to my video and adjust the volume balance"
• "adding background music to Android-recorded videos for Android creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Add Music to Video Android — Add Music and Export Video

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

Say you have a 60-second Android phone recording and want to add background music to my video and adjust the volume balance — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: trim your video to the right length before adding music so the track fits cleanly.

Matching Input to Actions

User prompts referencing add music to video android, 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.

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

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

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

Common Workflows

Quick edit: Upload → "add background music to my video and adjust the volume balance" → 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 to my video and adjust the volume balance" — 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 Android and social platforms.