<Name>

Metadata extraction from SKILL.md frontmatter is automated by parsing mandatory fields like name and description, detecting optional resource directories such as scripts/ and references/, and outputting a structured JSON file for tooling.

Skill metadata validation ensures secure deployment by applying toxicity checks and verifying mandatory fields in SKILL.md files, guaranteeing that only well-scoped and safe Skill Units are activated in the repository.

Generating structured JSON from YAML frontmatter involves reading the SKILL.md file, validating mandatory and optional fields, capturing resource references, and emitting a standardized metadata JSON object to inform discovery and activation.

Yes, skill metadata generation detects dependency references automatically by scanning for optional resource directories like scripts/, references/, and assets/ during the SKILL.md analysis to populate the structured JSON output.

Yes, you can validate mandatory fields in SKILL.md files without external dependencies, because the analyzer operates independently to check for required name and description fields while flagging toxicity status.

The primary limitation of automated skill metadata extraction is its strict reliance on standardized SKILL.md frontmatter formatting, meaning malformed YAML or missing mandatory fields will prevent successful JSON generation and validation.