skill-creator

Standardizing skill metadata requires applying a consistent YAML schema across the repository to generate structured fields like name, tagline, description, category, keywords, dependencies, and components for each detected skill unit.

Checking skill metadata for unsafe content involves computing a toxicity assessment during validation to guard against sensitive information or inadequate dependencies before publication.

YAML frontmatter validation works by detecting SKILL.md files and enforcing a strict schema that requires name and description fields, while also validating optional directories presence across the repository.

Yes, you can generate structured metadata fields for multiple skills by applying the validation process across the entire repository, detecting valid SKILL.md frontmatter to compute fields like name, tagline, category, keywords, dependencies, and components for each unit.

No external dependencies are required to validate skill metadata. The validation process operates standalone to detect SKILL.md frontmatter, enforce the YAML schema, and compute toxicity assessments without external libraries.