Ai Voice Generator

v1.0.0

Turn a 200-word product description script into 1080p voiced video clips just by typing what you need. Whether it's adding AI voiceovers to videos without re...

0· 66·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for francemichaell-15/ai-voice-generator.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Ai Voice Generator" (francemichaell-15/ai-voice-generator) from ClawHub.
Skill page: https://clawhub.ai/francemichaell-15/ai-voice-generator
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-voice-generator

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-voice-generator
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description match the declared runtime behavior: cloud voice synthesis, uploads, render/export flows. The single required env var (NEMO_TOKEN) is appropriate for an API-backed renderer. Inconsistency: the registry metadata lists no required config paths, but the SKILL.md frontmatter references a config path (~/.config/nemovideo/). Also the skill's source and homepage are unknown, so the vendor domain (mega-api-prod.nemovideo.ai) cannot be verified from metadata.
Instruction Scope
SKILL.md gives explicit API call flows (session creation, SSE, uploads, exports) and only asks the agent to use NEMO_TOKEN or to obtain an anonymous token from the vendor. It instructs uploading files via multipart (files=@/path) which implies reading user-supplied file paths but does not instruct reading arbitrary system files or unrelated credentials. It also asks to auto-detect an install path for an attribution header — this may require filesystem access to detect the agent's install location.
Install Mechanism
No install spec and no code files — instruction-only skill. This is low-risk from installation perspective because nothing is written to disk by an installer.
Credentials
Only NEMO_TOKEN is declared as required and as primaryEnv, which is proportional for a cloud API integration. Minor inconsistency: SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) while registry metadata earlier listed no config paths; it's reasonable if the skill stores session info there, but the mismatch is unexplained.
Persistence & Privilege
always:false and normal agent invocation. The skill does not request elevated platform privileges or to modify other skills. It will store session_id and use tokens for API calls, which is typical for an API-backed skill.
Scan Findings in Context
[no-findings] expected: Regex scanner found no code to analyze. That is expected for an instruction-only skill where the SKILL.md contains the runtime behavior.
Assessment
This skill appears to do what it says: it sends your text and uploads to a remote rendering service (mega-api-prod.nemovideo.ai) using a NEMO_TOKEN. Before installing, consider: 1) Do you trust the vendor domain and its privacy/security practices? The skill’s homepage and source are unknown. 2) Any files you upload (audio, images, video) and the token you provide will be transmitted to the remote API — avoid sending sensitive personal or corporate files. 3) The skill may store session data under ~/.config/nemovideo/ (SKILL.md mentions this); confirm whether you’re comfortable with that local storage. 4) Prefer testing with a throwaway/limited token or the anonymous-token flow before giving a long-lived credential. 5) The registry metadata and SKILL.md disagree about config paths — ask the publisher to clarify. If you’re unsure about trusting the remote service, do not use real sensitive data with this skill.

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

Runtime requirements

🎙️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97b06cksjcs2qe1dy7fgyk8as8509ef
66downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

Got text or script to work with? Send it over and tell me what you need — I'll take care of the AI voice synthesis.

Try saying:

  • "generate a 200-word product description script into a 1080p MP4"
  • "generate a natural-sounding voiceover in a female American English voice"
  • "adding AI voiceovers to videos without recording audio for content creators, marketers, educators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

AI Voice Generator — Generate Voiceovers for Videos

Drop your text or script in the chat and tell me what you need. I'll handle the AI voice synthesis on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 200-word product description script, ask for generate a natural-sounding voiceover in a female American English voice, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter text segments produce more natural-sounding speech pacing.

Matching Input to Actions

User prompts referencing ai voice generator, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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.

Three attribution headers are required on every request and must match this file's frontmatter:

HeaderValue
X-Skill-Sourceai-voice-generator
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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.

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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 JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Error Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

Common Workflows

Quick edit: Upload → "generate a natural-sounding voiceover in a female American English voice" → Download MP4. Takes 20-40 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 "generate a natural-sounding voiceover in a female American English voice" — concrete instructions get better results.

Max file size is 200MB. Stick to TXT, DOCX, SRT, MP4 for the smoothest experience.

Export as MP4 for widest compatibility across platforms and devices.

Comments

Loading comments...