Stop re-explaining yourself to the AI: turn repeat work into skills

The second time you walk an AI through the same multi-step task, you are wasting your time and its context. Capture the recipe once as a skill and it stops being re-figured-out every session.

Watch how you actually work with an AI assistant over a week. You explain a multi-step task, it does the thing, everyone is happy. Next week the same task comes up and you explain the whole thing again from scratch. That second explanation is pure waste, and it is the exact moment a skill pays for itself.

What a skill actually is

A skill is a small file that captures a procedure the assistant should already know: the steps, the exact commands, the shapes of the data, and the gotchas you hit the first time. Once it exists you stop narrating the recipe and just say the trigger, and the assistant runs the known-good version instead of improvising a fresh one that might be subtly wrong.

When it is worth making one

Not everything deserves a skill. A genuine one-off, or a single command, is better left alone. Reach for a skill when two or more of these are true:

• You have done this exact thing before, in another session or copied out of a notes file.
• It is three or more steps and parameterizable: same recipe, different input (a stack, a ticket, a file, an environment).
• It took trial and error to get right, so the working version is worth not losing.
• You keep saying things like 'again' or 'every time we do this'.

The line that matters most

The highest-leverage part of a skill is not the steps, it is the one-line description of what it does and when to use it. That line is the trigger. The assistant only reaches for a skill when the description matches the moment, so it should lead with what the skill does and then spell out the exact phrases and situations that should fire it. Spend your effort there, not on prettier steps.

A skill turns a recipe you re-derive every session into one the assistant just knows. Write down what you actually ran and saw work, not what you hope works.

Keep it honest. Only put in steps you have verified, replace the specific values with placeholders so it travels to the next input, and never paste a secret into it. Do that and the hard part of the work, the part you sweated through once, stops evaporating at the end of the session.