What coding skills do
Coding skills are workflows, not libraries. Most of them are a single SKILL.md that tells Claude Code what to do before, during and after a change: ask questions first, write a failing test, find the root cause before patching, or check its work before it says "done".
Four collections make up most of this list:
- Matt Pocock's skills (
mattpocock/skills): planning and design interviews such asgrillingandgrill-with-docs,tdd,diagnosing-bugs,improve-codebase-architecture, and handoff skills for passing work between sessions. - Superpowers (
obra/superpowers): a connected set wherebrainstormingleads towriting-plans, thenexecuting-plansorsubagent-driven-development, withsystematic-debugging,test-driven-developmentandverification-before-completionalong the way. - Addy Osmani's agent skills (
addyosmani/agent-skills): engineering practices such asspec-driven-development,code-review-and-quality,security-and-hardeningandperformance-optimization. - Caveman (
juliusbrussee/caveman): a terse "caveman" answering style that keeps the technical facts and drops the filler, plus related skills for commits, reviews and refactoring.
How to choose
Pick one collection to start with rather than mixing several. Skills in the same collection often call each other by name (Superpowers' brainstorming skill ends by invoking its writing-plans skill), so installing the whole set works better than picking single files from different authors.
Several of these skills are meant to be run on purpose rather than picked up automatically. Matt Pocock's grill-me, for example, sets disable-model-invocation: true, so you start it by typing /grill-me.