health-check · bitwize-music-studio — Claude Code skill: plugin diagnostics
health-check — a skill that runs plugin diagnostics: checks virtual environment packages, verifies skill registration, and detects album slug collisions. Use it to confirm your setup is correct or troubleshoot missing components.
CC0-1.0 187 installs ★ 686 updated 2026-10-22
npx skills add bitwize-music-studio/claude-ai-music-skills --skill health-check -a claude-codeWhat health-check does
health-check calls the health_check MCP tool and produces a structured report across three areas. It scans packages in ~/.bitwize-music/venv, flagging outdated or missing dependencies. It verifies that skills are registered in Claude Code and identifies stale cached entries from deleted skills. It also scans for album slug collisions, where two genres attempt to claim the same identifier.
When all checks pass, you get an OK status. If warnings arise, the skill shows what failed and provides the fix command—such as claude plugin update bitwize-music or /bitwize-music:setup. For critical failures, it suggests running the deeper diagnose MCP tool.
What it helps with
- verify all plugin packages are installed in the virtual environment
- confirm skills are registered and discoverable in the editor
- locate and resolve album slug collisions
- diagnose plugin startup errors and missing components
Example prompts for the agent
- Run health-check to see if the plugin setup is complete
- Run health-check and show me what's broken in the configuration
- Check the plugin's health—something might be missing
How to install health-check
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill health-check -a claude-code2Manually: put the files in place
~/.claude/skills/health-check/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/health-check/
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill health-check -a codex2Manually: put the files in place
.agents/skills/health-check/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill health-check -a cursor2Manually: put the files in place
.cursor/skills/health-check/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bitwize-music-studio/claude-ai-music-skills skills/health-check2Manually: put the files in place
.github/skills/health-check/SKILL.md1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill health-check -a gemini-cli2Platform CLI
gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills --path skills/health-checkManually: put the files in place
.devin/skills/health-check/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill health-check -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about health-check
How do I install health-check in Claude Code?
Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill health-check -a claude-code, then open ~/.claude/skills/health-check/SKILL.md.
What does health-check do?
It scans the plugin's virtual environment, verifies skill registration, and checks for identifier collisions. If it finds a problem, it shows the command to fix it.
What tools does health-check use?
It runs through the ToolSearch and bitwize-music-mcp MCP tools—no shell commands involved. For deeper insight, it can suggest running the diagnose tool.
Source text
SKILL.md · CC0-1.0
--- name: health-check description: 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. model: haiku allowed-tools: - ToolSearch - bitwize-music-mcp --- # 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 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 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
© bitwize-music-studio · CC0-1.0 · bitwize-music-studio/claude-ai-music-skills
Similar skills
All skills for Agent setup: memory, context, orchestration →health-check by other authors comes first.