agentleFS
Sign inStart free
bitwize-music-studiobitwize-music-studio/claude-ai-music-skills/skills/health-check/SKILL.md

health-check

Skill589 starsChanged 9 months agoCC0-1.0View on GitHub

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.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the health_check MCP tool and report results to the user.

    line 14
  2. Very specific:

    Use the ToolSearch tool with query select:mcp__plugin_bitwize-music_bitwize-music-mcp__health_check to load the MCP tool schema

    line 20
  3. Very specific:

    Call mcp__plugin_bitwize-music_bitwize-music-mcp__health_check (the MCP tool, not a CLI command)

    line 21

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free