Claude Code plugins. What a plugin is and how to install one

A plugin is a package that adds skills, subagents, hooks or MCP servers to Claude Code with one command. We explain how a plugin differs from a skill, what a marketplace is and how to install a plugin in the terminal, the desktop app and VS Code.

Part of the guideClaude Code, the complete guide. From installation to your own skills and plugins

In this article
  1. What a Claude Code plugin is
  2. Plugin vs skill, what is the difference
  3. Marketplaces, or where plugins come from
  4. How to install a Claude Code plugin
  5. A plugin runs with your permissions

In short

A Claude Code plugin is a folder that installs as one unit and can add skills, subagents, hooks, MCP servers and a few other things at once. Plugins come from a marketplace, which is a catalog, and Claude Code adds Anthropic's official catalog by itself the first time you start it in a terminal. Installing takes one command and a choice of one of three scopes.

A teammate posts one line in the chat. Type /plugin install commit-commands@claude-plugins-official and you will have commit commands. The part before the @ is the plugin name, the part after it is the catalog it comes from. This article explains what a Claude Code plugin is, how it differs from a skill and how to install one.

We checked everything in the Claude Code docs, on the pages about plugins, about installing and about Anthropic's marketplaces, as of 10 November 2026. The whole series is collected in our Claude Code guide.

What a Claude Code plugin is

A plugin is a folder of components that Claude Code loads together. It usually has a .claude-plugin/plugin.json file, where the only required field is the name. A description and a version can sit next to it. Claude Code loads a plugin even without this file and then names it after the folder.

The main components are skills, subagents, hooks and MCP servers. The docs also list LSP language servers, which show Claude type errors after an edit, executables, default settings, themes, output styles and monitors. The older commands folder still works, but Anthropic recommends skills for new plugins.

A plugin skill gets the plugin name in front of it. The commit skill from the commit-commands plugin runs as /commit-commands:commit. That way two plugins can each have a skill with the same name and nothing clashes.

Plugin vs skill, what is the difference

A skill is one folder with instructions. Put it in ~/.claude/skills/ and it works in all your projects, no plugin needed. The same goes for a single hook, subagent or MCP server. What a skill is on its own is explained in what is a Claude skill.

A plugin makes sense when several of those pieces should work together or reach other people. You install a ready set with one command and get updates from its author. Or you package your own set so the whole team has the same skills and hooks in every project.

Before you install a plugin, keep in mind that an enabled plugin is part of every session. The names and descriptions of its skills and agents sit in the context with every message and use your plan's limit even when you use nothing from the plugin. Its MCP servers run in the background, and its hooks fire on their events. A few plugins you actually use beat a dozen installed just in case.

Marketplaces, or where plugins come from

A marketplace is a catalog of plugins. Technically it is a repository or folder with a .claude-plugin/marketplace.json file that lists plugins and says where to fetch each one. It is a list, not a store.

CatalogName after @How to add it
Anthropic officialclaude-plugins-officialClaude Code adds it itself
Anthropic communityclaude-community/plugin marketplace add anthropics/claude-plugins-community
Third partyThe name field in its file/plugin marketplace add owner/repo

Claude Code adds the official catalog the first time you start it in a terminal. It holds Anthropic's own plugins, such as commit-commands, code-review and feature-dev, but most entries come from partners and other authors. Anthropic does not review third-party catalogs. The old claude-code-plugins catalog in the anthropics/claude-code repository is deprecated, so skip tutorials that tell you to add it.

The claude.com/marketplace website is something else. You can browse plugins there in a browser, but you do not add it with /plugin marketplace add.

How to install a Claude Code plugin

In the terminal, run claude in your project and type /plugin. The Discover tab lists plugins from your catalogs, and you can search it. If you know the name, type /plugin install name@catalog. This command does not install right away. It opens the plugin's details, which show the skills, agents, hooks and servers it adds, and for the official catalog also how many tokens it costs with each message.

Then you pick one of three scopes. Install for you means all your projects on this computer. Install for all collaborators on this repository writes the plugin into the project's .claude/settings.json, so after a commit it is enabled for everyone on the team, though each person still installs it on their own machine. Install for you, in this repo only works just for you and just in this repository.

At the end Claude Code prints a summary. Plugin is now active means it works right away. If the summary mentions /reload-plugins, Claude Code runs that reload for you. You will find the plugin's skills by typing a slash.

What you wantIn a sessionIn a normal terminal
Browse plugins/plugin
Install/plugin install name@catalogclaude plugin install name@catalog
Add a catalog/plugin marketplace add owner/repoclaude plugin marketplace add owner/repo
List installedInstalled tab in /pluginclaude plugin list
Disable/plugin disable name@catalogclaude plugin disable name@catalog
Uninstall/plugin uninstall name@catalogclaude plugin uninstall name@catalog
UpdateInstalled tab, Update nowclaude plugin update name@catalog

In the Claude desktop app, in the Code tab, click the plus button next to the prompt box and choose Add plugins. In the VS Code extension, type /plugins and the Manage plugins window opens. The terminal, the desktop app and the VS Code extension read the same settings files, so a plugin you install for yourself in one of them works in the other two on the same computer. Cloud sessions, including the browser at claude.ai/code, do not load plugins from your computer.

Plugins from the official catalog update on their own. For the community catalog and third-party ones, auto-update is off by default.

A plugin runs with your permissions

The docs say it plainly. An installed plugin can run any code on your computer with your user privileges. Before you install a plugin from outside Anthropic's catalogs, read its files, especially the hooks and the MCP server config. We cover hooks in Claude Code hooks and servers in MCP in Claude Code.

Your own plugin is not hard either. You need a folder with .claude-plugin/plugin.json and a skills subfolder, a check with claude plugin validate ./my-plugin, and a start with claude --plugin-dir ./my-plugin, which loads it for one session without installing it. How to write the skill inside is shown in how to write a Claude skill, and examples of ready plugins are in official Claude skills and plugins.

To begin, one plugin from the official catalog that fixes a problem you really have is enough. If you want to see which tasks in your company AI could take over, our free AI audit looks at where AI can take work off your team.

What would you like to change in your business?

Leave your number. We will talk about your process and see whether we can help. The first call is free.

When is the best time to call?
Controller: Oleksandr Bondarenko (BondSoft)Privacy PolicyTerms of Service
Legal details

The data controller is Oleksandr Bondarenko, trading as Oleksandr Bondarenko Software Solutions (BondSoft), ul. Jana Heweliusza 11, 80-890 Gdańsk, Poland, NIP 5833576264, e-mail: office@bondsoft.pl.

We process your data solely to contact you about your enquiry and to present an offer — on the basis of your consent (Art. 6(1)(a) GDPR and Art. 398 of the Polish Electronic Communications Law) and our legitimate interest in handling the enquiry (Art. 6(1)(f) GDPR).

Providing the data is voluntary but necessary for us to reply. You may withdraw your consent at any time by writing to office@bondsoft.pl — this does not affect the lawfulness of processing before the withdrawal.

You have the right to access your data, rectify it, erase it, restrict its processing, transfer it, and lodge a complaint with the President of the Polish Personal Data Protection Office.

Full information: Privacy Policy.

Send us an email

The service this text is about

Automation and AI / OCR

Automation of document re-typing, OCR and checking rules, and your data stays with you.