Royalty Free Music

Get music-backed videos ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "add...

Security Scan

The skill's requirements and runtime instructions are coherent for a cloud video-rendering service: it needs a single service token (NEMO_TOKEN) and calls nemovideo.ai endpoints to upload and render videos; no installs or unrelated credentials are requested.

Purpose & Capability

Name and description match the behavior in SKILL.md: the skill uploads video, requests a session/token, posts render jobs, and returns a download URL. Requiring a single service credential (NEMO_TOKEN) is proportionate for a cloud API-based renderer.

Instruction Scope

Instructions are explicit about network calls to https://mega-api-prod.nemovideo.ai, SSE handling, upload endpoints, and export polling; they also ask the agent to read the skill's YAML frontmatter and detect install path (~/.clawhub/, ~/.cursor/skills/) for attribution. Reading its own SKILL.md and checking a few well-known install paths is reasonable, but it does involve limited filesystem access (skill file + optional install-path probes). The runtime instructions do not ask for unrelated system files or other credentials.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That reduces risk.

Credentials

Only one environment credential is required: NEMO_TOKEN (primaryEnv). The skill also documents obtaining an anonymous token if none is present. One minor inconsistency: the SKILL.md frontmatter lists a configPaths entry (~/.config/nemovideo/), but the registry-level Requirements summary showed no required config paths—this mismatch is likely benign but should be clarified.

Persistence & Privilege

The skill is not always-enabled, does not request elevated or system-wide persistence, and does not attempt to modify other skills. It can be invoked autonomously (platform default), which is expected for skills of this type and is not by itself a red flag.

Assessment

This skill appears to do what it claims: it uploads user video to a nemovideo.ai backend, uses a single service token (NEMO_TOKEN) or an anonymous token it obtains, and returns rendered MP4s. Before installing/use: (1) Confirm you trust https://mega-api-prod.nemovideo.ai and review its privacy/retention policy because you will be uploading video (up to 500MB). (2) Prefer providing a purpose-limited token (not a long-lived privileged secret) and rotate it if possible. (3) Note the skill may read its own SKILL.md and check common install paths and ~/.config/nemovideo/ for attribution/config—if you have sensitive files in those locations, review them first. (4) The registry metadata and the SKILL.md have a small mismatch about config paths—ask the publisher to clarify if the skill will read ~/.config/nemovideo/. Finally, because this skill uploads content to an external service, test with non-sensitive sample videos first.

Getting Started

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

Try saying:

• "add a 2-minute product demo video into a 1080p MP4"
• "add upbeat background music that fits the mood and is safe for YouTube monetization"
• "adding copyright-free background music to videos for YouTubers, content creators, marketers"

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.

Royalty Free Music — Add Copyright-Free Music to Videos

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

Here's a typical use: you send a a 2-minute product demo video, ask for add upbeat background music that fits the mood and is safe for YouTube monetization, 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 video clips allow faster music syncing and preview rendering.

Matching Input to Actions

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

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

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

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

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.

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 "add upbeat background music that fits the mood and is safe for YouTube monetization" — 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, TikTok, and Instagram.

Common Workflows

Quick edit: Upload → "add upbeat background music that fits the mood and is safe for YouTube monetization" → 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.