skill-test

To validate YAML frontmatter in SKILL.md files, use the static lint mode to check required fields like name, description, argument-hint, user-invocable, and allowed-tools. Running a repository-wide static lint ensures structural compliance across all skill definitions.

The best way to audit Claude skill definitions is to run an audit mode evaluation that checks phase structure and procedural hints. This generates actionable compliance reports and recommended handoff follow-ups for improvements.

No external dependencies are required to run static analysis on skill definitions. The validation tooling uses built-in capabilities and the catalog to check YAML frontmatter and phase structure without installing additional packages.

To check the multi-phase structure of your skills, execute a spec or category mode evaluation. This validates required sections and procedural hints across your skills, ensuring behavioral compliance with handoff protocols.

Skill definition handoff protocol validation fails when required procedural hints or phase sections are missing. The compliance report identifies these structural gaps and provides actionable recommendations to fix the skill definition.

Yes, you can generate compliance reports for multiple skills at once by running a repository-wide static lint. This evaluates all skills in the directory and outputs a comprehensive compliance report with handoff recommendations.