Claude Code Plugins: an App Store in Your Terminal

Claude Code plugins are prebuilt extension packs: skills, agents, hooks and ready-made integrations that someone else built, which you install with a single command instead of configuring anything yourself. The whole system runs through one command — type /plugin inside Claude Code and a small app store opens right in your terminal.

The mental model that makes everything click: a marketplace is a store you register, and plugins are the apps inside it. Registering a store does not put anything on your phone — you still pick which apps to download. Same two-step here, and once you see it, every command in this guide becomes obvious.

What are Claude Code plugins made of?

One plugin can carry several kinds of cargo: skills (reusable playbooks you call with a slash), agents (specialist helpers Claude delegates to), hooks (scripts that fire automatically on events) and MCP servers (connectors to outside services like GitHub or Notion). To prevent name collisions, plugin skills are namespaced: installing a plugin called commit-commands gives you commands like /commit-commands:commit rather than a bare /commit. Slightly longer to type, but two plugins can never fight over the same name.

How to install Claude Code plugins

The official Anthropic marketplace, claude-plugins-official, is already registered the first time you start Claude Code — no setup. So installation is genuinely a one-liner:

/plugin install github@claude-plugins-official

Best Claude Code plugins: which to install first?

Every «Claude Code plugins list» starts with developer tools, but for non-programmers I would reorder it. Start with external integrations — github, slack, notion, linear, figma, asana — because each one bundles a pre-configured MCP server, meaning Claude can read and act on those services with zero manual setup. Then commit-commands, which packages polite git workflows: saving versions of your work without learning git incantations. Then security-guidance, a plugin that reviews each change Claude makes for common vulnerabilities and has it fix findings in the same session. The official marketplace also carries two output-style plugins, explanatory-output-style and learning-output-style, which turn Claude into a patient teacher. Code intelligence (LSP) plugins like typescript-lsp or pyright-lsp matter once you build real apps: they let Claude see type errors immediately after every edit.

Where do plugins come from — and can you trust them?

Three main sources. The official claude-plugins-official marketplace is curated by Anthropic. The community marketplace hosts third-party plugins that passed Anthropic's automated validation and safety screening — you add it manually. And any GitHub repository with a marketplace file can be a private store, which is how teams ship internal toolkits.

/plugin marketplace add anthropics/claude-plugins-community
/plugin install <plugin-name>@claude-community
/plugin list
/plugin disable plugin-name@marketplace-name
/plugin uninstall plugin-name@marketplace-name
/plugin marketplace update marketplace-name

Can you build your own plugin?

Yes, and it is less scary than it sounds: a plugin is a folder with a tiny manifest file at .claude-plugin/plugin.json (name, description, version) plus a skills/ directory holding the skills you already know how to write. Test it locally with claude --plugin-dir ./my-first-plugin before sharing anything, or scaffold one instantly with claude plugin init my-tool. The honest beginner advice from the docs: keep things as plain skills in .claude/ while experimenting, and convert to a plugin only when you want to share with other people or reuse across many projects.

Closing move: tell Claude — «Show my installed plugins, estimate what each costs me in context, and recommend which to disable». An app store is fun; a curated toolbelt is what actually makes you faster.