Skill

health

Kokoro TTS health check. TRIGGERS - kokoro health, tts health, kokoro status.

Install

Run in your terminal

npx claudepluginhub terrylica/cc-skills --plugin kokoro-tts

Tool Access

This skill is limited to using the following tools:

ReadBashGlob

Supporting Assets

View in Repository

references/health-checks.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

cost-optimization

1 file

Optimizes cloud costs on AWS, Azure, GCP via rightsizing, tagging strategies, reserved instances, spot usage, and spending analysis. Use for expense reduction and governance.

cloud-infrastructure

33.0k

Stats

Parent Repo Stars28

Parent Repo Forks4

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Checks

Check

Command

Venv exists

[[ -d ~/.local/share/kokoro/.venv ]]

Python 3.13

~/.local/share/kokoro/.venv/bin/python --version | grep 3.13

mlx_audio import

python -c "from mlx_audio.tts.utils import load_model"

kokoro_common.py

[[ -f ~/.local/share/kokoro/kokoro_common.py ]]

tts_generate.py

[[ -f ~/.local/share/kokoro/tts_generate.py ]]

version.json

[[ -f ~/.local/share/kokoro/version.json ]]

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

Post-Execution Reflection

After this skill completes, check before closing:

Did the command succeed? — If not, fix the instruction or error table that caused the failure.

Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.

Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.

Only update if the issue is real and reproducible — not speculative.

Kokoro TTS Health Check

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.

Checks

#	Check	Command
1	Venv exists	`[[ -d ~/.local/share/kokoro/.venv ]]`
2	Python 3.13	`~/.local/share/kokoro/.venv/bin/python --version \| grep 3.13`
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 ]]`

Execution

PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/cc-skills/plugins/kokoro-tts}"
bash "$PLUGIN_DIR/scripts/kokoro-install.sh" --health

Failure Recommendations

Failure	Recommended Skill
Venv missing	install
Import fails	install or upgrade
Scripts missing	install
version.json	install

Troubleshooting

Issue	Cause	Solution
All checks fail	Not installed	Run `/kokoro-tts:install` first
Only import fails	Venv corrupted	`kokoro-install.sh --uninstall` then `--install`

Post-Execution Reflection

After this skill completes, check before closing:

Did the command succeed? — If not, fix the instruction or error table that caused the failure.
Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.

Only update if the issue is real and reproducible — not speculative.