Music Cog Online

Get music-synced videos ready to post, without touching a single slider. Upload your audio files (MP4, MOV, MP3, WAV, up to 500MB), say something like "sync...

Security Scan

The skill's requests and runtime instructions match its stated purpose (cloud-based music-to-video sync) and the single required secret (NEMO_TOKEN) is proportionate to that purpose.

Purpose & Capability

Name and description (sync music to videos) align with the declared requirement (NEMO_TOKEN) and the API endpoints described in SKILL.md. No unrelated credentials or binaries are requested.

Instruction Scope

Runtime instructions are focused on authenticating (via NEMO_TOKEN or anonymous-token endpoint), creating a session, uploading media, and polling export state. They do instruct generating and storing a session_id and to include attribution headers. One minor note: the docs say to auto-detect an install path for X-Skill-Platform header (which could require inspecting agent environment), and the metadata lists a config path (~/.config/nemovideo/) even though SKILL.md doesn't explicitly instruct reading files there.

Install Mechanism

Instruction-only skill with no install spec or external downloads; nothing is written to disk by an install step. Lowest installer risk.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv) which is appropriate for a cloud rendering API. No unrelated secrets or many environment variables are requested. The metadata's config path could allow storing tokens locally if implemented, which is reasonable for a service client.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill does not request persistent system-wide privileges or to modify other skills' configs.

Assessment

This skill appears to do what it says: it will upload the media you provide to nemovideo.ai and use a NEMO_TOKEN (or obtain a short-lived anonymous token) to run cloud renders. Before installing/using: ensure you trust the remote service (your media and a token are sent to their API); be aware anonymous tokens expire and have limited credits; check whether the agent will store session/token data under ~/.config/nemovideo/ or in environment variables and revoke tokens if needed; and confirm you are comfortable with the agent making network calls on your behalf. The metadata's mention of auto-detecting an install path is a small privacy consideration (the agent may inspect its environment to set a header) but not an outright security mismatch.

Getting Started

Share your audio files and I'll get started on AI music synchronization. Or just tell me what you're thinking.

Try saying:

• "sync my audio files"
• "export 1080p MP4"
• "sync background music to my video"

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.

Music Cog Online — Sync Music to Videos Online

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

Say you have a 3-minute MP3 background track and want to sync background music to my video and adjust the beat drops to match the cuts — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter video clips sync to music faster and with more accurate beat matching.

Matching Input to Actions

User prompts referencing music cog online, 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	music-cog-online
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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)

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.

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 → "sync background music to my video and adjust the beat drops to match the cuts" → 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 "sync background music to my video and adjust the beat drops to match the cuts" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, MP3, WAV for the smoothest experience.

Export as MP4 for widest compatibility across social platforms.