← Back to Skills Marketplace
141
Downloads
1
Stars
0
Active Installs
5
Versions
Install in OpenClaw
/install text-to-voice-local
Description
Local text-to-voice generation for OpenClaw workspaces using a canonical txt-to-mp3 pipeline. Use when the user wants to turn any prepared text into voice, a...
Usage Guidance
This skill appears to do what it says: convert local text files to MP3 using node + node-edge-tts and ffmpeg, and maintain a canonical latest.mp3 path. Before installing/using it: (1) review and decide whether you’re comfortable installing node-edge-tts globally (npm i -g), since that requires network access to npm and the TTS library will contact its remote TTS provider during generation; (2) run the scripts in a non-root workspace or inspect/adjust the state JSON canonical paths (the bundled state uses /root/.openclaw/...); (3) verify node and ffmpeg come from trusted sources for your environment; (4) if you need offline-only operation, confirm node-edge-tts’s privacy/endpoint behavior or replace it with an explicitly offline engine. Otherwise the skill is coherent and proportionate to its stated purpose.
Capability Analysis
Type: OpenClaw Skill
Name: text-to-voice-local
Version: 1.4.0
The skill provides a legitimate local text-to-speech pipeline using the 'node-edge-tts' library and 'ffmpeg'. The bundle consists of shell scripts and a Node.js helper that manage text chunking, audio generation, and state tracking. No evidence of data exfiltration, persistence mechanisms, or malicious prompt injection was found; the code logic is transparent and aligns strictly with the stated purpose of converting text files to MP3 audio.
Capability Assessment
Purpose & Capability
Name/description (local text-to-voice) align with the provided scripts: they read text files, call a Node TTS helper, use ffmpeg to concat/encode chunks, and update canonical output/state files. Requested binaries (node, ffmpeg, node-edge-tts) are expected for this functionality.
Instruction Scope
SKILL.md and the shell/js scripts limit their actions to workspace tmp and skill state paths; they read text files, produce mp3s, and update a last-output pointer. There are no instructions to read unrelated system files, access unrelated credentials, or transmit data to custom external endpoints. Note: the node dependency node-edge-tts will perform TTS and likely contact the remote TTS service as part of normal operation (this is expected for a TTS library).
Install Mechanism
No automated install spec is present (the skill is instruction + scripts). The README tells the operator how to install node-edge-tts (npm i -g). That is reasonable, but users should be aware this requires running a global npm install and network access to npm; the skill itself does not embed or download external binaries automatically.
Credentials
The skill does not request environment variables or external credentials. It uses OPENCLAW_WORKSPACE optionally and TTS_RETRIES/other shell variables if present — all proportional to operation. The included state files contain absolute example paths under /root/.openclaw/workspace, which are benign but operator-specific and should be adjusted when installed into another workspace.
Persistence & Privilege
always:false and user-invocable; scripts only write to their own skill state directory and workspace tmp. The skill does not modify other skills or global agent settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install text-to-voice-local - After installation, invoke the skill by name or use
/text-to-voice-local - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.4.0
Add dependency checks with install hints in status and before voice generation
v1.3.0
Rename low-level TTS helper to edge_tts.js and improve dependency error messaging
v1.2.0
Improve dependency handling for node-edge-tts and document installation requirements
v1.1.0
Improve portability, move state into the skill, add status and voices helpers
v1.0.0
Initial public release
Metadata
Frequently Asked Questions
What is Text to Voice Local?
Local text-to-voice generation for OpenClaw workspaces using a canonical txt-to-mp3 pipeline. Use when the user wants to turn any prepared text into voice, a... It is an AI Agent Skill for Claude Code / OpenClaw, with 141 downloads so far.
How do I install Text to Voice Local?
Run "/install text-to-voice-local" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Text to Voice Local free?
Yes, Text to Voice Local is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Text to Voice Local support?
Text to Voice Local is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Text to Voice Local?
It is built and maintained by Ildar (@betonimig); the current version is v1.4.0.
More Skills