template-skill

To generate standardized metadata from a SKILL.md file, you parse its YAML frontmatter to extract the name and description, then augment it with tagline, category, keywords, dependencies, and components.

Defining a reusable AI assistant skill blueprint requires using a standard frontmatter-driven schema in a SKILL.md file to produce a complete, discovery-friendly metadata block for consistent downstream tooling.

Metadata discovery for Markdown-based skill definitions works by parsing the YAML frontmatter and detecting optional directories like scripts/ or assets/ to automatically determine the skill's real-world components.

Yes, you can use this skill template to evaluate toxicity, as it includes safety and governance features designed to guard against unsafe content and misconfiguration during metadata generation.

No external dependencies are required to parse a SKILL.md frontmatter, as the skill operates directly on the repository structure and Markdown files without needing additional packages or modules.

Your skill metadata lacks component awareness because the analyzer detects optional folders like scripts/, references/, and assets/ to reflect the real-world structure, requiring their actual presence in the repository.