Game Music

Turn a 2-minute gameplay recording of an RPG dungeon scene into 1080p music-synced videos just by typing what you need. Whether it's adding AI-generated back...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud-based game-video music service, but there are minor metadata inconsistencies and privacy implications you should review before installing.

Purpose & Capability

The skill is a cloud video/music composition service and only requests a single service token (NEMO_TOKEN) and calls endpoints under mega-api-prod.nemovideo.ai — this matches the stated purpose of uploading footage, generating music, and returning rendered videos. Nothing else (unrelated clouds, system binaries, or broad OS access) is requested.

Instruction Scope

Runtime instructions tell the agent to upload user video files and orchestrate jobs via SSE and REST to nemovideo.ai, which is expected. The skill also instructs generating an anonymous token automatically if NEMO_TOKEN is not set and storing session_id for subsequent requests. Important privacy behavior: user video/audio will be transmitted to a third-party service; the skill explicitly instructs not to display raw API responses or tokens to users.

Install Mechanism

No install spec or code is provided (instruction-only). That is low-risk from an installation/execution perspective because nothing is written to disk by an installer step.

Credentials

Only NEMO_TOKEN is required as the primary credential, which is proportional to the service. However, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) for metadata while the registry metadata lists no required config paths—this mismatch should be clarified because it implies the skill may read/write a local config directory (session/token persistence).

Persistence & Privilege

The skill does not request always:true and uses the normal autonomous-invocation defaults. It instructs storing session_id and token lifetime is described (anonymous token valid 7 days). There is no instruction to modify other skills or system-wide settings, but the metadata/config-path mismatch suggests you should confirm whether it will persist tokens/config locally.

Assessment

This skill appears to do what it says: it will upload your videos to nemovideo.ai, generate music and return rendered MP4s. Before installing or using it, consider: (1) Privacy — your footage will be sent to a third-party service; do not upload sensitive content. (2) Token handling — the skill can auto-generate and store an anonymous NEMO_TOKEN (7-day, 100-credit token); ask where tokens/session IDs are persisted (SKILL.md references ~/.config/nemovideo/ but the registry metadata did not). (3) Verify the service — there is no homepage or known owner information in the registry metadata, so check the service’s reputation and privacy policy. If you require assurances, ask the skill author to clarify where tokens/session data are stored and to provide a service homepage or terms/privacy link before proceeding.

Getting Started

Send me your video game footage and I'll handle the AI music generation. Or just describe what you're after.

Try saying:

• "add a 2-minute gameplay recording of an RPG dungeon scene into a 1080p MP4"
• "add atmospheric background music that matches the mood of my gameplay video"
• "adding AI-generated background music to gaming videos for gaming content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Game Music — Add Music to Game Videos

Drop your video game footage in the chat and tell me what you need. I'll handle the AI music generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute gameplay recording of an RPG dungeon scene, ask for add atmospheric background music that matches the mood of my gameplay video, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 60 seconds get the most accurate mood-matched music.

Matching Input to Actions

User prompts referencing game music, 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 game-music, 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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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 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

Common Workflows

Quick edit: Upload → "add atmospheric background music that matches the mood of my gameplay 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 "add atmospheric background music that matches the mood of my gameplay 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 YouTube, Twitch, and TikTok.