Skip to content

skillsmith

A skill is a reusable behavior contract, not a project manifesto.

Ask: what repeated task fails, when should the skill trigger, what minimum inputs are needed, what concrete output should result, how is success verified, and what must it not do?

A good skill has a narrow trigger, bounded context, ordered process, human checkpoints where needed, concrete output, stop condition, and conflict-free guardrails.

Teach through one relevant example and one anti-example. Keep version one small and easy to delete.