feature
Plugins
A bundle of skills, commands, hooks, and connectors you install in one step — a pre-packed setup someone else already figured out.
A plugin packages several add-ons together so you don't assemble them by hand. Install one and you might get a set of skills, a few slash commands, some hooks, and a tool connection all at once — configured and ready. It's the fastest way to adopt a proven setup for a whole team.
Everything else in this section — skills, slash commands, hooks, connectors — is a single add-on you set up by hand. A plugin is the box that ships several of them together, already configured. Install one and you might get a handful of skills, a few commands, some hooks, and a tool connection all at once, ready to use.
That makes it the fastest path from “I’ve heard this is good” to actually having it:
a proven setup someone else already assembled, in one command. Plugins come from a
marketplace — claude-plugins-official is the built-in one — and /plugin install
pulls a plugin from it; /reload-plugins activates a freshly installed one in the
current session.
Two habits make this safe and useful. Before you enable a plugin for a team, check what’s inside it — which skills, hooks, and connectors come along, since hooks and connectors can act on your machine. And when you’ve arrived at a setup that works, package it as your own plugin: it’s the cleanest way to hand one polished, identical configuration to every project and every teammate at once.
why it helps Get a battle-tested toolkit in one command instead of wiring it piece by piece.
examples
/plugin install code-review@claude-plugins-official/plugin install security-guidance@claude-plugins-official/reload-pluginstips & best practices
- Plugins are the fastest way to adopt a proven setup — a bundle beats wiring it piece by piece.
- Check what a plugin includes (skills, hooks, connectors) before enabling it for a team.
- Build your own plugin when you want to share one polished setup across many projects.