your-skill-name

You can generate YAML metadata by scanning a repository root for a valid SKILL.md file, extracting the required name and description from the frontmatter, and outputting a single YAML document per unit.

Automating skill discovery involves validating the presence of SKILL.md at the repository root and ensuring mandatory frontmatter fields exist before inferring optional components from directory structures.

Inferring dependencies checks for the existence of scripts/, references/, and assets/ directories within the Skill Unit repository to automatically populate corresponding component fields in the final YAML output.

Yes, a SKILL.md file must be located at the repository root to validate the Skill Unit, as the pipeline requires it to extract the name and description fields for marketplace readiness.

Yes, the metadata template pipeline automatically assigns category, complexity, and keywords while validating the frontmatter and aggregating optional resources into a clean YAML document.

The extraction pipeline outputs an is_toxic status alongside the category, complexity, and keywords to indicate the safety or validity classification of the parsed Skill Unit metadata.