Voiceover For Video

add video files into narrated video files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators, marketers, educators use it fo...

Security Scan

The skill's runtime instructions mostly match a cloud-based voiceover service, but there are provenance and metadata inconsistencies and it asks the agent to upload user videos to an external API operated by an unknown source — review before installing or sending sensitive files.

Purpose & Capability

The skill name/description (add AI narration to videos) aligns with the declared requirement for a service token (NEMO_TOKEN) and the SKILL.md API workflow. However, there's an inconsistency: registry metadata lists no required config paths while the SKILL.md frontmatter/metadata references a config path (~/.config/nemovideo/). That mismatch is unexplained and could affect where session or tokens are stored.

Instruction Scope

SKILL.md directs the agent to obtain/use a NEMO_TOKEN (or generate an anonymous token), create sessions, upload user video files, open an SSE chat stream, poll export endpoints, and return download URLs. Those steps are coherent for a cloud render service. Notably, the instructions require uploading user-supplied video files to https://mega-api-prod.nemovideo.ai and saving session_id — this is expected for the stated purpose but represents user data leaving the host and should be considered a privacy risk for sensitive content.

Install Mechanism

Instruction-only skill with no install spec and no code files. Lowest install risk — nothing is downloaded or written by an installer. Runtime network calls are described in SKILL.md.

Credentials

Only NEMO_TOKEN is declared as required, which is reasonable for authenticating to the described API. The SKILL.md also describes generating an anonymous token if none is present. The earlier-mentioned config path in the frontmatter (~/.config/nemovideo/) is not justified elsewhere and is inconsistent with the registry summary claiming no required config paths — this is disproportionate/unexplained.

Persistence & Privilege

always:false and normal autonomous invocation. The skill instructs saving session_id for ongoing jobs (expected). It does not request system-wide privileges or modifications to other skills; nothing indicates elevated platform privileges.

What to consider before installing

This skill will upload any video you provide to an external API (mega-api-prod.nemovideo.ai) and requires a NEMO_TOKEN (or will obtain an anonymous token). Before installing or using it: 1) Verify you trust the service owner (no homepage or known source is provided). 2) Do not send sensitive or confidential videos to the service. 3) Be aware the skill will persist session_id and may store tokens in its config path (frontmatter references ~/.config/nemovideo/ even though registry metadata omitted it) — confirm where data and tokens are saved. 4) Prefer skills with a known homepage, documented privacy/retention policy, or an official provider. If you must use it, create an anonymous/limited token and avoid uploading sensitive content.

Getting Started

Share your video files and I'll get started on AI voiceover generation. Or just tell me what you're thinking.

Try saying:

• "add my video files"
• "export 1080p MP4"
• "add a natural English voiceover narrating"

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.

Voiceover for Video — Add AI Narration to Videos

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

Here's a typical use: you send a a 2-minute product demo video, ask for add a natural English voiceover narrating the on-screen actions, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 60 seconds process faster and give more accurate voice sync.

Matching Input to Actions

User prompts referencing voiceover for 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.

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	voiceover-for-video
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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 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 "add a natural English voiceover narrating the on-screen actions" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best compatibility across platforms.

Common Workflows

Quick edit: Upload → "add a natural English voiceover narrating the on-screen actions" → 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.