skills-and-capabilities

To decide if a capability is a skill or an extension, evaluate whether the behavior represents a reusable workflow unit or a platform-specific feature, applying classification policies for structure and placement.

Edit AGENTS.md instead of creating an instruction file when defining structural policies and placement boundaries for capabilities, ensuring maintainable architecture across knowledge and extension ecosystems.

The best way to classify capabilities is applying criteria to categorize them as skills, docs, instructions, extensions, or plugins, preventing fragmentation and maintaining clear architectural boundaries.

Using a single skill for both workflows and extension features risks misplacement; criteria distinguish reusable workflows from extension features to maintain clear boundaries and prevent architectural fragmentation.

Capability misplacement causes fragmentation because behavior lives in the wrong layer, blurring boundaries between durable docs, reusable skills, and extensions, which degrades maintainability and structural clarity.