
Using Superpowers
This is the meta-skill that makes the entire Claude Code marketplace work. It forces Claude to actually invoke skills before doing anything, even asking clarifying questions. Without it, Claude will rationalize its way out of using skills 90% of the time with thoughts like "this is just a simple question" or "let me gather context first." It runs skill checks on literally every user message, creates todo lists from skill checklists, and establishes clear priority rules when multiple skills apply. Think of it as the dispatcher that ensures your other skills actually get used instead of sitting unused while Claude improvises.
- install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.
- 159
- skills.sh installs
- 283.7K
- GitHub stars
- 315.2K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add obra/superpowers --skill using-superpowers --agent claude-codeInstalls into .claude/skills of the current project.
Files
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. You cannot rationalize your way out of this.
The Rule
Invoke relevant or requested skills BEFORE any response or action — including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to use it.
Before entering plan mode: if you haven't already brainstormed, invoke the brainstorming skill first.
Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.
Skill Priority
When multiple skills apply, process skills come first — they set the approach, then implementation skills (frontend-design, etc.) carry it out. Brainstorming and systematic-debugging are Superpowers' most common process skills, but the rule holds for any of them.
Sponsors
Details
- Repository
- github.com/obra/superpowers
More from obra/superpowers
All 14- Requesting Code Review276.5K
- Test Driven Development274.8K
- Verification Before Completion270.3K
- Executing Plans257.5K
- Subagent Driven Development252K
- Receiving Code Review235.1K
- Dispatching Parallel Agents231.3K
- Writing Skills231.3K
- Using Git Worktrees230.2K
- Finishing A Development Branch227.7K
- Brainstorming423.3K
- Systematic Debugging326.7K
- Writing Plans298.6K