Write a skill

A skill is a pointer plus a procedure. The description decides whether it loads; the body decides what the agent does once it has. Write only what changes behavior you have observed.

Phase 1: Prove the gap

• Name the task, the observed failure and who hits it. Check existing skills and instruction files first; extend or fix one before adding another that competes for the same trigger.
• Run the task without the new guidance in a fresh context and record what the agent actually does, including the excuses it gives for skipping steps. If the baseline already succeeds, write nothing.
• Decide the scope: one job, one trigger family. Two unrelated triggers mean two skills.

Phase 2: Write the description

The description is always in context, so every word costs tokens across every session.