Video Music

Turn a 2-minute travel video clip into 1080p music-backed videos just by typing what you need. Whether it's adding background music to videos automatically o...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud video-music editing service and the single required credential (NEMO_TOKEN) is proportionate, with only minor scope notes about reading local metadata/config paths.

Purpose & Capability

The skill is a cloud-backed video music/editor front-end; requiring a service token (NEMO_TOKEN) and calling the described nemovideo.ai endpoints aligns with the stated purpose. One small inconsistency: the SKILL.md frontmatter advertises access to a config path (~/.config/nemovideo/) while the registry metadata listed no required config paths — reading that config directory could be justified for cached/session data, but it should be declared consistently.

Instruction Scope

Runtime instructions are narrowly scoped to interacting with the nemo backend: generating a client UUID, obtaining an anonymous token if needed, creating sessions, uploading files, streaming SSE and polling renders. The skill instructs the agent to read its own YAML frontmatter at runtime and to detect install path (e.g., ~/.clawhub/ or ~/.cursor/skills/) to set X-Skill-Platform; this requires reading local paths but is limited in scope. No instructions ask the agent to read unrelated user files or transmit data to third parties outside the nemovideo.ai domain.

Install Mechanism

Instruction-only skill with no install spec or code — lowest-risk installation surface; nothing is downloaded or written to disk by an installer step.

Credentials

Only one credential is required (NEMO_TOKEN), which is appropriate for accessing the service. The SKILL.md also references reading or using a config path (~/.config/nemovideo/) and local install-path detection; these are reasonable for storing tokens or attribution but should be explicitly declared in registry metadata to avoid surprises.

Persistence & Privilege

The skill is not force-included (always:false) and does not request elevated platform privileges. It instructs normal session creation and cloud job management but does not modify other skills or system-wide configs.

Assessment

This skill appears to do what it says: it uploads your videos to nemovideo.ai and returns edited exports. Before installing, consider: (1) you must provide a NEMO_TOKEN (or let the skill request an anonymous 7‑day token from the service) — only use tokens you trust; avoid giving long-lived/high-privilege credentials. (2) The skill will read its own frontmatter and may probe common install/config paths (e.g., ~/.config/nemovideo/, ~/.clawhub/) to generate attribution headers — if you prefer, remove or inspect those local files first. (3) All uploads and edits occur on nemovideo.ai — review their privacy/terms before sending sensitive video/audio. (4) Because this is instruction-only, there is no installer writing code to your machine, but the agent will need filesystem access to read the skill metadata and to include attribution headers. If you trust nemovideo.ai and are comfortable with cloud processing of the media, the skill is proportionate; if you have sensitive material or untrusted tokens, do not install or provide credentials.

Getting Started

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

Try saying:

• "add my video clips"
• "export 1080p MP4"
• "add background music that matches the"

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.

Video Music — Add Music to Videos

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

Here's a typical use: you send a a 2-minute travel video clip, ask for add background music that matches the mood of my 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 music synced faster and more accurately.

Matching Input to Actions

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

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

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.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "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 → "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.