Ai Audio Tts

v1.0.0

convert text or script into voiced video output with this skill. Works with MP4, MOV, TXT, DOCX files up to 200MB. content creators, marketers use it for add...

0· 69·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 whitejohnk-26/ai-audio-tts.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Ai Audio Tts" (whitejohnk-26/ai-audio-tts) from ClawHub.
Skill page: https://clawhub.ai/whitejohnk-26/ai-audio-tts
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-audio-tts

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-audio-tts
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name/description (text→voice/video) match the runtime instructions (endpoints for uploads, render, credits, SSE). The only mismatch: the registry metadata lists no required config paths but the SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/). This is likely benign (informational) but is an inconsistency worth noting.
Instruction Scope
SKILL.md confines actions to the nemovideo API: obtaining/using a NEMO_TOKEN (or creating an anonymous token), creating sessions, uploading user files, streaming events, polling render status, and returning download URLs. It does not instruct reading unrelated system credentials or roaming the filesystem beyond optional install-path detection. Important: it will upload user-provided files (video/audio/docs) to the remote service — this is expected for the skill but is a data-sharing/privacy consideration.
Install Mechanism
No install spec and no code files — instruction-only skill. That minimizes local disk footprint and reduces supply-chain risk. Network calls to a third-party API are required at runtime (standard for SaaS integration).
Credentials
The skill only requires a single credential (NEMO_TOKEN) which is appropriate for an API-backed TTS/rendering service. It will also attempt to obtain an anonymous token from the service if no token is present. The SKILL.md frontmatter includes a configPaths entry not reflected in the registry requirements; while likely harmless, it is an inconsistency to verify. No other unrelated secrets are requested.
Persistence & Privilege
always:false and model invocation is allowed (platform default). The skill expects to save session_id and reuse a session token lifecycle (normal for remote render jobs). It does not request permanent 'always' presence or access to other skills' configurations.
Assessment
This skill appears to do what it says: it uploads your text/files to a nemovideo.ai backend, creates a session, and returns rendered MP4s. Before installing: (1) Confirm you trust the external domain (mega-api-prod.nemovideo.ai) and are comfortable uploading the files you plan to process — do not upload secrets or personal data you wouldn't want shared. (2) Provide a NEMO_TOKEN only for this service; if the skill generates an anonymous token on your behalf, be aware it grants temporary access/credits. (3) Note the small metadata mismatch (config path declared in SKILL.md but not in registry) and the package has no homepage/source listed — if provenance matters, ask the publisher for a link or documentation. (4) If you need stronger guarantees about data handling, request the service's privacy/retention policy or avoid using the skill for sensitive content.

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

Runtime requirements

🔊 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk972pjj4thcjdmg2p694k6gzys85da9a
69downloads
0stars
1versions
Updated 5d 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 text-to-speech generation.

Try saying:

  • "convert a 200-word product description script into a 1080p MP4"
  • "convert this script to natural voiceover audio and sync it to my video"
  • "adding AI voiceover to videos from written scripts for content creators, marketers"

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 Audio TTS — Convert Text to Video Voiceover

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

A quick example: upload a 200-word product description script, type "convert this script to natural voiceover audio and sync it to my video", and you'll get a 1080p MP4 back in roughly 20-45 seconds. All rendering happens server-side.

Worth noting: shorter scripts with clear punctuation produce more natural-sounding speech.

Matching Input to Actions

User prompts referencing ai audio tts, 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.

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

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend 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>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-audio-tts, 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.

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

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.

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)

Common Workflows

Quick edit: Upload → "convert this script to natural voiceover audio and sync it to my video" → Download MP4. Takes 20-45 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 "convert this script to natural voiceover audio and sync it to my video" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Comments

Loading comments...