Music To Your

Get music-synced 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 largely behaves like a cloud video-music-syncing client (which explains most network calls and the single NEMO_TOKEN credential), but there are a few inconsistencies and data-access implications you should understand before installing.

Purpose & Capability

The declared purpose (upload clips, get music-synced renders) matches the API endpoints and flows described (session creation, upload, render, export). Requesting a single NEMO_TOKEN credential is proportionate. However, the SKILL.md frontmatter metadata references a config path (~/.config/nemovideo/) even though the registry metadata lists no required config paths — that mismatch should be clarified.

Instruction Scope

Runtime instructions remain focused on the backend service: check/obtain NEMO_TOKEN, create a session, upload files, run SSE and poll render jobs. Two things to watch: (1) the skill will POST to an external anonymous-token endpoint to mint tokens if NEMO_TOKEN is missing (this is expected for anonymous flows but involves network calls and returned tokens), and (2) it instructs auto-detecting an install path to set X-Skill-Platform, which implies reading agent/install path information (potentially filesystem metadata). Neither is obviously out of scope for a cloud render client, but both have privacy implications and should be documented.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk (nothing is downloaded or written by an installer).

Credentials

Only NEMO_TOKEN is required, which is appropriate for a cloud API client. The skill's instructions also include a flow to obtain an anonymous token if none is present; that behavior is sensible but means the skill (or the backend) will receive a freshly minted token and could accept uploads without a user-supplied credential. No other unrelated secrets are requested.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill stores session_id for job management (reasonable). It does not request system-wide configuration changes or permanent privileges, but it may leave server-side render jobs running if a session/client is closed.

What to consider before installing

This skill will upload your video files and interact with https://mega-api-prod.nemovideo.ai to create sessions, upload, and render. Before installing: (1) confirm you trust that external domain and its privacy/terms (your media and any embedded metadata are sent there); (2) prefer to set your own NEMO_TOKEN instead of allowing the skill to obtain anonymous tokens if you want auditability; (3) ask the author to clarify the metadata/configPaths mismatch (~/.config/nemovideo/) and exactly what the "auto-detect install path" step reads (to avoid unexpected filesystem disclosures); and (4) be aware that uploaded content and generated tokens may be retained by the backend for job processing. If you cannot verify the backend or want to avoid sending files off-site, do not install or use this skill.

Getting Started

Share your video clips and I'll get started on AI music syncing. Or just tell me what you're thinking.

Try saying:

• "add my video clips"
• "export 1080p MP4"
• "add background music that matches the"

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.

Music To Your Video — Sync Music to Your Clips

Drop your video clips in the chat and tell me what you need. I'll handle the AI music syncing 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 and rhythm of my video, 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 — shorter clips sync music more precisely to scene cuts.

Matching Input to Actions

User prompts referencing music to your, 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.

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

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

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

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.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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

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)

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

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 and rhythm 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 and rhythm 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.