system-health-check_skill

This skill runs a comprehensive ten-subsystem health check for the TTS engine and Telegram bot, producing a clear pass/fail report with actionable fixes.

TypeScript

14

GitHub Stars

1

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill terrylica/cc-skills --skill system-health-check

SKILL.md6.9 KB

Overview

This skill runs a focused health check across the TTS engine, Telegram bot, and supporting infrastructure, producing a pass/fail table and actionable recommendations. It targets macOS (Apple Silicon) setups and validates runtime, secrets, GPU availability, locks, and temporary artifacts. Use it to quickly verify system readiness or to diagnose intermittent failures in the TTS pipeline.

How this skill works

The skill executes ten discrete checks: bot process presence, Telegram API responsiveness, Kokoro virtualenv existence and import, Apple Silicon MPS availability via PyTorch, lock file state, audio process counts, secrets file presence, stale WAV artifacts, and shell symlink validity. Each check returns [OK] or [FAIL] with a short diagnostic. Results are collected into a table and summarized with pass/fail counts and recommended fixes for failures.

When to use it

Diagnose why TTS or Telegram bot is not working
Verify system readiness after bootstrap or configuration changes
Run a pre-demo or presentation system sanity check
Investigate intermittent TTS pipeline failures or crashes
Detect stale locks, zombie processes, or orphaned temp files

Best practices

Load environment variables from your mise configuration before running checks to ensure BOT_TOKEN and other secrets are available
Run the full 10-check sequence — don’t skip Kokoro or MPS checks when using Apple Silicon
Treat lock failures (stale/orphaned) as high priority; inspect PID and lock age before removing files
Never print secrets or tokens in report output; report only presence/absence and safe diagnostics
Automate this skill as a pre-deploy or CI gating step to catch regressions early

Example use cases

Pre-demo health report: run all checks and confirm 10/10 before presenting TTS features
Post-crash triage: run checks to find stale locks, orphaned WAVs, or missing bot processes
CI readiness gate: verify Kokoro venv, Python import, and MPS availability on macOS runners
On-call diagnostic: quickly determine whether Telegram API failures are token or network related
Maintenance script: scheduled run to detect and clean stale WAVs and reset orphaned locks

FAQ

This skill is designed for macOS on Apple Silicon; MPS checks require PyTorch with MPS support and Kokoro in the expected venv path.

Will it expose my bot token or secrets?

No. The checks validate presence and API responses but do not print secrets or raw token values in the report.

What indicates a critical failure?

Failures of core checks (bot process missing, Telegram API false, Kokoro venv/import failing, or stale/orphaned locks) are critical and should be addressed before running TTS workloads.