Ai Music Video Generator Free

Turn a 3-minute MP3 song file into 1080p synced music videos just by typing what you need. Whether it's generating visual music videos from audio tracks or q...

Security Scan

The skill's requests and runtime instructions are generally consistent with a cloud-based audio→video rendering service, but there are small metadata inconsistencies and you should be aware that it will contact a third‑party API and upload your audio.

Purpose & Capability

The skill claims to convert audio into 1080p videos and the required credential (NEMO_TOKEN) and endpoints in SKILL.md align with that purpose. However, the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) that isn't used or justified elsewhere in the instructions, which is an unexplained metadata mismatch.

Instruction Scope

Instructions are limited to connecting to the remote rendering API, creating/using a token, creating a session, uploading media, streaming SSE responses, and polling render status — all within the expected scope for a cloud render service. The skill will POST files and stream events to https://mega-api-prod.nemovideo.ai; it does not instruct reading unrelated local files or other environment variables. Note: it requires auto-generation of an anonymous token when NEMO_TOKEN is absent, which means the agent will make network calls without an explicit user-supplied key if none is provided.

Install Mechanism

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

Credentials

Only one credential (NEMO_TOKEN) is declared as required, which is proportionate for calling the remote API. The frontmatter's mention of a config path (~/.config/nemovideo/) conflicts with the registry metadata (which lists no required config paths) and is not referenced in runtime instructions — this mismatch should be clarified before trusting the skill to access local config.

Persistence & Privilege

The skill is not marked always:true and does not request elevated persistence. It can be invoked autonomously (platform default), which is normal; this combined with only a single service credential does not create an outsized privilege by itself.

Assessment

This skill appears to do what it claims (upload audio and request server-side rendering), but before installing or using it you should: (1) be aware that your audio and metadata will be uploaded to https://mega-api-prod.nemovideo.ai and processed there — review privacy and terms for that service or avoid uploading sensitive material; (2) prefer supplying your own NEMO_TOKEN if you have an account rather than relying on the anonymous-token flow the skill can create automatically; (3) ask the publisher to explain the frontmatter config path (~/.config/nemovideo/) because the SKILL.md does not use it — unexplained requests for local config are worth clarifying; (4) verify TLS and the domain name are legitimate (no shortened URLs or personal IPs here); and (5) if you need higher assurance, request the publisher add explicit statements about what is stored, retention of uploads and render jobs, and whether any other local files or environment variables will be accessed. If the skill later includes code files, an installer, or additional required env vars/config paths, re-evaluate (that would raise my confidence or change the verdict).

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 file into a 1080p MP4"
• "generate a music video with visuals that match the beat and mood of my track"
• "generating visual music videos from audio tracks for independent musicians and content creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Music Video Generator Free — Turn Audio Into Music Videos

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 file, type "generate a music video with visuals that match the beat and mood of my track", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter tracks under 2 minutes generate faster and give you more control over visual pacing.

Matching Input to Actions

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

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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-music-video-generator-free
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.

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

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)

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 match the beat and mood of my track" — 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, Instagram, and TikTok.

Common Workflows

Quick edit: Upload → "generate a music video with visuals that match the beat and mood of my track" → 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.