Free Unified Video Lyrics

Skip the learning curve of professional editing software. Describe what you want — sync song lyrics as animated captions across all scenes in one unified sty...

Security Scan

The skill's instructions, required environment variable (NEMO_TOKEN), and API calls are coherent with a cloud-based video-lyrics syncing service, but there are small metadata inconsistencies and you should confirm you trust the external API before uploading videos or supplying a long-lived token.

Purpose & Capability

The name and description describe cloud-based lyric-sync and the SKILL.md instructs the agent to call nemovideo.ai endpoints, upload videos, create sessions, and export renders — these actions align with the stated purpose. Minor inconsistency: the registry metadata reported no required config paths, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) which is not referenced elsewhere in the instructions.

Instruction Scope

Runtime instructions are focused on session creation, uploading video/audio, SSE message handling, and export polling — all expected. They explicitly use an environment token (NEMO_TOKEN) or describe obtaining an anonymous token from the API. The doc also instructs setting attribution headers and detecting an install path to set an X-Skill-Platform header; that implies reading or inferring installation location (a small scope creep) although the skill does not explicitly instruct reading arbitrary files.

Install Mechanism

No install spec or code files are present (instruction-only). Nothing will be downloaded or written by an installer as part of the skill bundle.

Credentials

Only one credential (NEMO_TOKEN) is declared and used, which is proportionate for a cloud rendering API. The SKILL.md also mentions a config path in its metadata (~/.config/nemovideo/), which is not used elsewhere — this mismatch should be clarified. The skill's described anonymous-token flow provides an option to obtain a short-lived token, which is safer than asking for a permanent account token.

Persistence & Privilege

The skill is not always-enabled and does not request elevated or persistent platform privileges. It asks the agent to store session_id for the session lifecycle (ephemeral), which is reasonable for its function.

Assessment

This skill appears to do what it says: it uploads video/audio and calls a nemovideo.ai API to produce lyric-synced exports. Before installing or using it: (1) confirm you trust the nemovideo.ai service and are comfortable uploading the videos you plan to process; (2) avoid providing high-privilege or long-lived account tokens — prefer the anonymous-token flow described in the SKILL.md or use a dedicated limited token; (3) ask the skill author to clarify the config-path metadata discrepancy (~/.config/nemovideo/) and what, if anything, the skill will read from disk; (4) review any privacy/retention policy for uploaded media; and (5) do not use this skill with sensitive or regulated video/audio without explicit assurances about storage, retention, and access controls.

Getting Started

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

Try saying:

• "generate a 3-minute music video in MP4 format into a 1080p MP4"
• "sync song lyrics as animated captions across all scenes in one unified style"
• "adding synchronized lyrics across a full music video in one consistent style for musicians and content creators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Free Unified Video Lyrics — Sync Lyrics Across Full Videos

This tool takes your video files and runs AI lyrics sync through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute music video in MP4 format and want to sync song lyrics as animated captions across all scenes in one unified style — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: uploading a clean audio track alongside your video improves lyric sync accuracy.

Matching Input to Actions

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

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

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

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.

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.

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

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)

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

Common Workflows

Quick edit: Upload → "sync song lyrics as animated captions across all scenes in one unified style" → 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 "sync song lyrics as animated captions across all scenes in one unified style" — 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.