Video Music Generator

generate video clips into music-backed videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for automatically ge...

Security Scan

The skill's requirements and runtime instructions are internally consistent with a cloud-backed video→music generation service, but source is unknown and there are minor metadata inconsistencies and privacy considerations you should review before using it.

Purpose & Capability

Name/description (generate music-backed videos) align with the runtime instructions: the SKILL.md describes uploading videos, creating render sessions, SSE for generation, and exporting MP4s. The single required credential (NEMO_TOKEN) matches the described cloud API auth model.

Instruction Scope

Instructions direct the agent to upload user video/audio files and interact with mega-api-prod.nemovideo.ai (auth, session, upload, render). That is within the stated purpose, but it means user content will be transmitted to a third‑party service. The skill also instructs creating an anonymous token via an API if NEMO_TOKEN is absent and to read the agent install path to populate X-Skill-Platform — both are reasonable for attribution but increase data points sent to the backend.

Install Mechanism

No install spec and no code files (instruction-only) — nothing is written to disk or downloaded by the skill itself. This minimizes local install risk.

Credentials

Only NEMO_TOKEN is required, which is proportionate to a cloud-rendering service. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while registry metadata reported no required config paths — that's an inconsistency to verify. The skill will also generate and use an anonymous token if none is provided.

Persistence & Privilege

always:false (no forced global presence) and normal model invocation permissions. The skill does not request elevated platform-wide privileges. It will create short-lived sessions/tokens with the remote service but does not ask to modify other skills or system settings.

Assessment

This skill will upload your videos/audio to a third‑party API (mega-api-prod.nemovideo.ai) for processing and will use or obtain an NEMO_TOKEN to authenticate. Before installing or enabling it: 1) Confirm you trust nemovideo.ai and review their privacy/retention terms (your media will leave your device). 2) Decide whether to provide your own NEMO_TOKEN or allow the skill to request an anonymous token (anonymous tokens appear to be temporary but still transmit metadata). 3) Note the small metadata inconsistency: SKILL.md declares a config path (~/.config/nemovideo/) but registry metadata lists none — ask the author whether the skill will read or write that path. 4) If you need guarantees (no uploads, on-device processing), do not enable this skill. 5) If you proceed, consider limiting the files you upload (avoid sensitive content) and look for an official homepage or source code to verify implementation and terms. If you want, I can draft a short checklist or questions to send to the skill author/owner before you install.

Getting Started

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

Try saying:

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

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.

Video Music Generator — Generate Music for Your Videos

This tool takes your video clips and runs AI music generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second travel montage clip and want to generate a background music track that matches the mood and pace of my video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes get more accurate mood-matched music.

Matching Input to Actions

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

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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-music-generator
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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

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.

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

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)

Common Workflows

Quick edit: Upload → "generate a background music track that matches the mood and pace 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.

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 and pace 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 platforms and devices.