● Community
obra
⚡ Instant
superpowers
by obra · obra/superpowers
Curated power-user skill bundle from obra — opinionated workflows for git, debugging, planning, and prompt-craft.
obra/superpowers (by Jesse Vincent, ex-Anthropic) packages a tight set of high-leverage skills for Claude Code: git habits, debugging discipline, planning loops, and meta-skills for working *with* Claude effectively. Smaller and more opinionated than the wshobson family — pick this if you trust the curator's taste.
Why use it
Key features
- Tight, opinionated skill set (not a kitchen sink)
- Includes meta-skills: how to brief Claude, how to self-review
- Strong git workflow skills (rebase, cherry-pick, bisect)
- Debugging and planning loops
- MIT licensed
Live Demo
What it looks like in practice
ready
Install
Author repository · Claude Skills documentation
In Claude Code, install the plugin from the official Claude plugin marketplace, as documented by the author:
/plugin install superpowers@claude-plugins-official
Follow the author installation instructions for your client; install separately in each client you use.
Use Cases
Real-world ways to use superpowers
When to use: Feature is fuzzy and you'd benefit from forced reflection.
Flow
-
Trigger plan skill
Apply the planning skill. Feature: per-user rate limiting that scales to 10k req/s.✓ Copied
→ Skill asks for constraints, success criteria, alternatives
-
Iterate on the plan
Push back on each assumption. What would Linus reject?✓ Copied
→ Stronger plan with explicit risks
-
Translate to first PR
What's the smallest first PR that proves the plan?✓ Copied
→ MVP-shaped first step
Outcome: A plan you'd defend in design review, not just one you guessed.
When to use: You've got a bad merge, lost commits, or rebase gone sideways.
Flow
-
Diagnose
Apply the git-rescue skill. Show me what's salvageable: reflog, stash, dangling commits.✓ Copied
→ Inventory of recoverable state
-
Rebuild
Plan the recovery. Run only after I confirm.✓ Copied
→ Proposed sequence of git ops with explanations
-
Verify
After recovery, confirm tree is what I expected.✓ Copied
→ Final tree matches intent
Outcome: Recovered branch state without losing work.
When to use: You want the model to audit itself before you do.
Flow
-
Trigger self-review
Apply self-review skill on the diff you just produced. Be harsh.✓ Copied
→ Specific concerns, not generic 'looks good'
-
Address findings
Fix every sev-1 finding. Ignore sev-3 if it's nitpicks.✓ Copied
→ Tighter diff
Outcome: Higher-quality output without you having to be the only critic.
Combinations
Pair with other MCPs for X10 leverage
Plan with superpowers, execute with wshobson agents
Plan via superpowers/planning; delegate implementation to backend-architect.✓ Copied
Two opinions stacked
Use both skill sets — superpowers for git, wshobson for testing.✓ Copied
Cost & Limits
What this costs to run
- API quota
- N/A — local
- Tokens per call
- Skills are concise here — lower per-trigger cost than larger sets
- Monetary
- Free (MIT)
- Tip
- This is the lighter set — fewer tokens per skill than wshobson
Security
Permissions, secrets, blast radius
Minimum scopes: filesystem-read
Credential storage: None
Data egress: None
Troubleshooting
Common errors and fixes
Trigger collisions with wshobson
Skills auto-route by description; rename one if both fight for same intent
Alternatives
superpowers vs others
| Alternative | When to use it instead | Tradeoff |
|---|
| wshobson/skills | You want broader coverage | Bigger but less curated |
| anthropics/skills (official) | Anthropic-official starter set | Official baseline; superpowers adds opinion |