comprehensive-skill

To validate frontmatter for skill discovery, open the SKILL.md file at the root directory to confirm the presence of mandatory fields like name and description, then review optional scripts, references, and assets directories to ensure they meet the standardized schema requirements.

The required frontmatter schema for automated validation mandates a name and description field in the SKILL.md file, while optional components, dependencies, categories, keywords, and toxicity checks are computed to support standardized indexing across a repository.

Yes, you can use automated discovery for skill units lacking assets, because the process aggregates optional directories like scripts and references while strictly enforcing only the mandatory SKILL.md frontmatter fields for validation and on-demand execution support.

Yes, you need a SKILL.md file at the root to compute dependencies, categories, keywords, and toxicity checks, because the validation process targets skill units with this root file to generate a structured, discovery-ready metadata package.

If your skill unit metadata is missing the mandatory name or description fields, the validation fails because the schema enforces these specific frontmatter properties in the SKILL.md file to enable consistent indexing and automated activation across the repository.