Ai Voiceover For Video Free

add video files into voiced-over videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use it for adding A...

Security Scan

The skill appears to do what it claims (cloud AI voiceover) and only asks for a single token, but it will upload your videos to an external, third‑party API and the metadata around config paths/tokens is inconsistent — verify the service and privacy before use.

Purpose & Capability

Name/description match the behavior: the skill sends video files to a cloud backend to generate voiceovers and needs a NEMO_TOKEN. However the skill metadata (SKILL.md frontmatter) lists a config path (~/.config/nemovideo/) while the registry summary shows no required config paths — this inconsistency should be clarified.

Instruction Scope

Runtime instructions will upload user video files and metadata to https://mega-api-prod.nemovideo.ai and keep session tokens; sending user media to an external service is expected for this purpose but is a privacy exposure. The skill also auto-creates an anonymous token by calling the auth endpoint if NEMO_TOKEN is absent, and it instructs the agent to derive headers from the skill file and detect install path — these actions are within scope but increase the amount of data the skill reads/sends (including install-path detection and possibly reading a local config path if present).

Install Mechanism

Instruction-only skill with no install spec or code files; nothing is downloaded or written by an install step, which is the lowest-risk install mechanism.

Credentials

The skill requests a single credential (NEMO_TOKEN) which is proportional to a cloud API integration. It will also obtain an anonymous token automatically if none exists. The earlier-mentioned metadata config path (~/.config/nemovideo/) suggests possible local credential/config file access — this was not listed in the registry's required config paths, creating a mismatch that should be explained.

Persistence & Privilege

The skill is not marked always:true, does not request system-wide changes, and does not attempt to modify other skills; it holds session state for the duration of operations which is expected for a service-backed skill.

What to consider before installing

This skill uploads your videos and related data to mega-api-prod.nemovideo.ai and uses a NEMO_TOKEN (it can create a short-lived anonymous token if you don’t provide one). Before installing or using it: 1) Confirm you trust the nemovideo.ai domain and review their privacy/terms (do they store or share uploaded media?). 2) Don’t use it with confidential or sensitive videos unless you’ve verified retention and access policies. 3) Ask the publisher to clarify the config path behavior (~/.config/nemovideo/) — will the skill read or write local files? 4) If you prefer, provide your own NEMO_TOKEN rather than relying on anonymous token creation and remove any tokens/config after use. 5) Because the skill source is unknown, prefer testing with non-sensitive sample videos first. If the maintainer or homepage is not provided, treat the service as unverified and proceed cautiously.

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 AI voiceover narrating"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

AI Voiceover for Video Free — Add AI Voice 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 AI voiceover narrating the on-screen content in English, 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 generate voiceover noticeably faster.

Matching Input to Actions

User prompts referencing ai voiceover for video free, 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 ai-voiceover-for-video-free, 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.

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 AI 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 AI voiceover narrating the on-screen content in English" → 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.