One plugin per stack: installing reviewed agent skills and MCP servers in Claude Code, Codex and Cursor
Agent skills are the most useful thing to happen to coding assistants this year, and also the messiest. The good ones are spread across dozens of repositories: Microsoft publishes .NET skills, Vercel publishes React and
Agent skills are the most useful thing to happen to coding assistants this year, and also the messiest. The good ones are spread across dozens of repositories: Microsoft publishes .NET skills, Vercel publishes React and Next.js rules, Anthropic publishes frontend and testing skills, database vendors publish their own, and each MCP server lives somewhere else again. Setting up a project means hunting through all of them, copying folders and hoping the versions still match.
I built PlaybookRun to fix that for my own projects. A playbook is a bundle of the skills a stack needs plus the MCP servers those skills use, published as one plugin. There are 98 of them today, from dotnet-api-aspire and nextjs-on-vercel to postgres-best-practices, spring-boot-java and flutter-dart.
Install one in Claude Code
All playbooks live in one public marketplace repository, so you add it once:
/plugin marketplace add Fcakiroglu16/marketplace
Then install the playbook for your stack, for example Redis:
/plugin install redis@playbookrun
That gives Claude Code Redis's official skills for data modelling, connections and pipelining, search and vectors, clustering, security and observability, together with the Redis MCP server, in one step.
Codex and Cursor use the same marketplace
The same repository works in Codex:
codex plugin marketplace add Fcakiroglu16/marketplace
codex plugin add redis@playbookrun
In Cursor, a team admin imports the repository under Dashboard → Plugins & MCPs → Team Marketplaces → Import from Repo. Every playbook page on playbookrun.com shows the install command for each tool.
Let the agent find the playbook
One playbook is a skill for finding the others. Install find-playbooks and ask your agent for what you are about to do ("I'm starting a FastAPI service with Postgres"); it searches the catalog and answers with the playbook that fits and the install command for the tool you are in.
/plugin install find-playbooks@playbookrun
Why reviewed matters
Skills run inside your own sessions, with your files and your credentials, so I don't publish a playbook without a review. Skills and MCP servers carry their source: Official when the owner of the technology publishes them, and Community otherwise. MCP server definitions are checked for things like literal secrets and unpinned packages before they go live, and anyone can report a playbook from its page.
Community playbooks are welcome too: sign in on the site, assemble skills and MCP servers into a playbook and submit it for review. Once it is approved it is published to the same marketplace, so it installs in every tool the same way.
Try it
- Browse the catalog: playbookrun.com
- Marketplace repository: github.com/Fcakiroglu16/marketplace
- Start with the playbook for the stack you use most and tell me what is missing.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.