← Back to Skills Marketplace
qui-edge-tts
by
QuincyGunter
· GitHub ↗
· v1.0.0
· MIT-0
67
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install qui-edge-tts
Description
Text-to-speech conversion using SkillBoss API Hub TTS service for generating audio from text. Supports multiple voices, languages, speed adjustment, pitch co...
Usage Guidance
This package implements a TTS client that will send your text and the SKILLBOSS_API_KEY environment variable to an external API (api.heybossai.com). Before installing: (1) Confirm the SKILLBOSS_API_KEY requirement (the registry omitted it) and only provide a key you trust to that service. (2) Verify which upstream service you expect — docs mention Microsoft Edge voices but the code uses SkillBoss; confirm you trust heybossai.com and tts.travisvn.com. (3) Inspect the node-edge-tts dependency (and run npm audit) if you will run npm install. (4) Be aware the skill writes ~/.tts-config.json and temp audio files; if you need isolation, run it in a sandbox or container. (5) If you are uncomfortable with an unknown external API receiving your text or API key, do not install.
Capability Analysis
Type: OpenClaw Skill
Name: qui-edge-tts
Version: 1.0.0
The skill exhibits significant discrepancies between its metadata and actual implementation. While 'skill-info.json' and the included reference guides claim the skill uses the 'node-edge-tts' npm package, the core logic in 'scripts/tts-converter.js' ignores this dependency and instead sends user text and the required 'SKILLBOSS_API_KEY' to a hardcoded third-party endpoint (api.heybossai.com). Additionally, the script uses the 'fetch' API while claiming compatibility with Node.js v14 (which lacks native fetch support), and 'scripts/config-manager.js' persists configuration data in the user's home directory ('~/.tts-config.json'), which is an invasive practice for a portable skill bundle.
Capability Tags
Capability Assessment
Purpose & Capability
The skill's name/description and the code/README all implement a text-to-speech client that calls an external SkillBoss API (API_BASE=https://api.heybossai.com/v1). That is coherent with a TTS skill. However, there are documentation inconsistencies: some reference Microsoft Edge's online TTS while other parts reference SkillBoss API Hub and a preview site (tts.travisvn.com). The registry metadata also omitted the SKILLBOSS_API_KEY requirement that the scripts actually need. These mismatches are likely sloppy packaging or copy-paste, but they reduce trust.
Instruction Scope
SKILL.md and the code instruct the agent to detect TTS intent, call a built-in tts tool or run the provided Node.js scripts. The scripts only read/write a per-user config (~/.tts-config.json), create temporary audio files in the system temp dir, and send the provided text and SKILLBOSS_API_KEY to the external API. The instructions do not tell the agent to read arbitrary unrelated files or other credentials. Note: the skill will transmit user text and the SKILLBOSS_API_KEY to an external endpoint (api.heybossai.com) which is expected for a hosted TTS service.
Install Mechanism
This is mostly an instruction/script package with an install.sh that runs npm install in the scripts directory. Dependencies come from npm (commander, node-edge-tts). No remote archive downloads or obscure shorteners are used. The install is traceable via package.json/package-lock.json. Still, running npm install will pull node-edge-tts and its deps from the public registry — standard but worth vetting.
Credentials
The scripts require SKILLBOSS_API_KEY (process.env.SKILLBOSS_API_KEY) to authenticate to the remote TTS API. That is proportionate to the described purpose, but the registry metadata incorrectly lists no required environment variables. This omission is a notable inconsistency. Also, the key is used as a Bearer token to api.heybossai.com — installing this skill gives that service access to anything you send to the TTS client (including potentially sensitive text).
Persistence & Privilege
The skill persists user preferences to ~/.tts-config.json and writes temporary audio files to the system temp directory. These behaviors are expected for a CLI TTS tool. The skill does not request elevated system privileges and is not marked always:true. Persisting config in the user's home directory is normal but means settings (including a configured proxy) survive beyond a single run.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install qui-edge-tts - After installation, invoke the skill by name or use
/qui-edge-tts - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of edge-tts skill: high-quality TTS with flexible controls.
- Generate audio from text using SkillBoss API Hub, supporting multiple languages and voices
- Adjust speed, pitch, volume, and output format; generate subtitles if needed
- Provides CLI scripts for advanced usage and a config manager for persistent user preferences
- Automatically detects and processes TTS requests, filtering out trigger keywords
- Requires the SKILLBOSS_API_KEY environment variable for operation
Metadata
Frequently Asked Questions
What is qui-edge-tts?
Text-to-speech conversion using SkillBoss API Hub TTS service for generating audio from text. Supports multiple voices, languages, speed adjustment, pitch co... It is an AI Agent Skill for Claude Code / OpenClaw, with 67 downloads so far.
How do I install qui-edge-tts?
Run "/install qui-edge-tts" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is qui-edge-tts free?
Yes, qui-edge-tts is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does qui-edge-tts support?
qui-edge-tts is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created qui-edge-tts?
It is built and maintained by QuincyGunter (@quincygunter); the current version is v1.0.0.
More Skills