Ai Voiceovers

add video or script into voiced-over videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators, marketers, educators use it...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud-based voiceover service: it asks for one service token, uploads media to the stated API, and contains no install steps or unrelated credential demands.

Purpose & Capability

The skill's name/description (AI voiceovers for videos) aligns with the declared requirement (NEMO_TOKEN) and the SKILL.md's API endpoints for uploads, SSE, session creation, and exports. The only minor inconsistency: the registry metadata earlier stated 'no required config paths' while the SKILL.md frontmatter references ~/.config/nemovideo/ — this is plausible (a local config cache) but should be clarified.

Instruction Scope

The instructions are focused on creating a session, uploading media, using SSE for edits, and polling for exports — all expected for a cloud rendering service. Important user-impact note: the workflow explicitly uploads user media (videos, scripts) and sends them to https://mega-api-prod.nemovideo.ai, so private or sensitive content will be transmitted to the remote service. The skill also instructs obtaining an anonymous token by POSTing to the service if NEMO_TOKEN is absent — expected but worth being aware of.

Install Mechanism

No install spec or code files are present; this is an instruction-only skill (lowest install risk). Nothing is downloaded or written by an installer according to the provided metadata.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportionate to calling the backend API. The SKILL.md frontmatter also references a config path (~/.config/nemovideo/) that could permit reading local configuration; the registry metadata earlier listed no config paths — this mismatch should be resolved. Aside from the token and optional local config, the skill does not request unrelated secrets.

Persistence & Privilege

The skill does not request always:true, does not install persistent components, and does not modify other skills or global agent settings. It creates ephemeral sessions with the remote service, which is normal for this kind of integration.

Assessment

This skill appears to do what it says: it uploads your video/script to a cloud rendering service (https://mega-api-prod.nemovideo.ai) and requires a NEMO_TOKEN to operate (it can get a short-lived anonymous token if none is provided). Before installing, consider: 1) privacy — media and scripts (possibly sensitive) will be uploaded to the remote service; don't use it for content you cannot share externally. 2) tokens/config — confirm you trust the service with NEMO_TOKEN and check whether a local config (~/.config/nemovideo/) will be read; the registry listing and SKILL.md disagree on config-path requirements. 3) domain legitimacy — verify the API domain and that HTTPS is enforced. There is no installer or extra credential request, so risk is limited to data you send to the remote API. If you need stronger guarantees (on-prem processing, no uploads), do not enable this skill.

Getting Started

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

Try saying:

• "add my video or script"
• "export 1080p MP4"
• "add a natural-sounding male voiceover reading"

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 Voiceovers — Add Voice Narration 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 male voiceover reading my script in English — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter scripts sync more accurately — split long narrations into sections for better timing control.

Matching Input to Actions

User prompts referencing ai voiceovers, 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	ai-voiceovers
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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-sounding male voiceover reading my script 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 male voiceover reading my script 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.