Practice Skill Authoring

What problem does it solve?

Guides creators through the missing discipline behind Practice skills so every methodology is scenario-agnostic, falsifiable, and publishes knowledge that outlives a single session.

Core Features & Use Cases

• Focus and scope guardrails clarify how to describe methodology intent, why it matters, and when to invoke it, keeping the skill firmly in the Practice category.
• Structured phases with decision points demand exit/entry criteria, observable actions, and artifact production so agents can trace progress and validate hypotheses.
• Convergence patterns and artifacts pair diagrams, tables, or checklists with explicit knowledge-capture requirements, ensuring tests, docs, or reports persist beyond the conversation.
• Anti-patterns and boundaries warn against common missteps and explain what the skill intentionally does not cover, preventing scope creep and promoting reuse; a team outlining a new hypothesis-driven debugging methodology will use these sections to align reviewers and future practitioners.

Quick Start

Draft a Practice skill by following the template's focus statement, phased process, convergence aids, artifact expectations, anti-patterns, and boundary clauses.