
Health Check
- 87 installs
- 400 repo stars
- Updated July 31, 2026
- bitwize-music-studio/claude-ai-music-skills
health-check is a Claude Code skill that runs the bitwize-music plugin health checks for venv packages and skill registration and reports the status.
About
This skill runs the bitwize-music plugin health checks and reports the results. It calls the health_check MCP tool to verify venv packages and skill registration, then formats a concise OK, WARN, or FAIL report with fix commands. A user runs it to check plugin health, verify setup, or troubleshoot missing skills. It uses only the MCP tool, not Bash.
- Runs the bitwize-music plugin health check via an MCP tool
- Verifies venv packages and skill registration, then reports OK/WARN/FAIL
- Surfaces concrete fix commands when checks are not OK
Health Check by the numbers
- 87 all-time installs (skills.sh)
- Ranked #859 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
health-check capabilities & compatibility
- Capabilities
- health check · setup verification · diagnostics · monitoring
- Use cases
- debugging
What health-check says it does
Runs plugin health checks (venv packages and skill registration).
Use when the user asks to check plugin health, verify setup, or troubleshoot missing skills.
Call `mcp__plugin_bitwize-music_bitwize-music-mcp__health_check` (the MCP tool, not a CLI command)
npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill health-checkAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 87 |
|---|---|
| repo stars | ★ 400 |
| Last updated | July 31, 2026 |
| Repository | bitwize-music-studio/claude-ai-music-skills ↗ |
What it does
Check the bitwize-music plugin's health by verifying venv packages and skill registration and reporting a concise status.
Who is it for?
Verifying the bitwize-music plugin's venv packages and skill registration and reporting status.
Skip if: Deep diagnostics (use the diagnose MCP tool) or any task requiring Bash.
When should I use this skill?
When the user asks to check plugin health, verify setup, or troubleshoot missing skills.
What you get
A concise OK/WARN/FAIL health report with fix commands for the bitwize-music plugin.
- Venv package status
- Skill registration status
- OK/WARN/FAIL report with fix commands
By the numbers
- 3 report states (OK/WARN/FAIL)
- 2 checks (venv packages, skill registration)
Files
Health Check
Your Task
Run the health_check MCP tool and report results to the user.
Workflow
IMPORTANT: Do NOT use Bash for any step. Use only the tools listed below.
1. Use the ToolSearch tool with query select:mcp__plugin_bitwize-music_bitwize-music-mcp__health_check to load the MCP tool schema 2. Call mcp__plugin_bitwize-music_bitwize-music-mcp__health_check (the MCP tool, not a CLI command) 3. Report results clearly using the format below
Report Format
All OK
HEALTH CHECK: OK
Venv: N packages verified
Skills: N skills registeredWarnings
HEALTH CHECK: WARN
VENV [warn]
N outdated: pkg1 (1.0 -> 1.1), pkg2 (2.0 -> 2.1)
N missing: pkg3, pkg4
Fix: ~/.bitwize-music/venv/bin/pip install -r .../requirements.txt
SKILLS [warn]
N missing from Claude Code: skill-a, skill-b
N ghost (deleted but cached): skill-c
Fix: claude plugin update bitwize-music
For comprehensive diagnostics, run the `diagnose` MCP tool.Failure
HEALTH CHECK: FAIL
VENV [fail]
Venv not found at ~/.bitwize-music/venv
Fix: /bitwize-music:setupRemember
1. Be concise — this is a status report 2. Show fix commands — always include the fix command when status is not ok 3. Suggest diagnose — if warnings are found, mention diagnose MCP tool for deeper checks