Audio Tts

convert text or script into voiced video clips with this skill. Works with TXT, DOCX, PDF, SRT files up to 200MB. content creators, marketers, educators use...

Security Scan

The skill's declared purpose (text→voiced video) matches the API calls it instructs, but there are metadata inconsistencies and unanswered questions about where tokens/sessions are stored and the SDK/config path access — ask the publisher for clarification before installing.

Purpose & Capability

The skill claims to convert text into voiceover videos and only requests a single service credential (NEMO_TOKEN), which is coherent. However the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — that mismatch is unexplained.

Instruction Scope

Runtime instructions call only the external nemo API endpoints needed for uploads, SSE, session creation, and exports (consistent with the stated purpose). The instructions also direct the agent to acquire an anonymous token if none is provided and to "store" the session_id for later calls — but they do not specify where/how to persist session/token data (in-memory vs disk vs agent config), which is ambiguous and worth clarifying.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing is written to disk by an installer. That is the lowest-risk install posture.

Credentials

The only declared required environment variable is NEMO_TOKEN, which is appropriate for a third-party TTS/rendering service. But the SKILL.md also lists a config path (~/.config/nemovideo/) in its frontmatter and requires auto-detection of the install path for X-Skill-Platform headers — both imply potential filesystem reads not declared in the registry metadata. This discrepancy makes it unclear what local data the skill will access.

Persistence & Privilege

always:false (good). The skill instructs the agent to create anonymous tokens and keep sessions alive across requests; it does not explicitly say it will modify other skills or system-wide settings. Clarify whether tokens/sessions are persisted to disk or saved only in-memory by the agent.

What to consider before installing

This skill appears to do what it claims (remote text→voiceover rendering) and asks only for a service token, but there are a few red flags to consider before installing: 1) Metadata mismatch — the SKILL.md references a local config path (~/.config/nemovideo/) that the registry metadata does not list; ask the publisher why the skill might read that folder. 2) Token/session persistence — the skill will generate an anonymous token and instruct you to "store" a session_id but doesn't say where; confirm whether tokens or session IDs will be saved to disk or only kept in-memory. 3) Privacy and retention — uploads and renders go to mega-api-prod.nemovideo.ai; request the service's privacy policy and data retention rules (do they keep uploaded scripts or generated media?). 4) Source and provenance — there is no homepage or source repo; prefer skills with a documented homepage or published client library you can audit. If you proceed, avoid supplying unrelated secrets (AWS keys, GitHub tokens, etc.), and restrict filesystem access if your agent platform allows it. Asking the publisher for a homepage, code examples showing how/where tokens are stored, and a privacy/retention statement would reduce risk.

Getting Started

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

Try saying:

• "convert a 200-word product description script into a 1080p MP4"
• "convert this script to a natural voiceover in English with a female voice"
• "generating AI voiceovers from written scripts for content creators, marketers, educators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Audio TTS — Convert Text to Voiceover Video

Send me your text or script and describe the result you want. The text to speech conversion 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 a natural voiceover in English with a female voice", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter text segments produce more natural-sounding speech output.

Matching Input to Actions

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

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

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.

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 "convert this script to a natural voiceover in English with a female voice" — concrete instructions get better results.

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

Export as MP4 for widest compatibility with video platforms.

Common Workflows

Quick edit: Upload → "convert this script to a natural voiceover in English with a female 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.