Music To Best

convert audio files into music-synced videos with this skill. Works with MP3, WAV, AAC, M4A files up to 500MB. musicians and content creators use it for turn...

Security Scan

The skill's behavior mostly matches a cloud-based audio→video service, but there are inconsistencies (metadata vs SKILL.md) and unnecessary filesystem-detection instructions that warrant caution before installing.

Purpose & Capability

The name/description align with using a remote rendering API and the single required credential (NEMO_TOKEN) is appropriate for that service. However, the SKILL.md frontmatter advertises a config path (~/.config/nemovideo/) while the registry metadata listed no required config paths — this mismatch is unexplained and should be clarified.

Instruction Scope

Runtime instructions are mostly scoped to session creation, uploads, SSE chat, polling export status, and returning download URLs — all expected. But the skill also instructs the agent to detect an install path to set X-Skill-Platform and to read the skill file's YAML frontmatter at runtime. Detecting install paths implies filesystem probing (e.g., checking ~/.clawhub/ or ~/.cursor/skills/) which is not necessary for core conversion and could broaden data access depending on implementation.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer — low install risk.

Credentials

Only NEMO_TOKEN is required which fits a service API token. That said, the SKILL.md frontmatter lists configPaths (e.g., ~/.config/nemovideo/) and asks the agent to read its own YAML frontmatter to populate attribution headers; those extra file-access expectations are not justified by the simple conversion use-case and create an ambiguity about what local data the skill will access.

Persistence & Privilege

always is false and the skill does not request system-wide or cross-skill configuration changes. Autonomous invocation is allowed but that's the platform default and not itself a red flag here.

What to consider before installing

This skill appears to call a remote rendering API and needs a NEMO_TOKEN to authenticate — that part is coherent. Before installing: (1) confirm you trust https://mega-api-prod.nemovideo.ai because your audio files and any generated/anonymous token will be sent there; (2) ask the author why the SKILL.md frontmatter references a local config path and why the agent must detect install paths (this requires filesystem access); (3) prefer using a short-lived anonymous token if you don't want to store a long-lived NEMO_TOKEN; (4) if you need a higher assurance, request the skill's source or a code-based implementation so you can verify it doesn't read other local files or exfiltrate extra data.

Getting Started

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

Try saying:

• "convert my audio files"
• "export 1080p MP4"
• "sync visuals to the beat and"

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 to Best — Turn Music Into Synced Videos

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

Say you have a 3-minute MP3 music track and want to sync visuals to the beat and create the best highlight video from my music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter tracks under 2 minutes produce tighter, more polished results.

Matching Input to Actions

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

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

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

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 → "sync visuals to the beat and create the best highlight video from my music" → 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 "sync visuals to the beat and create the best highlight video from my music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms like YouTube and Instagram.