Reusable skills

A useful skill has a recognisable trigger, stable inputs, a bounded procedure and a checkable output.

Describe when to use it and when not to. List required capabilities, source of truth, approval boundaries and the exact verification step. Link long references rather than loading them for every task.

Test a representative job and a failure case. Ask a reviewer other than the author to inspect the result. A written skill with an unavailable dependency is not an operational workflow.

Prefer extending an existing method over creating a near-duplicate. Record ownership and review dates. Update dependent skills when a capability changes, and explicitly retire obsolete methods.