Music To

Skip the learning curve of professional editing software. Describe what you want — turn this music track into a synced video with visuals and beat cuts — and...

Security Scan

The skill's behavior mostly matches its description (it talks to a cloud video-rendering API and asks for a single NEMO_TOKEN), but there are small inconsistencies in its metadata (a required config path appears only in the SKILL.md frontmatter) and it will generate/obtain tokens automatically which you should understand before installing.

Purpose & Capability

The name/description (convert audio into synced videos) aligns with the endpoints and workflows described (session creation, SSE, upload, render). Requesting a NEMO_TOKEN credential is coherent for a cloud service. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not reflected in the registry metadata summary: this mismatch is unexpected and should be clarified.

Instruction Scope

The runtime instructions confine actions to the nemovideo API (auth, session, upload, render, credits, state). The skill does not instruct reading arbitrary system files or unrelated environment variables. It will, however, generate an anonymous token from the remote endpoint if NEMO_TOKEN is missing — that involves sending a generated UUID and receiving a token from the server.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — low install risk (nothing written to disk by the skill package itself).

Credentials

Only a single credential (NEMO_TOKEN) is declared as required, which is proportionate for a cloud rendering service. The SKILL.md also indicates it may create an anonymous NEMO_TOKEN if none is present (via a network call). The earlier registry summary said no config paths required, but the skill frontmatter mentions ~/.config/nemovideo/ — that inconsistency could imply the skill expects to read that local config in some contexts; clarify before granting broader filesystem access.

Persistence & Privilege

always is false and the skill does not claim to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but this skill's requested privileges are limited to calling the remote API and using a token.

What to consider before installing

What to check before installing: (1) Confirm the service domain (mega-api-prod.nemovideo.ai) and the publisher are legitimate — there's no homepage or repo listed. (2) Decide whether you want to provide a persistent NEMO_TOKEN; if you don't, the skill will obtain an anonymous token from the remote service (100 free credits, 7‑day expiry) — that means audio files and a client UUID will be sent to that remote endpoint. (3) Ask the publisher to explain the metadata mismatch: SKILL.md frontmatter lists ~/.config/nemovideo/ while registry metadata shows no config paths — if the skill will read that directory, understand what it contains and whether that exposes credentials. (4) If you handle sensitive audio, confirm the service's privacy/storage policy and whether uploads are retained. (5) If you need higher assurance, request the skill's code or an official homepage/source before installing. These checks will reduce risk; the package itself otherwise appears coherent with its stated purpose.

Getting Started

Share your audio files and I'll get started on music-driven video creation. Or just tell me what you're thinking.

Try saying:

• "convert my audio files"
• "export 1080p MP4"
• "turn this music track into a"

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 Video — Convert Music Into Synced Videos

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

Here's a typical use: you send a a 3-minute MP3 track, ask for turn this music track into a synced video with visuals and beat cuts, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter tracks under 2 minutes produce tighter, more accurate beat-synced cuts.

Matching Input to Actions

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

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.

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

Common Workflows

Quick edit: Upload → "turn this music track into a synced video with visuals and beat cuts" → Download MP4. Takes 1-2 minutes 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 "turn this music track into a synced video with visuals and beat cuts" — concrete instructions get better results.

Max file size is 200MB. Stick to MP3, WAV, AAC, M4A for the smoothest experience.

Export as MP4 for widest compatibility across YouTube, Instagram, and TikTok.