Skills Board vs Superpowers

01 / Context

Where an installed methodology stops being the whole answer

Superpowers is opinionated on purpose, and that is most of its value. The gap shows up around it rather than inside it.

• It ships one curated methodology. The contributing section says the project does not generally accept contributions of new skills, so it is not the place your own skills go.
• It installs once per harness. The README carries fourteen separate install sections, from Claude Code to Codex, Cursor, Gemini CLI, and OpenCode, and says to install separately for each one you use.
• In Claude Code, plugin skills load where the plugin is enabled and answer to a plugin-name:skill-name command, so what a teammate has depends on which plugins that teammate turned on.
• The skills that describe your product, your deploy path, and your review conventions will never ship inside somebody else's plugin.
• Nothing in a plugin records which of its fourteen folders your team actually settled on, or why.

02 / Comparison

Side by side

One is a method you install. The other is where your team's AI skills live.

03 / Pick the other one

When Superpowers is the thing to install

This is a real product solving a real problem, and for a lot of people it is the right answer on its own.

• You want an opinionated process rather than a menu: design first, plan, then implement, with the skills triggering on their own.
• You want red and green TDD run as a cycle, write the failing test, watch it fail, write the minimal code, watch it pass, rather than as a suggestion.
• You want subagent-driven development with a two-stage review, spec compliance first and code quality second, without building it yourself.
• You work alone or on one harness, so a single plugin install already covers everyone who needs it.
• You would rather the method arrive as a versioned plugin that updates itself than as a list a person keeps current.

04 / Pick the library

When a team registry fits better

Skills Board starts from a smaller problem: your teammates cannot find your team's AI skills.

• The skills you need most are about your product, your deploy path, and your review conventions, so no third-party plugin will ever ship them.
• Teammates run different agents, and you would rather keep one entry than one install command per harness.
• You want people to search by the task they are doing and see the original source before they use anything.
• You want a compatible agent to search the same team list over an authenticated MCP endpoint instead of asking a person.
• You want teammates who never install a plugin, including designers, writers, and product folks, to reach the same set.

05 / How to run it

Running Superpowers and a team registry together

Nothing here replaces the plugin. This is the short path from an installed method to a list your team can search.

1. 1Keep Superpowers installed in the agents where you want its methodology.
2. 2Create a team library and save the Superpowers folders your team settled on, from github.com/obra/superpowers, so each entry points at the SKILL.md a teammate can read.
3. 3Save the skills your team wrote itself next to them, each from its own repository and path.
4. 4Tag both sets the way your team searches, by workflow or by the surface the skill belongs to.
5. 5Invite your teammates, or connect a compatible agent over MCP so it can search the same list without leaving the agent.

06 / Questions

Frequently asked questions

Is Skills Board a replacement for Superpowers?

No. Superpowers is an installed plugin that gives a coding agent one development methodology. Skills Board is the web app where a team keeps and shares its AI skills, whatever those skills came from. Teams commonly install Superpowers and save the folders they settled on to their team library.

Can I save Superpowers skills to Skills Board?

Yes. Superpowers is a public MIT-licensed repository and each of its fourteen skill folders holds a SKILL.md, so saving one records the original repository and path and a teammate opens the same folder you did.

Does Skills Board install or run skills?

No. It records the original repository and path, and offers the source link, an install command, or a ZIP of the latest files available at download time. Installing Superpowers is still a plugin install inside your agent.

Is Superpowers only for Claude Code?

No. The README documents install steps for fourteen harnesses, Claude Code, Antigravity, Codex, Cursor, Devin CLI, Factory Droid, Gemini CLI, GitHub Copilot CLI, Grok Build CLI, Kimi Code, OpenCode, Pi, and Hermes Agent among them, and asks you to install it separately for each one you use.

What does Skills Board cost?

The hosted product is free forever, with no trial, credit card, or paid tier. The code is MIT licensed and open source.

Sources

• obra/superpowers on GitHub

  The public repository, the fourteen folders under skills/, and the MIT license file with its copyright line.

• Superpowers README

  The methodology description, the per-harness install sections, the workflow and skills library listings, the note on contributing new skills, updating, and commercial support.

• Superpowers plugin manifest

  The plugin name, description, version, author, and MIT license as declared to Claude Code.

• anthropics/claude-plugins-official

  The official marketplace manifest that lists superpowers in the development category and points at github.com/obra/superpowers.

• Claude Code documentation, Skills

  Where plugin skills live on disk, that they are available where the plugin is enabled, and the plugin-name:skill-name namespace.

Keep reading