skill-test

Validate OpenCode skill markdown files by running a static linter that checks required YAML frontmatter fields, phase structure, and verdict keywords. This ensures skill files meet structural compliance and behavioral correctness before execution.

Behavioral testing for skill markdown protocol validation cross-references catalog, spec, and rubric paths to verify assertion-based test specifications. It produces deterministic compliance reports without external dependencies.

Check YAML frontmatter fields and missing verdict keywords by parsing skill arguments and enumerating skill files via globbing. The static linter mode detects missing required fields, insufficient phase structure, and missing collaboration protocol language.

Yes, you can audit skill catalog coverage gaps without external dependencies. Audit mode reports coverage status across skills and agents by cross-referencing catalog paths to produce deterministic compliance reports.

Skill validation works with category-specific quality rubrics to evaluate skills against category quality metrics. Category rubric mode checks whether skill instructions satisfy defined quality standards within the testing framework.

Static linting for markdown protocol validation is limited to detecting structural issues like missing frontmatter, insufficient phase structure, and missing protocol language. It does not execute or test the functional runtime behavior of the skill.