Ai Music Video Maker Free

Skip the learning curve of professional editing software. Describe what you want — create a music video for my song with synced visuals and beat drops — and...

Security Scan

The skill mostly matches its stated purpose (cloud video rendering) but contains inconsistencies and instructions (automatic anonymous-token creation, hidden tokens, reading local paths, ambiguous storage) that warrant caution before installing.

Purpose & Capability

The name/description (convert audio to AI-produced music videos) aligns with the endpoints and actions described (upload, render, export). However the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that the registry metadata did not list — an internal inconsistency about what local configuration the skill expects or will use.

Instruction Scope

Runtime instructions tell the agent to obtain an anonymous token if NEMO_TOKEN is not set, to POST that UUID to an external API, to 'store' the returned token/session_id for future requests, and to 'don't display' raw API responses or token values to users. The skill also instructs reading local install paths and this file's YAML frontmatter at runtime to set attribution headers. These actions go beyond simply accepting an audio upload and returning a URL — they include automatic credential acquisition, local file/ path inspection, and opaque persistence behavior.

Install Mechanism

Instruction-only skill with no install spec and no code files; no archives or external installers are downloaded. This is the lower-risk installation model.

Credentials

Only NEMO_TOKEN is declared as required, which is appropriate for a cloud-rendering service. But the skill will create an anonymous token itself if not provided and instructs storing session tokens; where/how those tokens are stored is unspecified. Also the SKILL.md frontmatter requests a config path (~/.config/nemovideo/) which was not declared in the registry metadata.

Persistence & Privilege

The skill instructs storing a session_id/token and references a config path. Although 'always' is false and there is no install, the combination of automatic token creation, opaque storage instructions, and 'do not display token values' raises concern about persistence of credentials and possible long-lived access to the external backend (tokens are said to be valid for 7 days).

What to consider before installing

This skill talks to an external domain (mega-api-prod.nemovideo.ai), will upload your audio to a cloud service, and can auto-generate and store an anonymous auth token if you don't provide one. Before installing, decide whether you trust that domain and its privacy policy. If you proceed: (1) Prefer supplying your own NEMO_TOKEN (so the agent doesn't create or persist tokens itself); (2) Ask the skill author where session/token data are stored (in-memory vs written to ~/.config/nemovideo/ or other files) and whether you can revoke them; (3) Be aware uploaded files may be processed/stored by the provider — don't upload sensitive or copyrighted audio unless you accept that; (4) If you are uncomfortable with the agent silently obtaining credentials or reading install paths, don't install or disable autonomous invocation for this skill until the storage/behavior is clarified.

Getting Started

Send me your audio files and I'll handle the AI music video creation. Or just describe what you're after.

Try saying:

• "create a 3-minute MP3 song track into a 1080p MP4"
• "create a music video for my song with synced visuals and beat drops"
• "generating visual music videos from audio tracks for musicians and TikTok 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 Maker Free — Turn Audio Into Music Videos

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 song track and want to create a music video for my song with synced visuals and beat drops — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter tracks under 2 minutes render noticeably faster.

Matching Input to Actions

User prompts referencing ai music video maker free, 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: ai-music-video-maker-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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

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 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 → "create a music video for my song with synced visuals and beat drops" → 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 "create a music video for my song with synced visuals and beat drops" — 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 YouTube, TikTok, and Instagram.