Skill Use Cases

Skills sound nice in theory. But where do they actually help? Here are three scenarios where they shine.

1. Your Own Projects

You have a deploy step that has to run before the migration, and a log file that lives somewhere nobody would guess. Every few weeks you come back to this project and re-teach your agent both facts, usually after it gets one of them wrong.

A Skill turns that repetition into a one-time cost. The next session opens with the project's quirks already loaded — build order, the environment variable that must be set, the test that is flaky and can be ignored. You start at turn five instead of turn one.

The value here is not sophistication, it's continuity. Solo work generates a surprising amount of hard-won trivia, and almost all of it currently dies in a scrollback buffer.

2. Shared Workflows

One person on the team figures out how to get the release pipeline to behave: which check to re-run rather than debug, how to word a migration PR so review doesn't stall, the two lint rules everyone disables for the wrong reasons.

Normally this goes into a wiki page that gets read once, at onboarding, and is stale in a month. As a Skill it goes somewhere the agent looks by itself, so the second person to hit the problem doesn't have to know it was ever solved.

That changes the economics of writing things down. You aren't documenting for a hypothetical future reader who has to remember to search — you're teaching a tool that's already in the loop.

3. Production Agent Services

A customer-facing agent runs thousands of times a day, and the same three tasks account for most of that traffic. Every one of those runs currently rediscovers the procedure from the system prompt and whatever the model happens to recall.

Skills give those hot paths a fixed, reviewed instruction set. Three things get better at once: consistency, because runs stop diverging on the same task; cost, because a task that used to need eight turns of exploration needs four; and traceability, because when behaviour changes you can point at the version that changed it.

And because versions are scored on real traffic rather than argued about in review, improving a production prompt stops being a matter of taste.

Coming soon: detailed walkthroughs for each scenario, with the trajectories and Skills they produced.

So Skills are worth having. The remaining question is who writes them — and chapter C is about not having to.