Health Check Skill for Claude
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill health-checkThe instruction itself
8 sections, as written by the authorHealth 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
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take bitwize-music-studio/health-check from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.