The Claude Code team shares its lessons learned from hundreds of internal skills.

Anthropic's Claude Code team shares lessons from internal skills, revealing that verification skills and specific "gotchas" yield the highest code quality.

A skill is not a simple Markdown file but a complete folder of instructions, scripts, and resources: this insight comes from the Claude Code team, which shares lessons learned from hundreds of skills in internal use at Anthropic.

Their cataloging reveals nine categories, ranging from API references to incident runbooks and code scaffolding, with the best skills fitting into a single category, whereas those that overlap several disorient the agent. Verification skills show the most measurable impact on the quality of the code produced, to the point of justifying an engineer dedicating an entire week to them.

Regarding writing, the "gotchas" section concentrates the most valuable signal; descriptions are written for the model, as triggers rather than summaries intended for humans, and obviousness is to be avoided: Anthropic's frontend design skill exists precisely to steer Claude away from the Inter font and purple gradients. A skill can also embed memory (logs, SQLite) and temporary hooks, like /careful which blocks destructive commands during a sensitive session.

For distribution, a code repository suffices for small teams, with an internal plugin marketplace taking over at scale. The initial advice is brief: a few lines, a single gotcha, then enrichment as issues are encountered.