Ai Voiceover For

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — add a natural AI voiceover in English for my product walkthrough video — a...

⭐ 0· 58·0 current·0 all-time

by@whitejohnk-26

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for whitejohnk-26/ai-voiceover-for.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Ai Voiceover For" (whitejohnk-26/ai-voiceover-for) from ClawHub.
Skill page: https://clawhub.ai/whitejohnk-26/ai-voiceover-for
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install ai-voiceover-for

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-voiceover-for

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Suspicious

medium confidence

ℹ

Purpose & Capability

The name, description and runtime instructions align with a remote AI video voiceover service and the single required credential (NEMO_TOKEN) is consistent with that purpose. However, registry metadata reported no required config paths while the SKILL.md frontmatter lists a config path (~/.config/nemovideo/), and there's no homepage or source repository to verify provenance.

✓

Instruction Scope

SKILL.md stays within the expected scope: it describes authenticating (using NEMO_TOKEN or an anonymous token), creating sessions, uploading media, requesting renders, polling status and handling SSE. It does not instruct reading unrelated system files or grabbing other environment variables. One operational detail to note: it requires building attribution headers and 'auto-detecting' an install path for X-Skill-Platform which may require access to runtime metadata.

✓

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That minimizes install-time risk.

ℹ

Credentials

Only NEMO_TOKEN is declared as required, which is appropriate for a third‑party API. But the SKILL.md frontmatter references a config path (~/.config/nemovideo/) not shown in the registry metadata; if the implementation reads that path it could access local configuration. Also the skill will use any NEMO_TOKEN present in the agent environment — ensure that token belongs to this service and not another higher-privileged credential.

✓

Persistence & Privilege

The skill is not marked always:true and does not request permanent platform-wide privileges. It is user-invocable and may run autonomously (default), which is expected for skills.

Scan Findings in Context

[NO_CODE_FILES_FOR_SCAN] expected: The regex scanner had no files to analyze because the skill is instruction-only (SKILL.md). This is expected but leaves runtime behavior unverified by static analysis.

What to consider before installing

This skill appears to implement a remote voiceover service and needs a NEMO_TOKEN API token (or will mint a short-lived anonymous token). Before installing: 1) Verify the skill's origin (there's no homepage or repo listed). 2) Don't provide a high-value or unrelated token — make sure NEMO_TOKEN is for this service only; prefer using the anonymous token flow if you want limited exposure. 3) Ask the publisher whether the skill will read ~/.config/nemovideo/ (the SKILL.md mentions it, registry metadata does not). 4) Confirm privacy/retention for uploaded videos and whether downloads are protected. 5) If you need higher assurance, request the skill's source or a homepage and/or require a signed release or official provider listing before use.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎙️ Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk973mr2tay2z1b1zcwbta4w4js85317d

58downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

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 into a 1080p MP4"
"add a natural AI voiceover in English for my product walkthrough video"
"adding AI-generated voiceovers to silent or muted 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 For — Add AI Voice to Videos

Send me your video or script and describe the result you want. The AI voiceover generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute product demo video, type "add a natural AI voiceover in English for my product walkthrough video", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter scripts sync more accurately to video timing.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
`/api/tasks/me/with-session/nemo_agent`	POST	Start a new editing session. Body: `{"task_name":"project","language":"<lang>"}`. Returns `session_id`.
`/run_sse`	POST	Send a user message. Body includes `app_name`, `session_id`, `new_message`. Stream response with `Accept: text/event-stream`. Timeout: 15 min.
`/api/upload-video/nemo_agent/me/<sid>`	POST	Upload a file (multipart) or URL.
`/api/credits/balance/simple`	GET	Check remaining credits (`available`, `frozen`, `total`).
`/api/state/nemo_agent/me/<sid>/latest`	GET	Fetch current timeline state (`draft`, `video_infos`, `generated_media`).
`/api/render/proxy/lambda`	POST	Start export. Body: `{"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}`. Poll status every 30s.

Accepted file types: 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-voiceover-for`
`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.

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

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.

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

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)

Common Workflows

Quick edit: Upload → "add a natural AI voiceover in English for my product walkthrough 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 AI voiceover in English for my product walkthrough 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.

Comments

Loading comments...