Qwencloud Audio TTS
Synthesize speech from text with Qwen TTS models. TRIGGER when: user wants to convert text to speech, create voiceovers, generate audio narration, read text aloud, build TTS applications, mentions speech synthesis/voice generation/audio output from text, or explicitly invokes this skill by name (e.g. use qwencloud-audio-tts). DO NOT TRIGGER when: user wants speech recognition/ASR, text generation without audio, non-Qwen audio tasks.
- Skill ID
- qwencloud/qwencloud-ai/qwencloud-audio-tts
- Publisher
- qwencloud
- Repository
- qwencloud-ai
- Installs
- 0
- Files
- 15
- Requires
- Requires Python 3.9+; curl is PAYG-only. Cursor: auto-loaded. Claude Code: read this skill's SKILL.md before first use.
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
qwencloud/qwencloud-ai/qwencloud-audio-ttsInstalls these files- SKILL.md
- cdn/config/qwencloud-audio-tts-config.json
- cdn/config/qwencloud-token-plan-config.json
- cdn/references/qwencloud-audio-tts-models.md
- cdn/references/qwencloud-model-pricing.md
- cdn/references/qwencloud-token-plan-models.md
- references/api-guide.md
- references/cosyvoice-guide.md
- references/execution-guide.md
- references/prompt-guide.md
- references/sources.md
- scripts/gossamer.py
- scripts/qwencloud_lib.py
- scripts/tts.py
- scripts/tts_cosyvoice.py
What this skill tells the agent
Qwen Audio TTS (Text-to-Speech)
Synthesize natural speech from text using Qwen TTS models. This skill is part of qwencloud/qwencloud-ai.
Skill directory
Use this skill's internal files to execute and learn. Load reference files on demand when the default path fails or you need details.
| Location | Purpose |
|---|---|
scripts/tts.py | Qwen TTS / Qwen Audio TTS (HTTP and WebSocket); current compatibility and defaults are in the model catalog below |
scripts/tts_cosyvoice.py | CosyVoice (WebSocket API) — requires dashscope SDK; current compatibility and defaults are in the model catalog below |
references/cosyvoice-guide.md | CosyVoice setup, voices, examples, errors |
references/execution-guide.md | Fallback: curl (standard, instruct, streaming), code generation |
references/prompt-guide.md | Text formatting for speech, instructions templates, voice selection |
references/api-guide.md | API supplement |
references/sources.md | Official documentation URLs |
Security
NEVER output any API key or credential in plaintext. Always use variable references ($QWENCLOUD_API_KEY in shell, os.environ["QWENCLOUD_API_KEY"] in Python). The scripts accept QWENCLOUD_API_KEY, then QWEN_API_KEY, then DASHSCOPE_API_KEY. Any check or detection of credentials must be non-plaintext: report only status (e.g. "set" / "not set", "valid" / "invalid"), never the value. Never display contents of .env or config files that may contain secrets.
When the API key is not configured, NEVER ask the user to provide it directly. Instead, help create a .env file with a placeholder (QWENCLOUD_API_KEY=sk-your-key-here) and instruct the user to replace it with their actual key from the QwenCloud Console. Only write the actual key value if the user explicitly requests it.
Key Compatibility
Scripts support both standard QwenCloud API keys (sk-...) and Token Plan keys (sk-sp-...). Token Plan keys are automatically routed to the Token Plan endpoint for supported TTS models — see Token Plan Support below.
Token Plan: do not use curl; always use the bundled Python scripts.
Coding Plan keys (also sk-sp- prefix but purchased via Coding Plan subscription) cannot be used — TTS models are not available on Coding Plan. The script detects key type at startup and routes accordingly. If qwencloud-ops-auth is installed, see its references/codingplan.md for full details.
Detect the API key type without exposing the key:
python3 -c "
import sys; sys.path.insert(0, 'scripts')
from qwencloud_lib import detect_api_key_type
print(detect_api_key_type('scripts/qwencloud_lib.py'))
"| Output | Meaning |
|---|---|
token-plan | Token Plan key detected (sk-sp- prefix) |
payg | Standard PAYG key detected |
not-set | No API key found in environment |
For Token Plan, fetch and read the current Token Plan model catalog, then use an exact listed model with scripts/tts.py. If CDN access fails, use the local fallback.
Model Selection
🚫 CRITICAL — Never override the user's model choice. If the user (or the request JSON) explicitly specifies amodel, you MUST use exactly that model. Do NOT: - Replace it with a "better suited" model (e.g., switching toqwen3-tts-instruct-flashfor stylized/poetic text) - Addinstructionsthe user did not ask for - Modify any parameter the user explicitly provided Model selection guidance below applies only when the user has NOT specified a model.
Before selecting, recommending, or defaulting a model, fetch and read the current QwenCloud audio TTS model catalog. It contains the model list, basic model information, script and voice compatibility, recommendations, and defaults. If CDN access fails, use the local fallback.
Consult the qwencloud-model-selector skill when model choice depends on capability, scenario, or pricing. CosyVoice requires the dashscope SDK and uses different voices; see cosyvoice-guide.md.
⚠️ Important: The model catalog is a point-in-time snapshot and may be outdated. Model availability changes frequently. Always check the [official model list](https://www.qwencloud.com/models) for the authoritative, up-to-date catalog before making model decisions.
Model details: For more information about a specific model, direct the user tohttps://www.qwencloud.com/models/<model-name>. Replace<model-name>with the exact model ID; never modify or guess it.
Dynamic model queries: If the qwencloud-model-selector skill or QwenCloud CLI (qwencloud models info <model>) is available, use it for real-time model data. CLI requires authentication — see the qwencloud-usage skill for login flow.Available Voices
Use the QwenCloud audio TTS model catalog linked above for current model-to-voice compatibility and defaults. For complete voice inventories, use the official voice-list links in sources.md.
Voice defaulting: When no voice is supplied for a Qwen-Audio WebSocket model,tts.pyselects that model's configured default voice and prints a notice to stderr. Any explicit voice—including explicitCherry—is passed through unchanged. Fetch the model catalog before choosing a voice.
Execution
⚠️ Multiple artifacts: When generating multiple files in a single session, you MUST append a numeric suffix to each filename (e.g.out_1.wav,out_2.wav) to prevent overwrites.
Qwen TTS (HTTP API) — tts.py
Prerequisites
- API Key: Check
QWENCLOUD_API_KEY,QWEN_API_KEY, thenDASHSCOPE_API_KEYusing a non-plaintext check only (e.g. in shell:[ -n "$QWENCLOUD_API_KEY" ]; report only "set" or "not set", never the key value). If not set: run the qwencloud-ops-auth skill if available; otherwise guide the user to obtain a key from QwenCloud Console and set it via.envfile (echo 'QWENCLOUD_API_KEY=sk-your-key-here' >> .envin project root or current directory) or environment variable. The script searches for.envin the current working directory and the project root. Skills may be installed independently — do not assume qwencloud-ops-auth is present. Note: The script auto-loads.envfrom the current directory and the project root (in addition to any exported environment variable). A shell check showing$QWENCLOUD_API_KEYas "not set" does NOT mean the script will fail — it may still find the key in.env. Treat the shell check as informational only; the authoritative test is simply running the script (it exits with a clear error if no key is found anywhere). - Python 3.9+ (stdlib only, no pip install needed)
Environment Check
Before first execution, verify Python is available:
python3 --version # must be 3.9+If python3 is unavailable or below 3.9, PAYG may use Path 2 (curl); Token Plan must install Python 3.9+ instead.
Default: Run Script
Script path: Scripts are in the scripts/ subdirectory of this skill's directory (the directory containing this SKILL.md). You MUST first locate this skill's installation directory, then ALWAYS use the full absolute path to execute scripts. Do NOT assume scripts are in the current working directory. Do NOT use cd to switch directories before execution.
Execution note: Run all scripts in the foreground — wait for stdout; do not background.
Discovery: Run python3 <this-skill-dir>/scripts/tts.py --help first to see all available arguments.
More from qwencloud
Use this skill in a project
Open any RiverX project, search the Skills panel for qwencloud/qwencloud-ai/qwencloud-audio-tts, and install it in one click.
