Unified Video Lyrics Online

Turn a 3-minute music video file into 1080p lyrics-synced videos just by typing what you need. Whether it's adding timed lyrics to music videos online or qui...

Security Scan

The skill's requirements and runtime instructions are generally consistent with a cloud-based video/lyrics rendering service, but there are small metadata inconsistencies and no publisher/homepage that reduce confidence—review the remote endpoint and token use before installing.

Purpose & Capability

The name/description match the actions in SKILL.md (upload video, create session, render/export). Requesting a NEMO_TOKEN as the primary credential is appropriate for a hosted service. Minor inconsistency: the top-level registry metadata lists no required config paths, but the skill frontmatter advertises a config path (~/.config/nemovideo/) — this mismatch should be clarified.

Instruction Scope

Instructions focus on connecting to the remote API, creating sessions, uploading video files, reading SSE events, polling render status, and returning download URLs — all expected for a cloud render/lyrics-sync service. The SKILL.md does not instruct reading unrelated local files or unrelated environment variables.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest-risk install mechanism (nothing written to disk by the skill itself).

Credentials

Only a single credential (NEMO_TOKEN) is declared and used, which is proportionate. However, the frontmatter references a local config path (~/.config/nemovideo/) which was not declared elsewhere in registry metadata; if the skill actually reads that path at runtime it would expand its scope and should be disclosed. The skill also instructs emitting attribution headers derived from install path detection (reading install path metadata) — minor but worth noting.

Persistence & Privilege

The skill is not forcing persistent inclusion (always:false) and does not request elevated system privileges. It does not instruct modifying other skills or system-wide config. Autonomous invocation remains allowed (platform default) but does not combine here with other high-risk flags.

Assessment

This skill appears to do what it says: it uploads videos to a remote render service and returns synced-lyrics videos. Before installing or using it, consider: (1) the service endpoint (https://mega-api-prod.nemovideo.ai) will receive your video/audio — confirm you trust the operator and understand the privacy policy; (2) the NEMO_TOKEN grants API access tied to your account or to an anonymous starter token — avoid putting long-lived or highly-privileged credentials here; (3) the frontmatter mentions a local config path (~/.config/nemovideo/) that the registry metadata did not — ask the publisher whether the skill reads local config files; (4) there is no homepage or publisher information listed — prefer skills from known vendors or ask the author for identity and documentation; (5) because this is instruction-only, static scanners had nothing to analyze — network calls and data uploads are performed at runtime, so review endpoints and headers. If you proceed, consider testing with non-sensitive videos and a throwaway/anonymous token first.

Getting Started

Send me your video with audio and I'll handle the AI lyrics sync. Or just describe what you're after.

Try saying:

• "add a 3-minute music video file into a 1080p MP4"
• "sync song lyrics as on-screen text timed to the vocals"
• "adding timed lyrics to music videos online for musicians and content creators"

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.

Unified Video Lyrics Online — Sync Lyrics to Videos Online

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

A quick example: upload a 3-minute music video file, type "sync song lyrics as on-screen text timed to the vocals", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: clean audio with minimal background noise improves lyric sync accuracy.

Matching Input to Actions

User prompts referencing unified video lyrics online, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is unified-video-lyrics-online, 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).

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

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)

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "sync song lyrics as on-screen text timed to the vocals" — 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 streaming and social platforms.

Common Workflows

Quick edit: Upload → "sync song lyrics as on-screen text timed to the vocals" → 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.