Ai Music Video Clip Generator

generate audio files into synced music videos with this skill. Works with MP3, WAV, MP4, MOV files up to 500MB. musicians and content creators use it for gen...

Security Scan

The skill is broadly consistent with an AI music-video frontend that uses a NEMO_TOKEN and a nemovideo.ai backend, but small metadata inconsistencies, automatic token acquisition/storage instructions, and lack of source/homepage mean you should be cautious before installing.

Purpose & Capability

The declared primary credential (NEMO_TOKEN) and the described network calls to nemovideo.ai align with the skill's stated purpose (cloud-rendered music video generation). However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata showed no required config paths — an internal inconsistency about where session tokens/state might be persisted.

Instruction Scope

The runtime instructions remain within the music-video generation domain (uploading files, SSE chat, export/polling). However the skill instructs the agent to automatically obtain an anonymous token if NEMO_TOKEN is not present and to store session_id and tokens for subsequent requests; it also explicitly tells the agent not to display raw API responses or token values to the user. Automatic token creation + hidden handling of tokens increases opacity and deserves scrutiny.

Install Mechanism

No install spec and no code files — instruction-only; nothing is written to disk by an installer from untrusted URLs. This is the lowest installation risk from a supply-chain perspective.

Credentials

Only one environment variable (NEMO_TOKEN) is required, which is proportionate to a third-party API integration. The SKILL.md flow will create and use such a token automatically if none is provided; that behavior is reasonable but should be explicit to users who prefer to supply/manage their own tokens.

Persistence & Privilege

The skill does not request always:true and does not demand elevated platform privileges. It does, however, suggest storing session_id/token state and references a config path (~/.config/nemovideo/) in its frontmatter — this implies local persistence of credentials/state (and the registry entry contradicts whether that path is required). Confirm where session data will be stored and how long tokens persist before installing.

What to consider before installing

This skill largely behaves like a normal cloud-rendering integration: it will call nemovideo.ai endpoints, upload media, and needs a NEMO_TOKEN. Before installing, consider: 1) provenance — the skill has no homepage/source listed; prefer packages with verifiable authors or docs; 2) token management — the skill will auto-create and store a token/session unless you supply one; decide whether you want to generate and provide your own token instead of letting the skill request one on your behalf; 3) persistence location — confirm whether ~/.config/nemovideo/ will be created and what it contains; review or sandbox that directory if possible; 4) privacy — uploaded media is sent to an external service; do not upload sensitive or private audio without understanding the provider's data retention and privacy policy; 5) demand transparency — ask the maintainer for a homepage, source code or privacy policy and for explicit details on token expiry and storage. These checks would reduce the remaining uncertainty before use.

Getting Started

Got audio files to work with? Send it over and tell me what you need — I'll take care of the AI music video creation.

Try saying:

• "generate a 3-minute MP3 song track into a 1080p MP4"
• "generate a music video clip synced to my song with matching visuals"
• "generating visual music video clips from audio tracks for musicians and content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

AI Music Video Clip Generator — Generate Music Videos from Audio

Send me your audio files and describe the result you want. The AI music video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute MP3 song track, type "generate a music video clip synced to my song with matching visuals", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 90 seconds produce the most visually coherent results.

Matching Input to Actions

User prompts referencing ai music video clip generator, 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	ai-music-video-clip-generator
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 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)

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a music video clip synced to my song with matching visuals" — concrete instructions get better results.

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

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

Common Workflows

Quick edit: Upload → "generate a music video clip synced to my song with matching visuals" → 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.