Skip to content
Founding Lifetime: every Pro skillfirst 100 members · $169 onceUpgrade
Lookbk
Sign In

Superpowers for Claude Code: how to install it and what it adds

How to install the Superpowers plugin in Claude Code, the two routes and how they differ, the 15 skills and the session hook it adds, and how to turn it off.

For
Claude Code users deciding whether to install Superpowers
Written for
Claude Code
Time
8 min read · updated Nov 21, 2026

The short answer

Superpowers is a plugin, not one skill: 15 skills for planning, test-driven development, debugging and code review, plus a hook that loads its “using-superpowers” text at the start of every session. In Claude Code, run /plugin install superpowers@claude-plugins-official, review the panel it opens, pick a scope and run /reload-plugins. The other route, /plugin marketplace add obra/superpowers-marketplace and then /plugin install superpowers@superpowers-marketplace, installs the same project from a third-party marketplace, which Claude Code does not auto-update by default. It is MIT licensed; the last release in our check was v7.0.2 on 3 November 2026.

Superpowers describes itself as a complete software development methodology for coding agents, built from composable skills and some initial instructions that make sure the agent uses them. Searching for it alongside Claude Code usually means one of three questions: how to install it, what it will change in your sessions, and how to undo it. This page answers those from the project’s repository and README and from Claude Code’s plugin documentation, read on 21 November 2026. We did not install it in Claude Code for this page, so what follows is what the files and docs say, not our review of how well it works.

Two ways to install it in Claude Code

The README gives two routes for Claude Code. They end at the same plugin from the same author; they differ in which marketplace Claude Code treats it as coming from.

The Claude Code install routes in the Superpowers README
TopicOfficial marketplaceSuperpowers marketplace
Commands/plugin install superpowers@claude-plugins-official/plugin marketplace add obra/superpowers-marketplace, then /plugin install superpowers@superpowers-marketplace
MarketplaceAnthropic’s official one, which Claude Code adds for you the first time you start an interactive sessionA third-party marketplace you add yourself
Auto-update, per Claude Code’s docsOn by defaultOff by default for third-party marketplaces
What the details pane shows, per the docsLast updated and a Context cost estimate, which appear when you open the plugin by naming its marketplaceThe components it adds; the docs tie Last updated and Context cost to the official marketplace
Claude Code
/plugin install superpowers@claude-plugins-official

In a session this command does not install straight away. Claude Code’s documentation says it opens the /plugin panel on the plugin’s details so you can review it and choose a scope first. The pane lists what the plugin adds, which can include hooks and MCP servers, and the docs say to read it before you install. Then choose a scope: user scope enables it for you in every project on the machine, project scope records it in .claude/settings.json for everyone in the repository, and local scope enables it for you in this repository only. When the panel asks, run /reload-plugins.

Claude Code
/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@superpowers-marketplace

Which to use: the official route shows more in the details pane and updates itself by default. The second route is the author’s own marketplace, which the README says provides Superpowers and some other related plugins. If you take it, updating is up to you, with /plugin marketplace update or the marketplace’s own auto-update setting. Best Claude Code plugins explains the /plugin panel and the scopes in full.

What it adds

The repository’s skills/ folder holds 15 skills. The README groups them by purpose, and the descriptions below are from its list.

The 15 skills in obra/superpowers, by the README’s grouping
GroupSkills
Testingtest-driven-development: the RED-GREEN-REFACTOR cycle
Debuggingsystematic-debugging (a four-phase root cause process), verification-before-completion, diagnosing-superpowers
Collaborationbrainstorming, writing-plans, executing-plans, dispatching-parallel-agents, requesting-code-review, receiving-code-review, using-git-worktrees, finishing-a-development-branch, subagent-driven-development
Metawriting-skills, using-superpowers

The README’s basic workflow chains seven of them: brainstorming before building anything, then using-git-worktrees, writing-plans, either subagent-driven-development or executing-plans, test-driven-development during implementation, requesting-code-review between tasks, and finishing-a-development-branch at the end. It says the skills trigger automatically, and that mandatory workflows are the point, not suggestions.

The part that is not a skill is a hook. The plugin ships a SessionStart hook that runs on startup, clear and compact. Its script reads the full text of the using-superpowers skill and hands it to Claude as context at the start of the session, so that skill’s instructions are in front of the model before you type anything. Those instructions say to invoke a relevant skill before any response, including clarifying questions, and to do so if there is even a 1% chance a skill applies. That is how the “skills trigger on their own” behavior is produced, and it is also why installing Superpowers is a bigger change to a session than installing one skill: it adds text to every session, and 15 skill descriptions to the list Claude reads.

Plugin or a single skill

Claude Code’s docs define a plugin as a directory of skills, agents, hooks, MCP servers and other components installed and loaded as one unit. Superpowers is installed that way. You can still copy one folder from its skills/ directory into ~/.claude/skills/, as with any skill, and the license is MIT. Without the plugin you lose the hook that loads using-superpowers, and some skills refer to others by name, so a single copied skill may point at skills you haven’t installed. Skills vs prompts, commands and plugins compares the forms.

Turning it off, updating it, what it reports

  • Turn it off. claude plugin disable superpowers@claude-plugins-official from a shell, or the Installed tab in /plugin. Disabling keeps it installed; claude plugin uninstall removes it. Use the marketplace name you installed from.
  • Update it. The official marketplace auto-updates by default per Claude Code’s docs. For the Superpowers marketplace, update it yourself. When Claude Code prints that a plugin updated, run /reload-plugins to load it in the open session. The README only says updates depend on the coding agent and are often automatic.
  • What it reports. The README says that, by default, the Prime Radiant logo in the brainstorming skill’s optional visual companion is loaded from its website and that this includes the Superpowers version, and nothing about your project, prompt or agent. SUPERPOWERS_DISABLE_TELEMETRY set to a true value turns it off, and it honors Claude Code’s DISABLE_TELEMETRY and CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC opt-outs.

Using it in another agent

The README is explicit that installation differs by harness and that if you use more than one you install Superpowers separately for each. It has sixteen install sections. A few examples from it: Cursor, /add-plugin superpowers in Agent chat; Gemini CLI, gemini extensions install https://github.com/obra/superpowers; GitHub Copilot CLI, copilot plugin marketplace add obra/superpowers-marketplace and then copilot plugin install superpowers@superpowers-marketplace; Codex through its plugin marketplace. The repository carries a separate plugin folder for several of them, including .cursor-plugin and .codex-plugin. For how each of those agents otherwise gets skills, see Cursor agent skills and agent skills marketplaces.

Before you install

Before you install Superpowers

Skills that make a finished file

Superpowers is about how the agent works: plans, tests, reviews. It doesn’t produce a deliverable you open afterwards. Lookbk’s skills do the other job: each one renders a file, such as a landing page, a slide deck, a link-preview image or a title video, and its page shows what it made. They are plain skill folders, so they sit alongside any plugin. These four are free.

Mono Editorial Landing: an example of what it makes
Free
web
Mono Editorial LandingClaude CodeCodexCursor+3 more agents
Swiss Grid Deck: an example of what it makes
Free
slides
Swiss Grid DeckClaude CodeCodexCursor+3 more agents
Editorial OG Card: an example of what it makes
Free
image
Editorial OG CardClaude CodeCodexCursor+3 more agents
Kinetic Title Drop: an example of what it makes
Free
video
Kinetic Title DropClaude CodeCodexCursor+3 more agents

Run the installer from inside Claude Code with the last part of a skill page’s address; it writes to ~/.claude/skills, the folder Claude Code reads.

Terminal
curl -fsSL https://lookbk.dev/cli.js | node - add mono-editorial-landing

Common questions

How do I install Superpowers in Claude Code?
Run /plugin install superpowers@claude-plugins-official, review the panel it opens, choose a scope and run /reload-plugins. Or add the author’s marketplace with /plugin marketplace add obra/superpowers-marketplace and install superpowers@superpowers-marketplace.
Is Superpowers a skill or a plugin?
A plugin that bundles 15 skills and a SessionStart hook. Claude Code installs and loads a plugin as one unit. You can copy a single skill folder out of it, but not the hook.
What does the Superpowers hook do?
On startup, clear and compact, it runs a script that reads the using-superpowers skill and passes its full text to Claude as context, telling it to check for relevant skills before it responds. You can read it in hooks/session-start in the repository.
Is Superpowers free?
The repository is MIT licensed. Its README also gives an email address for commercial support in enterprise use.
Which is better, the official marketplace or obra/superpowers-marketplace?
They install the same project. Per Claude Code’s docs the official marketplace auto-updates by default and shows Last updated and Context cost in the details pane, while third-party marketplaces do not auto-update by default.
How do I turn Superpowers off in Claude Code?
Run claude plugin disable superpowers@<marketplace> in a shell, or use the Installed tab in /plugin. claude plugin uninstall removes it.
Does Superpowers collect data?
The README says the logo in an optional visual companion is loaded from its website by default and includes the Superpowers version. Set SUPERPOWERS_DISABLE_TELEMETRY to a true value to turn it off.

Sources

What this guide says about other companies’ tools comes from their own documentation, checked on Nov 21, 2026.

Did this guide help?

See a skill’s result before you install it.

Every skill page shows what it makes, what it needs and which agents can run it.