Audit your Claude Code.claude/ setup — scans skills, commands, hooks, agents, and settings for dead refs, weak trigg...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Not hard to test, not trivial to unwind. Worth trying if it closes a sharp gap.
GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if claude-markdown-health-check belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
# Visit: https://github.com/ncoevoet/claude-markdown-health-checkRun this first. You will know quickly if the workflow earns a permanent slot.
# No automated removal — visit https://github.com/ncoevoet/claude-markdown-health-checkNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ claude-markdown-health-check/ ← installs here └─ settings.json
Audit your Claude Code.claude/ setup — scans skills, commands, hooks, agents, and settings for dead refs, weak triggers, token bloat, and skill-listing-budget overflow.