New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Superpowers

by Peiiii in Peiiii/nextclaw

A skill your agent uses when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or…

MITAuto-check passedAgent Workflows

Install Superpowers

skills CLI
$ npx skills add Peiiii/nextclaw --skill superpowers -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Peiiii/nextclaw superpowers --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/superpowers .claude/skills/superpowers && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
superpowers
GitHub stars
260
Token cost
~2.1k tokens
SKILL.md length
917 words
Files
11 (incl. references)
Skills in repo
70
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or…

  • Works in 5 steps: Verify bundled references exist → Classify the user's need → Load only the matching reference → …
  • The user wants a disciplined software development workflow with design-first planning
  • SKILL.md covers Overview, What This Skill Covers, What This Skill Does Not Cover and Install Boundary, plus 6 more sections
  • Reaches github.com

What it does

Superpowers is an agent skill from Peiiii/nextclaw. Use when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or verification-before-completion, adapted from obra/superpowers.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `marketplace.json`, `references/SOURCES.md` and `references/brainstorming.md`).

It sits in Agent Workflows, covering Planning, Verification before completion and Debugging. The repository describes itself as: A human-centered long-term AI partner—not a task-centered assistant. The licence is MIT.

When your agent uses it

  • The user wants a disciplined software development workflow with design-first planning
  • Implementation plans
  • Systematic debugging
  • Verification-before-completion

Example prompts

  • “/superpowers”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Verify bundled references exist
  2. Classify the user's need
  3. Load only the matching reference
  4. Reconcile with host rules before acting
  5. Execute with honest boundaries

What it can do on your machine

Read from SKILL.md and the folder at commit 973722e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Superpowers loads about 2.1k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 917 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~16k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Peiiii/nextclaw at commit 973722e, republished under its MIT licence (© Peiiii). 917 words, ~2,119 tokens.

Download SKILL.mdSave it as .claude/skills/superpowers/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
superpowers
description
Use when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or verification-before-completion, adapted from obra/superpowers.

Superpowers

Overview

Use this skill when the user wants a stronger engineering workflow inside NextClaw.

This marketplace skill adapts the upstream obra/superpowers project into a single installable NextClaw skill. Because NextClaw marketplace installs one skill directory at a time, this package provides:

  • one top-level workflow router,
  • bundled local reference files for the most useful upstream superpowers skills,
  • and clear rules for when to load which reference.

Be explicit about the boundary:

  • This skill owns workflow selection, expectation-setting, and reference routing.
  • The bundled reference files own the detailed superpowers methodology.
  • NextClaw, the current project rules, and the actual tool runtime own execution.

Do not present bundled superpowers guidance as a higher-priority authority than the user's instructions, the current project's AGENTS.md, or the host platform's rules.

What This Skill Covers

  • design-first brainstorming before implementation,
  • implementation plan writing for multi-step work,
  • test-driven development for feature and bugfix work,
  • root-cause-first debugging,
  • pre-merge or post-task code review prompts,
  • evidence-before-claims verification,
  • optional subagent-driven execution when the environment actually supports it.

What This Skill Does Not Cover

  • overriding user instructions or project rulebooks,
  • pretending NextClaw natively supports the upstream superpowers multi-directory auto-discovery model,
  • forcing subagent workflows when the current runtime does not support them,
  • claiming a workflow step happened when the needed evidence was not actually collected,
  • replacing domain-specific project skills that are more specific than this general workflow skill.

Install Boundary

Always distinguish these paths:

  • NextClaw marketplace install: nextclaw skills install superpowers
  • Installed NextClaw skill assets: <workspace>/skills/superpowers/
  • Upstream standalone installation outside NextClaw: clone https://github.com/obra/superpowers and follow the upstream install docs

For NextClaw users, prefer the marketplace-installed assets already bundled under skills/superpowers/.

Do not ask the user to install the upstream repo separately unless they explicitly want the original Codex or Claude plugin setup outside NextClaw.

Deterministic First-Use Workflow

When this skill triggers, follow this order.

Step 0: Verify bundled references exist

Check:

bash
test -f skills/superpowers/references/brainstorming.md
test -f skills/superpowers/references/systematic-debugging.md

If either file is missing, the skill is not correctly installed in the current workspace.

Step 1: Classify the user's need

Choose the smallest matching workflow:

  • feature or behavior design,
  • implementation planning,
  • implementation or bugfix execution,
  • debugging an existing problem,
  • review before merge or handoff,
  • verification before claiming completion,
  • plan execution with parallel agents.
Step 2: Load only the matching reference

Read only the smallest relevant reference instead of loading everything at once:

Do not bulk-read all references unless the task truly spans multiple workflow stages.

Step 3: Reconcile with host rules before acting

Before following any bundled superpowers guidance, reconcile it with:

  • the user's explicit request,
  • the current repository's AGENTS.md,
  • the host runtime's tool and permission model,
  • and any more specific installed skill that directly matches the task.

If there is a conflict, follow the higher-priority local rule and use the bundled superpowers material as methodology, not authority.

Step 4: Execute with honest boundaries
  • Prefer the project's existing validation and review commands when they already exist.
  • If the current repository has stricter branching, testing, review, or release rules, follow those.
  • If the environment lacks multi-agent support, skip the subagent path and continue with the non-delegated workflow.
  • If the task is trivial, keep the workflow compact rather than theatrical, but still choose an explicit workflow.
Show full SKILL.md (358 more words)Show less

Workflow Routing Guidance

New feature, refactor, or behavior change

Start with:

If the work becomes multi-step or cross-module, continue with:

During implementation, use:

Before declaring success, use:

Bug, failing test, or unexpected behavior

Start with:

Once root cause is understood and a fix is ready, use:

Before closing the task, use:

Review or handoff checkpoint

Use:

If the work was executed from a formal plan and the runtime supports delegation, optionally use:

Safe Usage Rules

  • Treat the bundled references as workflow assets, not as license to ignore local project rules.
  • Prefer the smallest process that still makes the work explicit and honest.
  • Do not claim TDD happened unless a failing test was observed first.
  • Do not claim a bug is fixed unless the original failure mode was re-verified.
  • Do not claim completion without fresh verification evidence.
  • Do not require subagent usage when the current runtime, product tier, or user request does not support it.

Troubleshooting

Reference files missing
  • Re-check the skill installation.
  • Confirm skills/superpowers/ exists in the active workspace.
  • Reinstall the marketplace skill if needed instead of inventing fallback paths.
The current project already has stricter workflow rules
  • Follow the stricter local rule.
  • Use superpowers references only for the missing part of the workflow.
The task needs the upstream standalone ecosystem
  • Be explicit that the marketplace skill is a NextClaw adaptation, not the original multi-plugin install.
  • Point the user to the upstream repository and install docs only if they want that exact standalone setup.
The user wants speed over process
  • Compress the workflow, but still keep the key gates:
    • clarify intent for creative work,
    • find root cause before fixing bugs,
    • verify before claiming completion.

Success Criteria

This skill is working correctly when:

  • the user gets an explicit workflow instead of ad-hoc thrashing,
  • the smallest relevant superpowers reference is loaded for the task,
  • local project rules remain the source of truth,
  • debugging starts with root-cause investigation,
  • implementation uses test-first discipline when appropriate,
  • and completion claims are backed by fresh verification evidence.

Attribution

This skill adapts the upstream obra/superpowers project for the NextClaw marketplace.

Upstream source mapping is documented in references/SOURCES.md.

© Peiiii, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references) in skills/superpowers of Peiiii/nextclaw.

  • SKILL.md
  • UPSTREAM_LICENSE
  • marketplace.json
  • references/SOURCES.md
  • references/brainstorming.md
  • references/requesting-code-review.md
  • references/subagent-driven-development.md
  • references/systematic-debugging.md
  • references/test-driven-development.md
  • references/verification-before-completion.md
  • references/writing-plans.md

Open the folder on GitHubat commit 973722e

Compare with similar skills

Superpowers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Superpowers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Superpowers this skillPeiiii/nextclaw260—~2.1kAutomated safety check: PassMIT
Vibe ImplementidiotLeoLYJ/Daliu-Awesome-Skills140—~2.7kAutomated safety check: PassNone
Plan Py4vaspvasp-dev/py4vasp100—~2.3kAutomated safety check: PassApache-2.0
Verification Before Completionforyourhealth111-pixel/Vibe-Skills3.6k—~1.1kAutomated safety check: PassApache-2.0
Inline Plan ExecutionjnMetaCode/superpowers-zh8.3k—~2.5kAutomated safety check: PassMIT
Create Featurezacharyfmarion/openscad-studio238—~1.5kAutomated safety check: PassGPL-2.0

Similar skills

  • Vibe Implement

    idiotLeoLYJ/Daliu-Awesome-Skills

    Vibe Coding 流水线的实现阶段(流水线终点,顺序 idea → interaction → architecture → design → prototype → implement)。当 interaction.md、architecture.md、design.md、prototypes/ 已就绪,用户说"开始实现""写代码""把设计落地""进入开发""implement /…

    140 GitHub stars~2.7k tokensUpdated 29 days ago
    Agent WorkflowsAuto-check passed

  • Plan Py4vasp

    vasp-dev/py4vasp

    Plan a py4vasp change as an ordered list of test-first chunks — that chunk list is the plan.

    100 GitHub stars~2.3k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Verification Before Completion

    foryourhealth111-pixel/Vibe-Skills

    Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.

    3.6k GitHub stars~1.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Inline Plan Execution

    jnMetaCode/superpowers-zh

    Executes a written implementation plan task by task in the current session, with a progress ledger, test-first gates and one fresh-context review at the end.

    8.3k GitHub stars~2.5k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed

  • Create Feature

    zacharyfmarion/openscad-studio

    A skill your agent uses when the user asks to take a feature or bug fix from prompt to implementation, especially prompts like "/create a new feature", "build this feature end-to-end", "take this…

    238 GitHub stars~1.5k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Auditable Playbook Designer

    cursor/plugins

    Official

    Designs a step-by-step playbook for large or unfamiliar work, runs it as a loop of hypotheses and measurements, and logs decisions so a human can review them later.

    10k GitHub starsUsed in 8 repos~1k tokens
    Agent WorkflowsAuto-check passed

More from Peiiii/nextclaw

All 70 skills in this repo

  • Nextclaw Skin Studio

    Peiiii/nextclaw

    A skill your agent uses when a user wants to browse, apply, inspect, create, refine, switch, or remove a NextClaw skin; wants a personal skin with arbitrary CSS, JavaScript, images, SVG, DOM…

    260 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

  • Development Task Telemetry

    Peiiii/nextclaw

    A skill your agent uses when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard…

    260 GitHub stars~802 tokensUpdated yesterday
    Auto-check passed

  • Nextclaw Product Visual Assets

    Peiiii/nextclaw

    当 NextClaw 产品更新后需要生成、替换、挑毛病或检查官网、GitHub README、用户文档或社交传播中的真实截图、AI 宣传视觉、整页 HTML 宣传预览、社区二维码等对外视觉资产时使用；也用于“更新截图”“重新截一批图”“做宣传页”“生成 campaign 页面”“视觉审稿”“五星挑刺法”或发布前检查视觉资产。普通站点布局开发或只写文章不触发。

    260 GitHub stars~801 tokensUpdated yesterday
    Auto-check passed

  • UI UX Pro Max

    Peiiii/nextclaw

    A skill your agent uses when the user wants professional UI/UX design guidance, design-system generation, UX review, or stack-specific frontend guidance through a bundled local UI/UX Pro Max dataset…

    260 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Impeccable

    Peiiii/nextclaw

    A skill your agent uses when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable…

    260 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

  • Nextclaw Skill Resource Hub

    Peiiii/nextclaw

    Curate NextClaw skill resources, including OpenClaw and community sources.

    260 GitHub stars~479 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Superpowers

What does Superpowers do?

A skill your agent uses when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or…. Superpowers is an agent skill from Peiiii/nextclaw. Use when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or verification-before-completion, adapted from obra/superpowers.

When should I use Superpowers?

Superpowers fits situations like: the user wants a disciplined software development workflow with design-first planning; implementation plans; systematic debugging; verification-before-completion.

How do I install Superpowers in Claude Code?

Run `npx skills add Peiiii/nextclaw --skill superpowers -a claude-code`. Or copy the skill folder (skills/superpowers in Peiiii/nextclaw) into .claude/skills/superpowers in your project. Claude Code loads it when a task matches its description.

How do I install Superpowers in Codex?

Run `npx skills add Peiiii/nextclaw --skill superpowers -a codex`. Or copy the skill folder (skills/superpowers in Peiiii/nextclaw) into .agents/skills/superpowers in your project. Codex loads it when a task matches its description.

Can I use Superpowers in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Peiiii/nextclaw --skill superpowers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/superpowers, .gemini/skills/superpowers, .github/skills/superpowers and .opencode/skills/superpowers in your project.

What does Superpowers need to run?

SKILL.md names no scripts, command-line tools or credentials: Superpowers is instructions for the agent only.

Does Superpowers access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Superpowers safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Superpowers use?

Superpowers is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Superpowers use?

About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.

What are the alternatives to Superpowers?

Skills that share tags, products or a category with Superpowers: Vibe Implement (idiotLeoLYJ/Daliu-Awesome-Skills, 140 stars), Plan Py4vasp (vasp-dev/py4vasp, 100 stars), Verification Before Completion (foryourhealth111-pixel/Vibe-Skills, 3.6k stars) and Inline Plan Execution (jnMetaCode/superpowers-zh, 8.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Superpowers?

Peiiii (a GitHub user) maintains it in Peiiii/nextclaw, which has 260 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 7, 2026.

Source: Peiiii/nextclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.