Stats
Actions
Tags
From clp
Diagnose and validate the CLP installation. Checks directory structure, configuration files, hook wiring, skill registry, and context optimization. This skill should be used when something seems wrong, after initial setup, or to audit the installation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/clp:clp-doctorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<instructions>
<diagnostic_checks>
- Is jq installed and available?
- Is git available?
Present results as: ✓ for pass, ✗ for fail, ⚠ for warning (non-critical). End with a summary: X passed, Y failed, Z warnings. If there are failures, provide specific fix instructions for each one.
- Actually check the filesystem. Do not assume files exist. - For JSON validation, try parsing with jq or by reading the file. - Be precise about what's wrong and how to fix it. - Keep output scannable — one line per check, details only for failures.npx claudepluginhub ryannle1/clp --plugin clpAudits .claude/ structure, naming, hooks, and plugin versions. Runs hygiene and sync checks, outputs health report with fix commands.
Scans skills, commands, CLAUDE.md, and hooks for redundancy, overlap, and misclassification. Produces an informational report with restructuring suggestions.
Validates Claude Code plugins for compliance with official guidelines including plugin.json manifest, directory structure, and formats for agents/skills/commands to prevent installation failures.