Ai Video Editing With Music

Skip the learning curve of professional editing software. Describe what you want — add background music and auto-sync cuts to the beat — and get music-synced...

Security Scan

The skill's declared purpose (cloud video editing) matches most of its instructions, but there are inconsistencies around required config paths and token handling and it will upload user video files to a third‑party service — review before installing or sending sensitive content.

Purpose & Capability

The skill is advertised as a cloud-based AI video editor and the SKILL.md describes API endpoints, uploads, rendering, and exports that fit that purpose. However, registry metadata earlier listed no config paths while the SKILL.md frontmatter requires ~/.config/nemovideo/ — this mismatch should be resolved. Declaring NEMO_TOKEN as required is also inconsistent with runtime instructions that can obtain an anonymous token if none is present.

Instruction Scope

The instructions direct the agent to upload user video files to a remote host (mega-api-prod.nemovideo.ai), create sessions, use SSE streams, and include specific attribution headers. Uploading arbitrary user files to an external service is expected for this functionality but is a high‑privacy operation and should be explicitly authorized by the user. The SKILL.md also instructs generation of a client UUID and automatic acquisition/storage of an anonymous token, implying the agent will perform network calls and manage credentials. It references file upload via multipart with local file paths (e.g., -F "files=@/path"), which presumes the agent can read local file paths — ensure this matches your agent environment and privacy policy.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest risk from install mechanics (no downloads or executed installers).

Credentials

Only one credential (NEMO_TOKEN) is declared, which is proportionate to a cloud API client. However, SKILL.md will obtain an anonymous token if NEMO_TOKEN is missing, so declaring it as strictly required is misleading. The frontmatter also lists a config path (~/.config/nemovideo/) that the registry summary omitted — that path would grant the skill access to a user config directory and should be justified. Verify how and where tokens are stored (env vs config file) and whether tokens persist beyond the session.

Persistence & Privilege

always:false (not force-included) and normal autonomous invocation flags. The skill does instruct the agent to retain session_id for job lifecycle handling, which is appropriate for render jobs but not an elevated platform privilege.

Scan Findings in Context

[no_code_files] expected: The regex scanner found nothing because this is an instruction-only skill. That is expected here, but it means runtime behavior comes entirely from SKILL.md instructions (network calls, file uploads).

What to consider before installing

This skill will send any video you give it to mega-api-prod.nemovideo.ai for cloud editing and will create or store an anonymous token if you don't provide one. Before installing or using it: (1) Confirm you trust the remote service and are willing to upload the videos (do not use for sensitive footage without vendor assurances). (2) Ask how the NEMO_TOKEN is stored (environment vs ~/.config/nemovideo/); the SKILL.md and registry metadata disagree. (3) Verify your agent runtime will only send files you explicitly provide and will not expose other local files. (4) Prefer skills with an identified source/homepage or inspect network calls in a controlled environment first. If any of the above are unacceptable or unclear, do not install or invoke the skill.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "add background music and auto-sync cuts"

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.

AI Video Editing with Music — Edit Videos with Synced Music

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

A quick example: upload a 60-second travel video clip, type "add background music and auto-sync cuts to the beat", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds sync to music beats more accurately.

Matching Input to Actions

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

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-video-editing-with-music
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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.

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)

Common Workflows

Quick edit: Upload → "add background music and auto-sync cuts to the beat" → 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 background music and auto-sync cuts to the beat" — 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.