skill-test

You can validate skill files for structural integrity by running static linting checks on frontmatter and metadata to ensure name and description fields exist and are well-formed across all skills under .agents/skills.

Skill behavioral spec checking enforces behavioral correctness by validating multiple phases, verdict keywords, collaborative protocol language, handoff, and runtime wording within skill definitions to maintain structural consistency.

You can audit skill coverage and category rubrics by running coverage auditing modes that scan all skill definitions under .agents/skills to produce standardized, actionable results for remediation.

Skill-test is specifically applicable to Skill units located under .agents/skills/*, meaning it targets and validates skill definitions exclusively within that designated repository path.

The best way to standardize skill metadata and fix errors is to run static validation across all skills, which produces consistent, actionable results that guide operational remediation for non-compliant definitions.

Skill definitions fail linting checks when collaborative protocol language, handoff specifications, or runtime wording do not meet the standardized behavioral spec checks enforced during the validation process.