I sell Claude Code orchestration templates — pre-assembled agent teams with skills and hooks. So when people ask "isn't this just what claude.com/plugins already does for free?" it's a fair question. I went and looked. Short answer: it's a different layer of the stack — not really the same job.
What's on claude.com/plugins
Anthropic's own tagline for the page: "Browse plugins that bundle tools, skills, and integrations." You browse a grid and filter by "works with" (Claude Code, Cowork). Install counts are public, and some are large:
| Plugin | Installs | What it does |
|---|---|---|
| Superpowers | 1,009,371 | Teaches Claude brainstorming, subagent development, code review, debugging, TDD, and skill authoring |
| Playwright | 319,887 | Browser automation and testing |
| GitHub | 319,381 | Official repo management |
| Ralph Loop | 196,527 | Interactive loops for iterative development |
| Vercel | 227,688 | Deployment and infrastructure |
| Figma | 167,556 | Pull design files into Claude Code |
| Slack | 92,287 | Works with both Cowork and Claude Code |
There's also a long tail: language servers (TypeScript, Python, Go, Rust, Java, PHP), cloud platforms (AWS, Azure, Firebase), databases (Supabase, MongoDB, Prisma), and dev tools (Linear, GitLab, Postman, Sentry).
What a plugin is
Per Anthropic's own FAQ, a plugin "bundles multiple MCPs, skills, and tools into a single download." So it's not always one skill — some plugins do bundle several pieces together. But look at what's actually popular: almost everything in the top installs is a tool connector (talk to GitHub, talk to Figma, talk to Slack) or a generic capability teacher (Superpowers teaches Claude the pattern of building subagents — it doesn't hand you a built team).
That distinction matters. A plugin gives Claude a new thing it can do. It doesn't decide who does what on your project.
So are plugins ever the right call?
Yes. If you need Claude Code to talk to a specific external tool, install the plugin for that tool. There's no reason to hand-roll an MCP server for GitHub or Figma when Anthropic (or the vendor) already maintains one with 300k+ installs behind it. Same for Superpowers if you want to learn how subagents and skills work, or build your own from scratch — it's free and a solid starting point.
What happens when you install a few of them together
Each plugin adds a capability, but the capabilities don't coordinate with each other. Install five of them and you're the one deciding: who plans the feature? Who writes the code? Who reviews it for security? Who checks the UI actually works? What order do they run in, and what happens when one of them finds a problem the others need to know about?
That's an organizational design question, not a tool-integration one — closer to assembling a team than installing a tool.
So what am I actually selling, then?
Four templates, each a pre-assembled team — agents with defined roles, skills that route work between them, hooks that log what happened, and a workflow doc explaining how they fit together:
| Template | Price | What's in it |
|---|---|---|
| Startup Dev Team | Free | 4 agents, 5 skills — PM, developer, UX, tester |
| Test & Bug Fix Kit | $9 | 6 agents, 6 skills — focused QA loop |
| UX Review Team | $19 | 10 agents, 10 skills — full UX audit pipeline |
| Enterprise Dev Team | $19 | 8 agents, 13 skills — draft + advanced dev split, full review chain |
Every agent in a template is written to hand off to the others correctly — the PM's plan matches the fields the developer expects, the tester's report format is what the PM reads back. That's the part that takes iteration to get right, and it's what you're paying for: not the individual agent files (you could write those yourself), but the fact that they're tested working together.
Which one you need
If you want to learn how subagents work, or you only need Claude Code to talk to one more external tool, claude.com/plugins is free and well-maintained — use it. If you want a working team on day one, with roles, handoffs, and a workflow already wired together, that's what a template gets you. Plugins extend what Claude can do. Templates decide who does what.
Next steps
- Browse the plugins yourself at claude.com/plugins — it's worth knowing what's there
- Start with the Startup Dev Team — it's free, and you'll feel the difference between "a capability" and "a team" in the first task you give it
- Read what agents actually are if you want to understand the building blocks before deciding