Skill Authoring

This skill is guidance, not a script. A skill is a reference for a reusable judgment; it earns its place when it changes a decision, not when it restates what a capable agent already does.

When not to use

• Project conventions, commands, or paths. Record them in the project's own documentation, not a skill.
• A constraint that can be enforced mechanically. Ship a gate or lint instead.
• Documentation placement or structure. Use canonical-docs.

Inputs and authorization

• Required: the judgment the skill should change and the situation that should trigger it. If either is missing, ask or stop.
• Authorization: authoring or editing a skill does not authorize changing unrelated skills, committing, or publishing.

Method

When to create a skill