Ai Voiceover Free

Turn a 2-minute product demo video with no audio into 1080p voiced-over videos just by typing what you need. Whether it's adding AI-generated narration to si...

Security Scan

The skill's declared purpose (cloud AI voiceover) aligns with its network calls and single required credential, but metadata and runtime instructions ask the agent to read local paths and a config location that aren't declared in the registry, the source is unknown, and the skill will upload user video/audio to an external API — these inconsistencies and missing provenance warrant caution.

Purpose & Capability

Name/description (AI voiceover) match the actions described: creating sessions, uploading video, generating renders, and downloading results. Requesting a single service token (NEMO_TOKEN) is proportionate. However, the SKILL.md metadata lists a config path (~/.config/nemovideo/) and instructs detecting install paths at runtime even though the registry metadata said no required config paths — an incoherence that should be explained by the author.

Instruction Scope

Instructions include network calls to an external API (expected) and explicit guidance to upload files and poll session state (expected). They also instruct reading the skill's YAML frontmatter and detecting install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) and reference a local config path (~/.config/nemovideo/). Reading those filesystem locations is outside pure voice-generation logic and could access user-local state; the skill does not document why those paths are needed or what will be read from them.

Install Mechanism

There is no install spec and no code files (instruction-only). That minimizes on-disk code installation risk. All runtime activity is network/API driven.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which is reasonable for an API-backed voiceover service. The SKILL.md also describes automatically obtaining an anonymous token if none is present. However, the SKILL.md metadata mentions a config path that could contain additional tokens/configuration not declared in the registry; this mismatch is unexplained and worth clarifying.

Persistence & Privilege

The skill is not always-enabled and does not request elevated or persistent platform privileges. It does perform autonomous network interactions when invoked normally, which is standard for skills. It does not attempt to modify other skill configs in the provided instructions.

What to consider before installing

This instruction-only skill appears to implement an online AI voiceover service and will upload videos or URLs to an external API (https://mega-api-prod.nemovideo.ai). Before installing or using it: 1) Note the source is unknown and there's no homepage or code to inspect — ask the author for provenance, privacy policy, and source code. 2) Understand it will send your media to an external service; avoid uploading sensitive videos until you verify their data retention and sharing policies. 3) Ask why the SKILL.md mentions reading ~/.config/nemovideo/ and detecting install paths — request a clear justification for any filesystem reads and confirmation which exact paths will be accessed. 4) Prefer providing a disposable/limited NEMO_TOKEN or use the anonymous flow if you don't trust a persistent token. 5) If you need stronger assurance, request an explicit list of API endpoints used and a signed privacy/security statement from the publisher.

Getting Started

Ready when you are. Drop your video or script here or describe what you want to make.

Try saying:

• "add a 2-minute product demo video with no audio into a 1080p MP4"
• "add a natural-sounding AI voice reading my script over this video"
• "adding AI-generated narration to silent videos for content creators, marketers, educators"

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 Free — Add AI Voice to Videos

This tool takes your video or script and runs AI voiceover generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute product demo video with no audio and want to add a natural-sounding AI voice reading my script over this video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter scripts under 60 seconds generate the most natural-sounding results.

Matching Input to Actions

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

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

• X-Skill-Source: ai-voiceover-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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.

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

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 → "add a natural-sounding AI voice reading my script over this video" → 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 "add a natural-sounding AI voice reading my script over this video" — 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.