Free Video Music Generator

Skip the learning curve of professional editing software. Describe what you want — generate and add background music that matches the mood of my video — and...

Security Scan

The skill's runtime instructions mostly match a cloud video-music service (upload video, generate music, return URL), but there are small metadata inconsistencies and privacy/third‑party risks you should understand before installing.

Purpose & Capability

The name/description (add AI music to videos) aligns with the runtime actions: session creation, upload, SSE chat, render/export and download URL polling to https://mega-api-prod.nemovideo.ai. Requesting a NEMO_TOKEN is coherent for a cloud API. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not reflected in the registry's reported required config paths — this metadata mismatch should be clarified.

Instruction Scope

Instructions confine behavior to the remote rendering service (auth, session, upload, SSE, export). They explicitly call for checking NEMO_TOKEN, obtaining an anonymous token if missing, and performing uploads. That means user video files and session tokens will be sent to the external domain — expected for this use case but a clear privacy/networking action that the user should be aware of. The skill does not instruct reading arbitrary local files beyond the possible config path mentioned in metadata (inconsistency).

Install Mechanism

There is no install spec and no code files (instruction-only), so nothing will be written to disk by an installer. This is the lowest install risk.

Credentials

Only one credential is declared (NEMO_TOKEN) which is proportional for authenticating with the service. The skill's fallback to request an anonymous token from the same domain if NEMO_TOKEN is absent is consistent with its purpose. Consider that any NEMO_TOKEN you provide (or anonymous token obtained at runtime) will grant the skill network access to the third‑party backend and could be used to list/poll jobs and access returned URLs; treat it as a secret. There is no evidence the skill requests unrelated credentials.

Persistence & Privilege

always:false and normal model invocation are used. The skill does not request forced global inclusion or system-wide config changes. Note: if your agent runs autonomously and has a token, it could initiate uploads/requests without interactive prompts — standard platform behavior but worth keeping in mind.

What to consider before installing

This skill appears to do what it says (upload your video to a cloud backend, generate background music, and return a download link), but before installing you should: 1) Confirm you trust the endpoint (https://mega-api-prod.nemovideo.ai) and review its privacy/terms because your videos will be uploaded off-device; 2) Avoid setting a long‑lived, high‑privilege NEMO_TOKEN in shared/system environments — prefer a disposable/anonymous token if possible; 3) Ask the author to clarify the metadata mismatch about ~/.config/nemovideo/ (does the skill read that folder?), and request a homepage/source for auditing; 4) Be aware that an agent with access to NEMO_TOKEN could perform network uploads/polls autonomously — limit token scope or revoke tokens when not needed.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "generate a 60-second travel montage clip into a 1080p MP4"
• "generate and add background music that matches the mood of my video"
• "adding AI-generated background music to videos for TikTok creators"

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.

Free Video Music Generator — Add AI Music to Videos

Send me your video clips 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 clip, type "generate and add background music that matches the mood of my video", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 2 minutes produce more cohesive music that fits the full video.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-video-music-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).

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 and add background music 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 across social platforms.

Common Workflows

Quick edit: Upload → "generate and add background music that matches the mood of my video" → Download MP4. Takes 30-60 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.