<skill-name>

Validate skill definitions by confirming a SKILL.md file exists at the directory root with YAML frontmatter containing the required name and description fields. This enforces a defined metadata schema for consistent discovery and safe integration into tooling.

The required YAML frontmatter schema includes name, description, owner, last-reviewed, and compatible-repo-areas. This standardized metadata ensures consistent repository discovery, metadata extraction, and activation workflows.

Structure directories by placing a SKILL.md at the root of each skill unit. You can optionally add scripts/, references/, and assets/ subdirectories to support extended capabilities for automated validation.

A Skill Unit is a standardized directory structure for defining skills in a repository, anchored by a SKILL.md file. You need to define one when you want to enforce consistent metadata extraction and enable safe integration into automation tooling.

Yes, the skill definition template tracks optional components and safety checks. It supports optional scripts/, references/, and assets/ directories alongside the required SKILL.md root file for extended capabilities.

Skill discovery fails if the directory lacks a SKILL.md file at the root or if the YAML frontmatter is missing the required name and description fields. The validation process strictly enforces this metadata schema before activation.