{skill-name}

To extract and validate YAML frontmatter metadata for skill discovery, place a SKILL.md file at the root of your skill directory. This process validates mandatory name and description fields while detecting optional components like scripts, references, and assets.

Standard skill metadata structure requires a SKILL.md file with YAML frontmatter containing at least name and description fields. The structure also detects optional directories including scripts, references, and assets, assembling this information for discovery.

Repository structure rules detect optional skill components by checking for the presence of scripts, references, and assets directories. This detection records available components for on-demand usage and includes them in the returned structured YAML metadata block.

Yes, you can enforce safety checks and toxicity validation when defining skill metadata. The validation process records a toxicity flag for risk assessment, ensuring safety and readiness before the skill is discovered and used in the repository.

To enable skill discovery, you need to include mandatory name and description fields in the SKILL.md YAML frontmatter. This minimum requirement allows the metadata extraction process to surface your skill and assemble its dependencies and components.

Skill metadata validation returns a structured YAML block with dependencies to standardize how skills are defined and discovered. This uniform output ensures consistent metadata extraction, component detection, and toxicity status reporting across the repository.