Superpowers (obra) Review
A community skill collection that turns Claude Code into a more aggressive, opinionated builder — with sharper triggers and tighter feedback loops.
What it is
Superpowers is a community-maintained skills collection for Claude Code that pushes the official format harder. Where Anthropic's repo is conservative and reference-grade, Superpowers is opinionated, aggressive, and designed for people who want Claude to be less polite and more useful.
What it actually does
The collection bundles skills for verifying work, hunting bugs, writing tests before code, breaking tasks into chapters, and committing in surgical slices instead of dumps. Each skill takes a stronger position than its official equivalent — the verification skill, for instance, refuses to mark work "done" without running an actual reproduction, not just a typecheck.
The maintainer treats this as a working set, not a museum. Skills get rewritten when they fail in real sessions, deprecated when something better lands, and named after the behavior they enforce rather than the domain they cover. That maintenance discipline matters: a skill repo is only as useful as the consistency of its conventions, and Superpowers keeps tighter conventions than most.
The trade-off is that it's more opinionated than the official repo, which means it sometimes argues with you about how to do your own work. For some users that's the value. For others it's friction.
When to use it
- You've outgrown the official skills repo and want a more battle-tested set.
- You want Claude to be more skeptical, more verification-heavy, more commit-disciplined by default.
- You're a solo operator or small team where strong defaults beat configurable defaults.
- You want to read someone else's working skill set as a reference for writing your own.
When NOT to use it
- Your team has its own opinionated workflow that an outside skill set will fight.
- You want skills that just work without thinking about what they enforce.
- You need long-term stability — community repos can change direction without notice.
Pros
- More opinionated and more useful than the official repo for real engineering work.
- Verification + commit-discipline skills materially reduce shipped-broken-code rate.
- Active maintainer who treats the repo like working software, not a portfolio piece.
Cons
- Opinionated to the point of friction if your workflow disagrees with the maintainer's.
- Less documentation than the official repo — you have to read SKILL.md files to understand each one.
- Single-maintainer risk — the repo is as durable as its author's interest.
Use Superpowers if you want Claude Code to behave like a senior engineer who pushes back; skip it if you prefer your tools to do exactly what you ask without arguing.
Install / access
git clone https://github.com/obra/Superpowers.git ~/superpowers && cp -r ~/superpowers/<skill-name> ~/.claude/skills/