unknown-field

To validate SKILL.md frontmatter, you check that required fields like name and description exist while gracefully ignoring extra or unknown fields so discovery and loading remain unaffected.

Unknown or extra YAML frontmatter fields are gracefully ignored during validation, ensuring non-critical metadata does not break skill discovery or loading processes.

Dependencies and components are determined by analyzing the skill's directory structure and contents, enforcing structural checks rather than relying solely on declared frontmatter fields.

Frontmatter validation does not require strict schema compliance for skill discovery, as it tolerates additional non-critical fields and only enforces the presence of name and description.

Validating skill frontmatter produces consistent structured metadata suitable for unit catalogs and tooling, alongside a toxicity assessment derived from the directory structure and contents.

Unknown frontmatter can affect skill discovery if validation lacks tolerance, but you can prevent this by using a validation process that ignores extra fields and enforces only required fields.