skill-architect

To create a reusable skill from an existing workflow, define discovery goals, choose a primary pattern, and draft frontmatter before generating the SKILL.md file. This process enforces modularity and progressive disclosure, turning ad-hoc workflows into deliberate, ready-to-ship skills.

The best way to structure a SKILL.md file is by following a disciplined workflow: Discovery, Architecture, Craft, Validate, and Deliver. This ensures deliberate creation with mandatory frontmatter fields, versioning, and clear success criteria for agent consistency.

Frontmatter validation improves skill architecture by enforcing mandatory fields and versioning early in the design process. This discipline prevents ad-hoc templates and ensures the final SKILL.md meets quality gates and anti-pattern checks for reliable delivery.

Yes, you can use this approach to build both standalone skills and MCP-enhanced workflows. The architecture process addresses turning workflows into reusable skills and automating tasks by applying progressive disclosure and validation to both contexts.

Generating SKILL.md without discovery and architecture phases leads to ad-hoc templates lacking modularity. Skipping these phases risks failing quality gates, missing frontmatter validation, and delivering inconsistent agent actions without clear success criteria.