Health check
Skill bitwize-music-studio/claude-ai-music-skills/skills/health-check
Runs plugin health checks (venv packages, skill registration, and album slug collisions). Use when the user asks to check plugin health, verify setup, or troubleshoot missing skills.From its SKILL.md
npx -y skills add bitwize-music-studio/claude-ai-music-skills --skill health-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.9 KB, 476 tokens by cl100k_base, as published. Nobody here has run it
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.
- Use the
ToolSearchtool with queryselect:mcp__plugin_bitwize-music_bitwize-music-mcp__health_checkto load the MCP tool schema - Call
mcp__plugin_bitwize-music_bitwize-music-mcp__health_check(the MCP tool, not a CLI command) - Report results clearly using the format below
Report Format
All OK
HEALTH CHECK: OK
Venv: N packages verified
Skills: N skills registered
Collisions: no album slug collisions
Warnings
HEALTH CHECK: WARN
VENV [warn]
N outdated: pkg1 (1.0 -> 1.1), pkg2 (2.0 -> 2.1)
N missing: pkg3, pkg4
Fix: <the venv check's `fix` field from the health_check result> (already the correct command for the user's OS)
SKILLS [warn]
N missing from Claude Code: skill-a, skill-b
N ghost (deleted but cached): skill-c
Fix: claude plugin update bitwize-music
COLLISIONS [warn]
N album slug collision(s):
slug-name: kept [genre-a], shadowed by [genre-b]
Fix: Rename one album with /bitwize-music:rename or move its directory, then run rebuild_state
For comprehensive diagnostics, run the `diagnose` MCP tool.
Failure
HEALTH CHECK: FAIL
VENV [fail]
Venv not found at ~/.bitwize-music/venv
Fix: /bitwize-music:setup
Remember
- Be concise — this is a status report
- Show fix commands — always include the fix command when status is not ok
- Suggest diagnose — if warnings are found, mention
diagnoseMCP tool for deeper checks
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most quality gates skills give in 476 tokens
Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06
- Read full output and check exit codein 45 of 1524, across 40 files
- Verify output confirms the claimin 44 of 1524, across 39 files
- Identify the command that proves the claimin 43 of 1524, across 39 files
- Execute the full verification commandin 36 of 1524, across 30 files
- Produce a verification reportin 34 of 1524, across 18 files
- Review git diff changesin 30 of 1524, across 16 files
- Fix build failures immediatelyin 29 of 1524, across 9 files
- Group findings by severityin 28 of 1524
- State claim only with evidencein 27 of 1524, across 22 files
- Verify regression tests with red-green cyclein 26 of 1524, across 22 files
- Run the full test suitein 26 of 1524, across 25 files
- Run test suite with coveragein 25 of 1524, across 10 files
Said here and by no other author read
- Use the ToolSearch tool to load the MCP schema
- Include fix commands when status is not OK
- Suggest the diagnose tool if warnings are found
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.