Video Editing With 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 "edit...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud video-editing service: it needs a NEMO_TOKEN and uploads videos to a remote API; nothing requests unrelated credentials or writes code to disk.

Purpose & Capability

The skill is a cloud video-editing workflow and explicitly requires/uses a NEMO_TOKEN to call mega-api-prod.nemovideo.ai, which is consistent with its description. Minor inconsistency: the YAML frontmatter in SKILL.md lists a config path (~/.config/nemovideo/) while the registry metadata above the file indicated no required config paths. This is likely a metadata mismatch but does not change the core capability.

Instruction Scope

The SKILL.md instructs the agent to (a) check for NEMO_TOKEN, (b) if missing, call an anonymous-token endpoint to obtain one, (c) create a session, upload files, and read SSE responses. All of these are within the stated purpose (remote rendering). The instructions also describe deriving attribution headers and 'detecting the install path' to set X-Skill-Platform — that implies the agent may inspect its install path or environment to choose a header value, which is reasonable but broader than strictly necessary for video editing.

Install Mechanism

No install spec or code is provided (instruction-only). Nothing is downloaded or written to disk by an installer in the skill bundle itself.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv). The SKILL.md outlines a flow to auto-acquire an anonymous NEMO_TOKEN if none is present, so requiring the token up-front is somewhat inconsistent but not harmful. No unrelated secrets or multiple credentials are requested.

Persistence & Privilege

always:false and default autonomous invocation are set (normal). The skill asks the agent to keep session_id in memory for job operations but does not request permanent system-level privileges or to modify other skills.

Assessment

This skill uploads your video files to a third-party cloud service (mega-api-prod.nemovideo.ai) and uses a NEMO_TOKEN (which the skill will try to obtain anonymously if you don't provide one). Before installing or using it: 1) Confirm you are comfortable having your videos processed by that external service and review its privacy/TOS if available. 2) Note the token the skill obtains is temporary (SKILL.md says 100 free credits, 7-day expiry); check whether tokens are stored persistently by your agent environment. 3) The SKILL.md contains a small metadata mismatch (declared config path vs. registry metadata) — not a security break but worth being aware of. 4) Avoid uploading sensitive content in videos. 5) If you want tighter control, supply your own NEMO_TOKEN (and revoke it later) or test with non-sensitive files first.

Getting Started

Send me your video clips and I'll handle the AI editing with music. Or just describe what you're after.

Try saying:

• "edit a 2-minute travel video clip into a 1080p MP4"
• "edit my video and add free background music that matches the mood"
• "editing videos with royalty-free background music for content creators"

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 Editing with Free Music — Edit Videos and Add Free Music

Send me your video clips and describe the result you want. The AI editing with music runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute travel video clip, type "edit my video and add free background music that matches the mood", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process faster and sync music more accurately.

Matching Input to Actions

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

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-editing-with-free-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).

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.

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

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.

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 "edit my video and add free background music that matches the mood" — 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 → "edit my video and add free background music that matches the mood" → Download MP4. Takes 1-2 minutes 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.