Free Music Ai Generator

Get music-backed videos ready to post, without touching a single slider. Upload your video or images (MP4, MOV, AVI, WebM, up to 500MB), say something like "...

Security Scan

The skill generally does what it says (remote video/music rendering) and only needs a single API token, but the runtime instructions ask the agent to probe local install/config paths and to contact an external anonymous-token endpoint — plus there's a small metadata mismatch — so you should review those behaviors before installing.

Purpose & Capability

The skill's stated purpose (generate music-backed videos) aligns with the single required credential NEMO_TOKEN and the described API calls. However the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) and the instructions derive headers from local install paths (e.g., ~/.clawhub/, ~/.cursor/), which is not essential to core functionality and is inconsistent with the registry summary that listed no required config paths.

Instruction Scope

The instructions direct the agent to call external APIs (expected) and to upload user media (expected). They also tell the agent to detect local install locations and a local config path in order to populate attribution headers, which requires reading the filesystem and leaks local environment details. The instructions include an anonymous-token flow (POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token) if NEMO_TOKEN is not present — this is functional but causes network contact to a third-party and creates tokens tied to the client id. There are no steps that request unrelated credentials, but filesystem probing and automatically obtaining tokens are broader than strictly necessary.

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. That's the lowest-risk install mechanism.

Credentials

Only NEMO_TOKEN is declared as required and it is appropriate for an external API. However the SKILL.md metadata and instructions reference a config path (~/.config/nemovideo/) and expect to detect install directories to populate headers; those imply reading local files or probing paths outside the skill's primary need and are not well-justified in the description.

Persistence & Privilege

The skill does not request always:true and does not ask to alter other skills or system-wide settings. Autonomous invocation is allowed by default but is not combined with excessive credential requests here.

What to consider before installing

This skill appears to do what it says (remote music + video rendering) and only needs an API token, but it also instructs the agent to probe certain local paths (~/.clawhub, ~/.cursor, ~/.config/nemovideo/) to populate attribution headers and will contact an external anonymous-token endpoint if no token is provided. Before installing: (1) consider whether you're comfortable the agent may check for those local paths (this reveals whether certain tools/configs exist), (2) avoid putting sensitive credentials in NEMO_TOKEN unless you trust the service, (3) ask the developer for source or a homepage if you need more assurance, and (4) if unsure, run the skill in a restricted/sandboxed environment or deny filesystem access so it cannot probe local directories. If you plan to provide a long-lived token, rotate it later and limit its permissions if possible.

Getting Started

Share your video or images and I'll get started on AI music generation. Or just tell me what you're thinking.

Try saying:

• "generate my video or images"
• "export 1080p MP4"
• "generate a background music track that"

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.

Free Music AI Generator — Generate Music for Your Videos

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

A quick example: upload a 60-second travel montage video, type "generate a background music track that matches the mood of my video", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter videos allow the AI to match music tempo and mood more accurately.

Matching Input to Actions

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

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-music-ai-generator, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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.

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)

Common Workflows

Quick edit: Upload → "generate a background music track that matches the mood of my video" → Download MP4. Takes 20-40 seconds 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 background music track that matches the mood of my video" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.