template-skill

To create a new skill, duplicate the skill template and update the SKILL.md frontmatter with your skill name, tagline, and description to establish discovery-friendly metadata. You then add operational guidance to the body.

SKILL.md metadata should include name, tagline, description, request, complexity, category, keywords, dependencies, components, and toxicity fields extracted from the skill's content and filesystem to ensure proper discovery.

The best way to standardize skill creation is to apply a consistent skeleton and frontmatter structure, providing ready-to-use description sections for problem, features, and quick start to guide future skills and onboard contributors.

No dependencies are required to use the skill template. It serves as a standalone skeleton that you can copy to bootstrap a new Skill Unit and rapidly define its metadata and operational guidance.

A skill description should include sections for the problem it solves, core features and use cases, and a quick start guide to effectively structure the skill's operational guidance and onboarding documentation.

Yes, you can use this template to structure operational guidance by extracting the name and description from the frontmatter and defining the body content, ensuring your new skills follow the same standardized structure.