skill-creator

To convert recurring workflows into reusable skills, you package the process into a formal skill definition with valid frontmatter, a clearly defined trigger, test guidance, and indexing into skills.md. This requires identifying a workflow that recurs three or more times.

Frontmatter is required metadata for skill creation, containing the skill name and description. It serves as the validated header for your workflow documentation, enabling proper indexing and discovery of the formal skill definition in skills.md.

To package a formal skill definition, draft a frontmatter-backed skill entry with a name and description, define a clear trigger, provide test guidance, and index the entry into skills.md. This process converts recurring task patterns into validated skills for discovery.

You need to formalize a workflow into a skill definition when a task pattern recurs three or more times across sessions. This recurring pattern indicates the workflow is ready to be packaged with frontmatter, tested, and indexed for iterative improvement based on real scenarios.

Skill creation requires test guidance as part of the formal skill definition. Along with valid frontmatter, a defined trigger, and indexing into skills.md, test guidance ensures the packaged workflow is validated and supports gradual promotion and iterative improvement across real scenarios.

The best way to index skills for discovery is to package the workflow into a formal skill definition and index it into skills.md. This requires valid frontmatter with a name and description, a clearly defined trigger, and test guidance to ensure proper indexing.