Claude Code skills | Blog

~/blog/tag/skills

Skills

The smallest unit of teaching an agent something it cannot infer. What Skills are, how to write them, and where they fall apart.

What I write about here ​

A Skill is a small, named bundle of instructions that an agent loads on demand. Not a tool, not a plugin, not a prompt template. Closer to a piece of institutional knowledge written down so the agent can read it the next time it needs to.

The framing matters. A Skill is what you reach for when the agent keeps doing the same thing wrong and you keep correcting it the same way. Write it down once. Let the agent invoke it next time. That's the whole idea.

The posts under this tag look at Skills the way I look at any tool. What they're good at, where they leak, and what people get wrong when they reach for one. I write Skills for myself a lot. Some hold up. Some get rewritten three times before they stick. The patterns I keep coming back to are in these posts.

Read these expecting opinions, not just walkthroughs. A Skill that solves the wrong problem cleanly is worse than no Skill at all.

How Skills fit into the rest of an agent setup is covered in the Agentic coding guide.

latest
Skillstooling
0.06%of tokens were output8 minClaude Pro #40

Claude Code Superpowers: what subagent-driven development costs in tokens

I counted every token of a month of my own Superpowers runs: eleven plans, 407 subagent dispatches, 3.3 billion tokens. Writing code was 0.06% of it. The rest was contexts being read again, and the fresh subagent per task only stayed cheap while the task stayed small.

read