custom-nested-skill

To validate SKILL.md frontmatter, scan multi-level directories to ensure each nested skill has required name and description metadata. This process checks for mandatory fields and detects optional resources in scripts, references, and assets directories.

A nested skill directory structure organizes skills across multiple levels. You need validation when maintaining a scalable skills repository to ensure consistent structure, required metadata presence, and activation readiness for each skill.

Yes, you can check for a working entry point by validating the skill's SKILL.md frontmatter. This confirms the presence of mandatory name and description fields required for activation and detects optional resource directories.

Detect optional resources by scanning the skills tree for scripts, references, and assets directories. The validation process identifies these optional paths alongside checking required metadata in the SKILL.md frontmatter.

Limitations include focusing solely on SKILL.md frontmatter validation for name and description fields. It detects optional resource directories but does not execute or validate the actual contents of scripts, references, or assets.

The best way to maintain a scalable skills repository is running validation passes over the skills tree. This verifies SKILL.md metadata consistency and exposes multi-level organization patterns to ensure activation readiness across nested directories.