auditing-skills

Auditing a SKILL.md file requires validating YAML frontmatter, enforcing XML structure conformance, and checking progressive disclosure to identify anti-patterns and generate actionable remediation reports with file:line locations.

YAML frontmatter validation requires checking for mandatory fields like name and description to ensure correctness, preventing silent failures and promoting consistent quality governance across all skill documentation units.

Checking progressive disclosure involves verifying the SKILL.md file remains under 500 lines and that references maintain a depth of one, ensuring documentation aligns with non-destructive evaluation and structural best practices.

Missing XML structure tags are flagged because the audit enforces pure XML conformance for objective, quick_start, and success_criteria sections, actively identifying any markdown headings or missing tags in the file.

Yes, the auditing workflow applies reference checks across all skill units including legacy ones, ensuring non-destructive evaluation by identifying anti-patterns like missing failure modes and unclear verification gates.

Generating actionable findings requires running a comprehensive audit that produces severity labels, specific file:line locations, and clear contextual remediation guidance for identified structural and content issues.