Automatic Music Generator

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

Security Scan

The skill's requested credential and runtime behavior are consistent with a cloud-based video→music service, with only small metadata/instruction inconsistencies that look like sloppy authoring rather than malice.

Purpose & Capability

Name/description (auto-generating background music for uploaded videos) align with required credential (NEMO_TOKEN) and the API endpoints described in SKILL.md. Minor inconsistency: registry metadata listed no config paths, but the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/). This looks like a documentation/metadata mismatch rather than a functional mismatch.

Instruction Scope

Runtime instructions stay within the stated purpose (create session, upload video, run SSE text stream, render/export). They do request the agent detect its install path (~/.clawhub/, ~/.cursor/skills/) to populate an X-Skill-Platform header — this requires probing known install locations (reading filesystem/environment) which is not strictly necessary for audio generation but appears to be used for attribution. The skill also instructs the agent to obtain an anonymous token via a POST if NEMO_TOKEN is absent; that is functionally reasonable for a self-service API but is an autonomous network call.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk install surface. There are no downloads, package installs, or archive extraction steps.

Credentials

Only one credential is required (NEMO_TOKEN), which is appropriate for a remote processing API. The SKILL.md also describes how to mint an anonymous token at runtime (100 credits, 7-day expiry). This is proportionate, but users should note the skill may create/use a token on your behalf and will persist session identifiers; the configPaths mention in SKILL.md suggests the author intended local config usage but the registry omitted it.

Persistence & Privilege

Skill is not always-enabled and does not request elevated system privileges. It asks to save session_id for job management (normal). Autonomous invocation is allowed (platform default) but not combined with other high-risk behaviors.

Assessment

This skill appears to do what it says: it talks to a remote Nemovideo API, needs a NEMO_TOKEN (or will request an anonymous token), and uploads videos to get music-scored exports. Before installing: (1) decide whether you trust the nemovideo.ai service — the skill will make network calls and can create/hold a short-lived token for you; (2) consider setting NEMO_TOKEN yourself rather than allowing the skill to mint one automatically if you want control over credentials; (3) be aware it may probe well-known install paths to set a header (this reads non-sensitive paths in your home directory) — if you have policy concerns about filesystem probing, avoid installing; (4) note the small metadata mismatch (configPaths present in SKILL.md but not in registry) — probably benign but indicates sloppy authoring. If you need stronger assurances, ask the publisher for source code or an official homepage before proceeding.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI music generation.

Try saying:

• "generate a 2-minute travel montage video into a 1080p MP4"
• "generate background music that matches the mood and pacing of my video"
• "automatically adding AI-generated background music to videos for content creators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Automatic 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 2-minute travel montage video and want to generate background music that matches the mood and pacing of my video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter videos under 60 seconds get the most accurately matched music mood.

Matching Input to Actions

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

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

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.

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.

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate background music that matches the mood and pacing 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.

Common Workflows

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