Browser Lyric Video

Skip the learning curve of professional editing software. Describe what you want — sync the lyrics to the beat and display them on screen in the browser — an...

Security Scan

The skill's requirements and runtime instructions are internally consistent with a cloud-based lyric-video service: it only needs a single service token, calls the nemovideo.ai API, and has no install step or unrelated credential requests.

Purpose & Capability

Name/description (create lyric videos in-browser) match the declared requirement (NEMO_TOKEN) and the SKILL.md which exclusively describes API calls to nemovideo.ai for uploads, session creation, rendering, and export.

Instruction Scope

SKILL.md stays focused on the service workflow (obtain/authenticate token, create session, upload media, send SSE edits, poll export). It does not instruct reading unrelated system files or harvesting unrelated environment variables. It does instruct reading the frontmatter and detecting install path for attribution headers, which is reasonable for attribution but will require the agent to inspect its runtime context.

Install Mechanism

No install spec or downloads are present (instruction-only). Nothing will be written to disk by an installer; the skill expects the environment and will call remote APIs.

Credentials

Only NEMO_TOKEN is required and is the primary credential used to call the nemovideo.ai API, which is proportionate. Metadata also references a config path (~/.config/nemovideo/) and the skill proposes storing session_id/token for subsequent requests — this is reasonable but means the skill may read/write a small config area in the user profile for session persistence.

Persistence & Privilege

always:false and normal autonomy settings. The skill does ask to store session_id/token for requests, but it does not request persistent system-wide privileges or modify other skills' configuration.

Assessment

This skill appears to be what it claims: it uploads media and uses the nemovideo.ai backend to produce lyric videos. Before installing/using, consider: (1) the skill will send your audio/media files and tokens to https://mega-api-prod.nemovideo.ai — only proceed if you trust that service and understand its privacy/retention policy; (2) the skill may store a short-lived anonymous token and session_id in a config path under your home directory for convenience — if you prefer not to persist credentials, unset NEMO_TOKEN or clear the config after use; (3) avoid uploading sensitive or copyrighted material unless you accept cloud processing and storage; (4) if you need stronger guarantees, ask the skill author how tokens/session data are stored and how to revoke them. If any of these behaviors are unacceptable, do not enable the skill.

Getting Started

Share your audio files and I'll get started on lyric video creation. Or just tell me what you're thinking.

Try saying:

• "create my audio files"
• "export 1080p MP4"
• "sync the lyrics to the beat"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Browser Lyric Video — Create Lyric Videos in Browser

Drop your audio files in the chat and tell me what you need. I'll handle the lyric video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute MP3 song with lyrics text file, ask for sync the lyrics to the beat and display them on screen in the browser, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — uploading a timestamped lyrics file speeds up sync accuracy significantly.

Matching Input to Actions

User prompts referencing browser lyric video, 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: browser-lyric-video
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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 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)

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

Common Workflows

Quick edit: Upload → "sync the lyrics to the beat and display them on screen in the browser" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "sync the lyrics to the beat and display them on screen in the browser" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across YouTube, Instagram, and Spotify Canvas.