skill-audit

You can audit SKILL.md files by scanning them to identify bloated templates, oversized frontmatter, and unnecessary content repetition. The process flags anti-patterns and reports structured metadata including dependencies and safety flags.

Harmful anti-patterns in markdown skill definitions include risky prompts like "DO NOT FIX" and oversized YAML frontmatter. Identifying these patterns improves maintainability and ensures safe skill catalogs.

Validating YAML frontmatter in SKILL.md entries involves checking for the presence of required name and description fields. The audit examines the frontmatter structure and flags entries missing these critical metadata components.

Yes, you can scan all skill units under the .agents/skills directory across a repository during catalog maintenance. The audit identifies security flags and harmful patterns to help prune obsolete skills and reduce token costs.

The best way to reduce token costs in a skill catalog is running hygiene audits to prune obsolete or redundant skills. Detecting unnecessary repetition and bloated templates in SKILL.md entries keeps the catalog concise.

Automated skill audits are not suited for repositories lacking standardized SKILL.md entries with YAML frontmatter. The audit relies on consistent file structures to validate name and description fields and detect anti-patterns effectively.