Plugins

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. You install it by typing a /plugin command in the chat (it works the same in Claude Desktop or the terminal). It's a Power-Track, team-setup move — the fastest way to roll a proven configuration out to 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 you install one by typing /plugin install in the chat (the same slash command works in Claude Desktop or the terminal); /reload-plugins activates a freshly installed one in the current session. This is more of a Power-Track, team-setup tool than an everyday one — most people get a long way before they reach for it — but when a team wants everyone’s Claude configured identically, it’s the cleanest way.

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.