{skill-name}

You enforce consistent frontmatter by applying a standard template to new Skill Unit directories under .squad/templates. This ensures fields like name, description, complexity, category, and dependencies follow a standard for reliable search and retrieval.

A Skill Unit structure standardizes how skills are documented and discovered across a repository. You need it when automating onboarding and ensuring automated tooling can validate, categorize, and surface skills reliably.

To create a new Skill Unit, duplicate the skeleton template under the appropriate .squad/templates path and fill in the actual content in the provided sections. This applies consistent conventions for automated discovery and tooling.

Yes, you can use this template to standardize codebase conventions. It centralizes governance artifacts like patterns and anti-patterns, enabling automated tooling to validate, categorize, and surface skills for discovery.

The best way to automate discovery is enforcing a consistent frontmatter and structure for new Skill Units. This centralizes governance artifacts and ensures fields follow a standard for reliable search and retrieval.

Skill discovery fails because automated tooling relies on a consistent frontmatter and structure to validate and categorize skills. Without standard fields like name, category, and dependencies, reliable search and retrieval cannot work.