executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
server-and-cliOperate Coqui TTS installed console commands and the safe local demo server.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is about the installed tts or tts-server console commands: checking availability, listing models, querying model metadata, building synthesis or voice-conversion commands, routing custom checkpoint paths, using pipe output, or safely starting the local demo server.
Do not use this sub-skill for Python API details, training commands, vocoder/audio preprocessing utilities, or production deployment design.
tts flag syntax and command templates, read references/cli-reference.md.tts-server help/list/run patterns and demo-server safety, read references/server-workflows.md.tts help/list/model-info paths without synthesis.tts commands from validated inputs.tts-server help/list paths without binding a server.TTS.api.TTS, ModelManager, and Synthesizer usage belong in ../inference-and-model-zoo/SKILL.md.tts --source_wav --target_wav CLI surface.tts-server as a local demo interface. It can bind a port, run Flask debug mode, load large models, and download released checkpoints. Do not present it as a hardened persistent service.tts --help, tts --list_models, tts --model_info_by_name ..., tts --model_info_by_idx ..., tts-server --help, and tts-server --list_models are the preferred low-side-effect checks.tts-server must be opt-in. Choose a port deliberately, check whether it is free, avoid debug mode unless actively debugging, and remember that this version binds the Flask app to the unspecified host ::.