Ai 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 functionality (cloud voiceover) matches the network calls it instructs, but there are internal inconsistencies about required environment/config and it asks the agent to expose local install metadata to a third‑party API — review before installing or sending private video content.

Purpose & Capability

The skill claims to add AI voiceover to uploaded videos and instructs the agent to upload files and call a nemo-video backend — these actions are coherent with the described purpose. However, registry metadata lists no config paths while the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) and marks NEMO_TOKEN as required while the runtime instructions include an anonymous-token fallback. Those inconsistencies mean the declared requirements don't fully match the runtime behavior.

Instruction Scope

Instructions direct the agent to upload user video files to https://mega-api-prod.nemovideo.ai, request tokens, create sessions, stream SSE, poll render status, and include attribution headers. They also say to read the skill's YAML frontmatter to set X-Skill-Source/Version and to detect install path (e.g., ~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform. Reading install path and including that derived platform header will expose local environment/location metadata to the remote API. The skill also promises to generate an anonymous token if NEMO_TOKEN is absent — but the registry marks NEMO_TOKEN required. These scope items (reading local paths and emitting them externally) are not strictly necessary for voiceover and represent privacy/leakage concerns.

Install Mechanism

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

Credentials

The only declared environment variable is NEMO_TOKEN (primaryEnv). That is reasonable for a backend service. But SKILL.md allows obtaining an anonymous token if NEMO_TOKEN is not present, which conflicts with the registry declaring it required. The skill also requests and will transmit metadata derived from local paths and frontmatter as headers, which can leak information about the user's environment — not strictly necessary for core functionality.

Persistence & Privilege

The skill is not always:true and doesn't request to modify other skills or system-wide settings. It does not ask for persistent installation privileges. Autonomous invocation is enabled by default (normal) but not combined with other high-risk patterns here.

What to consider before installing

This skill will upload your video files to mega-api-prod.nemovideo.ai for cloud processing and normally uses an NEMO_TOKEN if provided; if it isn't present the skill will call the service to obtain an anonymous token. Before installing or sending sensitive videos: 1) confirm you trust nemo‑video as the backend (privacy/retention policy, who can access uploaded videos); 2) note the skill will include attribution headers that may reveal local install paths/platform (it reads YAML frontmatter and detects install directories) — consider whether you want that metadata sent; 3) the registry metadata conflicts with the SKILL.md (config path declaration and whether NEMO_TOKEN is truly required), so prefer to use an ephemeral/anonymous token or test with non-sensitive data first; 4) because the skill source is unknown and there is no homepage, exercise caution and favor services with clear provenance and privacy terms.

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-sounding voiceover narrating the"

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.

AI Voiceover for Video — Generate and Add Video Narration

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-sounding voiceover narrating the on-screen content in English, and about 30-90 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 generate voiceover faster and let you fine-tune the script more easily.

Matching Input to Actions

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

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

• X-Skill-Source: ai-voiceover-for-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.

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 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 "add a natural-sounding voiceover narrating the on-screen content in English" — 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 platforms and devices.

Common Workflows

Quick edit: Upload → "add a natural-sounding voiceover narrating the on-screen content in English" → Download MP4. Takes 30-90 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.