Superpowers vs Vercel Agent Skills · Scriptiii AI Tools
Superpowers vs Vercel Agent Skills
In short
Superpowers vs Vercel Agent Skills: both are coding tools on Scriptiii AI Tools. Superpowers pricing: Free. Free to use. (reported by the maker) Vercel Agent Skills pricing: Free. Free to use. (reported by the maker) Both have 0 upvotes.
Pricing and pricing details come from the maker's submission. They are not independently verified.
Superpowers
Superpowers
Superpowers is a complete software development methodology for your coding agents, built on top of a set of composable skills and some initial instructions that make sure your agent uses them.
It starts from the moment you fire up your coding agent. As soon as it sees that you're building something, it doesn't just jump into trying to write code. Instead, it steps back and asks you what you're really trying to do.
Once it's teased a spec out of the conversation, it shows it to you in chunks short enough to actually read and digest.
After you've signed off on the design, your agent puts together an implementation plan that's clear enough for an enthusiastic junior engineer with poor taste, no judgement, no project context, and an aversion to testing to follow. It emphasizes true red/green TDD, YAGNI (You Aren't Gonna Need It), and DRY.
Next up, once you say "go", it launches a subagent-driven-development process, having agents work through each engineering task, inspecting and reviewing their work, and continuing forward. It's not uncommon for your agent to work autonomously for a couple hours at a time without deviating from the plan you put together.
There's a bunch more to it, but that's the core of the system. And because the skills trigger automatically, you don't need to do anything special. Your coding agent just has Superpowers.
Commercial Services
If you're using Superpowers in enterprise and could benefit from commercial support, additional tooling, or managed spending, please don't hesitate to drop us a line at sales@primeradiant.com.
Installation
Installation differs by harness. If you use more than one, install Superpowers separately for each one.
Antigravity lists each installed skill's description, and the description of
the using-superpowers skill prompts the model to load that skill at the start
of a conversation. Reinstall with the same command to update.
Install Superpowers as a Pi package from this repository:
pi install git:github.com/obra/superpowers
For local development, run Pi with this checkout loaded as a temporary package:
pi -e /path/to/superpowers
The Pi package loads the Superpowers skills and a small extension that injects the using-superpowers bootstrap at session startup and again after compaction. Pi has native skills, so no compatibility Skill tool is required. Subagent and task-list tools remain optional Pi companion packages.
Qwen Code
Qwen Code installs plugins from Claude Code marketplaces directly.
Install the plugin from this repository, and pick superpowers when prompted:
qwen extensions install obra/superpowers
Update later:
qwen extensions update superpowers
Hermes Agent
Install Superpowers as a Hermes plugin from this repository:
hermes plugins install obra/superpowers --enable
Restart any active Hermes sessions after installing. Note: Hermes has no
post-compaction hook, so a very long session that compacts over its first
turn loses the bootstrap — start a fresh session if skills stop triggering.
Muse
Superpowers is available as a native Muse plugin — same repo, same skills, all harnesses. The using-superpowers bootstrap is injected via the native SessionStart hook alongside Claude Code, Codex, Cursor, Gemini, Pi, and the rest — no per-session opt-in.
Restart any active Muse sessions after installing so the SessionStart hook takes effect — skills are active immediately, hooks require approval on first install. To verify, start a fresh session and send Let's make a react todo list — a working install auto-triggers brainstorming before any code is written. Version is tracked in .version-bump.json so scripts/bump-version.sh keeps it in sync.
The Basic Workflow
brainstorming - Activates before building anything. Draws out what you actually want, and why, through questions that get you describing it, then plays its understanding back for correction. Small changes get agreed in chat; projects get a written design document a builder could plan from.
using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.
writing-plans - Activates with approved design. Breaks work into bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps.
subagent-driven-development or executing-plans - Activates with plan. Either dispatches a fresh subagent per task with a review after each (most thorough), or implements every task inline in the current session with one fresh review of the whole branch at the end (cheapest).
test-driven-development - Activates during implementation. Enforces RED-GREEN-REFACTOR: write failing test, watch it fail, write minimal code, watch it pass, commit. Deletes code written before tests.
requesting-code-review - Activates between tasks. Reviews against plan, reports issues by severity. Critical issues block progress.
finishing-a-development-branch - Activates when tasks complete. Verifies tests, presents options (merge/PR/keep/discard), cleans up worktree.
The agent checks for relevant skills before any task. Mandatory workflows, not suggestions.
When Something Goes Wrong
Sometimes a session misbehaves: a skill fires when it shouldn't, stays silent when it should, or the agent ignores its plan, repeats work, or burns more tokens than you'd expect. Ask your coding agent to "figure out what went wrong with superpowers in this session" and it will invoke the diagnosing-superpowers skill. To examine an earlier session, name it: "figure out what went wrong with superpowers in session <id>".
The skill reads the session transcript, reports what happened with line-level evidence, and, if you want, packages a scrubbed bundle for a bug report.
The general contribution process for Superpowers is below. Keep in mind that we don't generally accept contributions of new skills and that any updates to skills must work across all of the coding agents we support. We also don't accept agent-written PRs that fix issues filed by someone else unless a maintainer asked for one, even when you hit the same problem; add your report to the existing issue instead.
Fork the repository
Switch to the 'dev' branch
Create a branch for your work
Follow the writing-skills skill for creating and testing new and modified skills
Submit a PR, filling in every section of the pull request template, including the summary a human writes in their own words.
Skill-behavior tests use the drill eval harness from superpowers-evals, cloned into evals/ — see evals/README.md for setup. Plugin-infrastructure tests live at tests/ and run via the relevant run-*.sh or npm test.
See skills/writing-skills/SKILL.md for the complete guide.
Updating
Superpowers updates are somewhat coding-agent dependent, but are often automatic.
License
MIT License - see LICENSE file for details
Visual companion telemetry
Because skills and plugins don't provide any feedback to creators, we have no idea how many of you are using Superpowers. By default, the Prime Radiant logo on brainstorming's optional visual companion feature is loaded from our website. It includes the version of Superpowers in use. It does not include any details about your project, prompt, or coding agent. We don't see your clicks or anything about what you're building. This helps us have a rough idea of how many folks are using Superpowers and which version of Superpowers they're using. It's 100% optional. To disable this, set the environment variable SUPERPOWERS_DISABLE_TELEMETRY to any true value. Superpowers also honors Claude Code's DISABLE_TELEMETRY and CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC opt-outs.
Vercel Agent Skills
Agent Skills
A collection of skills for AI coding agents. Skills are packaged instructions and scripts that extend agent capabilities.
Audits a Vercel project for cost, performance, reliability, caching, function usage, and billing opportunities. It collects Vercel metrics first, then investigates only the routes and files those metrics point to.
Use when:
Optimizing a deployed Vercel project
Reducing Vercel costs or function usage
Investigating slow or expensive routes
Finding caching, ISR, middleware, image, or build-minute issues
Questions
Do Superpowers and Vercel Agent Skills list the same price?
Both listings report Free. Free to use. Pricing is reported by the maker and is not independently verified.
Which has more upvotes, Superpowers or Vercel Agent Skills?
Both have 0 upvotes.
What does each maker say Superpowers and Vercel Agent Skills are for?
Superpowers: Skills library and development methodology for coding agents covering planning, TDD and debugging. Vercel Agent Skills: Vercel collection of agent skills for React, Next.js and web development best practices.
Review docs and prose for compliance with the Vercel writing handbook. Audits your pages for 80+ rules covering voice, structure, content types, code samples, typography, and AI workflow.
React Native best practices optimized for AI agents. Contains 16 rules across 7 sections covering performance, architecture, and platform-specific patterns.
Use when:
Building React Native or Expo apps
Optimizing mobile performance
Implementing animations or gestures
Working with native modules or platform APIs
Categories covered:
Performance (Critical) - FlashList, memoization, heavy computation
Implement smooth, native-feeling animations using React's View Transition API. Covers the <ViewTransition> component, addTransitionType, transition types, and Next.js integration including the transitionTypes prop on next/link.
Use when:
Adding page transitions or route animations
Animating enter/exit of components
Creating shared element transitions (list-to-detail morphing)
React composition patterns that scale. Helps avoid boolean prop proliferation through compound components, state lifting, and internal composition.
Use when:
Refactoring components with many boolean props
Building reusable component libraries
Designing flexible APIs
Reviewing component architecture
Patterns covered:
Extracting compound components
Lifting state to reduce props
Composing internals for flexibility
Avoiding prop drilling
deploy-to-vercel
Deploy applications and websites to Vercel. Prefers git-push deploys on a linked project, falls back to the Vercel CLI, and uses vercel deploy --temporary when no login is available. Temporary deployments return a claim URL so users can keep them.
Use when:
"Deploy my app"
"Push this live"
"Deploy and give me the link"
"Create a preview deployment"
Installation
npx skills add vercel-labs/agent-skills
Usage
Skills are automatically available once installed. The agent will use them when relevant tasks are detected.
Examples:
Deploy my app
Review this React component for performance issues
Help me optimize this Next.js page
Discovery index
Every change to a skill on main publishes an immutable GitHub release with
an Agent Skills discovery index and one artifact per skill. Build the same
artifacts locally with:
npm ci --ignore-scripts
node scripts/build-discovery-index.mjs https://example.com/skills
Skill Structure
Each skill contains:
SKILL.md - Instructions for the agent
scripts/ - Helper scripts for automation (optional)