What is superpowers?
superpowers is a Claude skill by obra that generate and explore ideas. It is listed under Other and has 301,280 GitHub stars.
| Type | Claude skill |
|---|---|
| Author | obra |
| Repository | obra/superpowers |
| Popularity | 301,280 GitHub stars |
| Category | Other |
| Security | Not scanned |
| Rank | #129 of 1,262 Claude skills; #16 in Other |
| License | MIT |
| Last commit | 2026-10-10 |
| Stars this week | +3,625 |
Is superpowers safe to install?
We have not scanned superpowers yet because its SKILL.md could not be fetched. Read the source before installing.
| Check | Result |
|---|
How do I install superpowers?
- Install with the skills CLI. Works for Claude Code and other agents that read skills.
npx skills add https://github.com/obra/superpowers --skill superpowers
- Or copy it by hand. Claude Code loads any folder with a SKILL.md from ~/.claude/skills.
git clone https://github.com/obra/superpowers cp -r superpowers/superpowers ~/.claude/skills/superpowers
- Use it. Claude loads the skill when a task matches its description. You can also name it in your prompt.
Use the superpowers skill to …
Or ask Claude to set it up
Paste this into Claude Code and it installs superpowers for you:
Install the "superpowers" skill from https://github.com/obra/superpowers into ~/.claude/skills, then tell me in one line what it does.
More from obra/superpowers
This repository has at least 9 Claude skills on MCPMods.
- brainstorming: You MUST use this before any creative work - creating features, building components, adding functionality, modifying beh (Low risk)
- systematic-debugging: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes (Low risk)
- writing-plans: Use when you have a spec or requirements for a multi-step task, before touching code (Low risk)
- using-superpowers: Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY respo (Low risk)
- requesting-code-review: Use when completing tasks, implementing major features, or before merging to verify work meets requirements (Low risk)
- test-driven-development: Use when implementing any feature or bugfix, before writing implementation code (Low risk)
- verification-before-completion: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verifi (Low risk)
- executing-plans: Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose (Low risk)