Ai Video Editor Music Sync

Skip the learning curve of professional editing software. Describe what you want — sync the video cuts to the beat drops in my music track — and get beat-syn...

Security Scan

The skill's requests and runtime instructions are generally consistent with a cloud-based video editing service: it expects a single service token, documents API endpoints to upload media and request renders, and has no install step — but there are a few minor inconsistencies and privacy implications you should be aware of before use.

Purpose & Capability

The skill is a cloud video-editing/music-sync frontend and asks for a service token (NEMO_TOKEN) and network access to nemovideo.ai — this aligns with its stated purpose. No unrelated credentials (AWS, GitHub, etc.) are requested. Note: the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths, creating a small inconsistency about whether the skill will read local config.

Instruction Scope

The instructions tell the agent to check for NEMO_TOKEN, and if absent, call an anonymous-token API to obtain one, then create sessions, upload media, stream SSE chat, and poll export status. All of these operations are directly tied to cloud rendering and file uploads and are expected for the service. Important privacy note: user media and metadata are uploaded to a third-party endpoint (mega-api-prod.nemovideo.ai). The skill explicitly instructs not to expose tokens, but it does direct outbound network calls and transfers of user media — which is expected but worth confirming with the user.

Install Mechanism

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

Credentials

Only a single environment variable (NEMO_TOKEN) is required, which is proportional for a cloud API client. However, instructions include an automatic anonymous-token request workflow (POST to /api/auth/anonymous-token) that will create and use a token if none is present — this behavior means the skill may obtain credentials on behalf of the user and use them for up to 7 days/100 credits. Also note the discrepancy between registry metadata (no config paths) and SKILL.md frontmatter (mentions ~/.config/nemovideo/) — clarify whether local config will be read or written.

Persistence & Privilege

always is false and the skill does not request persistent system-wide privileges or to modify other skills. Normal autonomous invocation is allowed (disable-model-invocation=false), which is expected for skills of this type.

Assessment

This skill sends your uploaded media and API calls to a third-party service (mega-api-prod.nemovideo.ai) to perform rendering. Before installing or using it: 1) Confirm you trust the nemovideo.ai service and are comfortable uploading the files you intend to edit (do not upload sensitive or confidential media unless you have explicit agreement). 2) Decide whether to provide your own NEMO_TOKEN (from a trusted account) or allow the skill to request an anonymous token — the skill will call the anonymous-token endpoint automatically if no token is present, which creates a short-lived credential and consumes free credits. 3) Ask the author/owner for clarification about the apparent config-path mention (~/.config/nemovideo/) — verify whether the skill will read or write local config. 4) Check billing/credits and retention policy on the service (who keeps the uploads, how long). 5) If you need stronger privacy guarantees, do not install or use this skill, or only use it with non-sensitive test media.

Getting Started

Got video clips audio to work with? Send it over and tell me what you need — I'll take care of the AI music sync editing.

Try saying:

• "sync a 60-second travel montage and a background music track into a 1080p MP4"
• "sync the video cuts to the beat drops in my music track"
• "syncing video cuts and transitions to music beats automatically for content creators and social media editors"

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 Editor Music Sync — Sync Video Cuts to Music

Send me your video clips audio 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 montage and a background music track, type "sync the video cuts to the beat drops in my music track", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: tracks with a strong consistent beat sync more accurately than ambient or variable-tempo music.

Matching Input to Actions

User prompts referencing ai video editor music sync, 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.

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

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

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 "sync the video cuts to the beat drops in my music track" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WAV for the smoothest experience.

Export as MP4 for widest compatibility across social platforms and video players.

Common Workflows

Quick edit: Upload → "sync the video cuts to the beat drops in my music track" → 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.