From kokoro-tts
Kokoro TTS health check. TRIGGERS - kokoro health, tts health, kokoro status.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kokoro-tts:healthhaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run 6 health checks to verify the Kokoro TTS engine installation.
Run 6 health checks to verify the Kokoro TTS engine installation.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
| # | Check | Command |
|---|---|---|
| 1 | Venv exists | [[ -d ~/.local/share/kokoro/.venv ]] |
| 2 | Python 3.14 | ~/.local/share/kokoro/.venv/bin/python --version | grep 3.14 |
| 3 | mlx_audio import | python -c "from mlx_audio.tts.utils import load_model" |
| 4 | kokoro_common.py | [[ -f ~/.local/share/kokoro/kokoro_common.py ]] |
| 5 | tts_generate.py | [[ -f ~/.local/share/kokoro/tts_generate.py ]] |
| 6 | version.json | [[ -f ~/.local/share/kokoro/version.json ]] |
PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/cc-skills/plugins/kokoro-tts}"
bash "$PLUGIN_DIR/scripts/kokoro-install.sh" --health
| Failure | Recommended Skill |
|---|---|
| Venv missing | install |
| Import fails | install or upgrade |
| Scripts missing | install |
| version.json | install |
| Issue | Cause | Solution |
|---|---|---|
| All checks fail | Not installed | Run /kokoro-tts:install first |
| Only import fails | Venv corrupted | kokoro-install.sh --uninstall then --install |
After this skill completes, check before closing:
Only update if the issue is real and reproducible — not speculative.
npx claudepluginhub terrylica/cc-skills --plugin kokoro-ttsGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.