OrchestKit vs Superpowers
Superpowers is on the official Anthropic marketplace. That listing is not a vacancy. OrchestKit is a different job: production patterns plus lifecycle hooks, so the agent already knows how you ship a FastAPI endpoint or a TanStack query, and a commit that skips tests does not land.
At a glance
| Superpowers | OrchestKit | |
|---|---|---|
| Job | How the agent works a task (TDD, planning, review loops) | How you ship production software (FastAPI, React, RAG, CI, security) |
| Home | Official Anthropic marketplace | yonatangross/orchestkit |
| Size | Small, official, process | 106 skills, 36 agents, 175 hooks |
| Enforcement | You follow the process | Hooks fire without being asked |
| Listing fight | Already won. It is official. | Don't re-fight that marketplace |
Use both, or pick one
If you want the agent to follow a disciplined process, start with Superpowers. If you want it to already know your stack, and to block a bad commit, that is OrchestKit. Many people run both. Roundups that list Superpowers and gstack and skip OrchestKit are process-plugin lists; they are not a verdict on production-pattern kits.
Install
- Claude Code:
claude install orchestkit/ork - Cursor: marketplace
yonatangross/orchestkit, enable ork, new chat - Starter 12 via skills.sh (not the whole catalog):
npx skills add yonatangross/orchestkit -s doctor -s setup -s explore -s implement -s verify -s review-pr -s commit -s expect -s assess -s brainstorm -s create-pr -s remember
Also: OrchestKit vs an ad-hoc Claude Code setup.
Want this outcome for your product?
A free 15-minute intro call. No pitch deck, no pressure. Just whether I can help.