checkup

You can audit a Claude Code skills library by running a health-check to identify broken references, missing dependencies, and trigger collisions across all installed skills. The process validates frontmatter, trigger uniqueness, file naming, and cross-references.

Skills library drift occurs when structural issues and dependency changes accumulate over time. You detect drift and trigger collisions by running an audit that applies validation checks across all installed skills to surface duplicate triggers and unresolved references.

To validate frontmatter and cross-references, run a structural audit across your installed skills. This checks frontmatter formatting, trigger uniqueness, file naming conventions, and cross-references to surface structural issues and dependency drift.

Yes, a quick health snapshot is available by default with Level 0 and Level 1 checks. For a detailed report validating all structural issues, trigger uniqueness, and dependency drift, you can run the full audit using the --full flag for Level 2 checks.

Your audit report shows duplicate triggers and broken file references because the health-check detected structural issues and drift across your installed skills. It surfaces unresolved references, missing dependencies, and trigger collisions to provide actionable remediation guidance.

The best way to fix dependency drift and structural issues is to run a comprehensive library audit and follow the actionable remediation guidance it generates. This validates frontmatter, resolves broken cross-references, and ensures trigger uniqueness for safe updates.