Music Ai

Skip the learning curve of professional editing software. Describe what you want — generate a music video with visuals that sync to the beat — and get music-...

Security Scan

The skill's requirements and runtime instructions are generally consistent with a cloud-based music-video generation service, with only minor inconsistencies worth checking before use.

Purpose & Capability

Name/description (generate music videos) match the runtime instructions and listed API endpoints. The sole required credential (NEMO_TOKEN) aligns with a cloud backend that needs Bearer auth for uploads, sessions, and exports.

Instruction Scope

Instructions focus on session creation, uploads, SSE streaming, polling, and exports — all appropriate for a render service. The skill also instructs the agent to read its own SKILL.md frontmatter for attribution and to detect install paths (~/.clawhub, ~/.cursor/skills) at runtime; these filesystem reads are minor but should be noted as extra scope.

Install Mechanism

No install spec or code files (instruction-only) — lowest-risk distribution model. The skill does perform network calls to a specific domain (mega-api-prod.nemovideo.ai), but that is expected for a cloud API service.

Credentials

Only NEMO_TOKEN is required (declared as primary), which is proportionate. Minor inconsistency: the SKILL.md frontmatter metadata lists a config path (~/.config/nemovideo/) whereas the registry metadata earlier reported no required config paths; this mismatch should be clarified (the config path may be used to locate stored tokens/sessions).

Persistence & Privilege

The skill is not marked always:true and does not request elevated platform-wide privileges. It can be invoked autonomously (platform default), which is expected for skills that interact with cloud backends.

Assessment

This skill appears to do what it says: it uploads user audio/videos to a cloud rendering API and returns a generated video. Before installing: (1) Confirm you trust the domain (mega-api-prod.nemovideo.ai) and the NEMO_TOKEN consumer — this token grants upload/render access; (2) Ask whether the skill will persist the anonymous token and where (environment vs config file), and whether it will write anything under ~/.config/nemovideo/ or other paths; (3) Avoid supplying other credentials; run initial tests with non-sensitive sample media and a disposable token/account if possible; (4) If you need higher assurance, request the owner/source or an official homepage/manifest to verify ownership and hosting.

Getting Started

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

Try saying:

• "generate my audio files"
• "export 1080p MP4"
• "generate a music video with visuals"

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 AI — Generate Videos from Music

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

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

Tip: shorter tracks under 2 minutes process noticeably faster.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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-ai
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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.

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 field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Common Workflows

Quick edit: Upload → "generate a music video with visuals that sync to the beat" → 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 "generate a music video with visuals that sync to the beat" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across streaming and social platforms.