lockstep
5 min readNaman Jain

Claude Code plugins and marketplaces: a guide for teams

What a Claude Code plugin is, when you need one, how to build a team marketplace, and how admins require plugins on every machine with managed settings.

Your team has a good release skill, a code-review subagent, a formatting hook, and the Sentry MCP server set up just right. All of it lives in one repository. The next repository starts from nothing, and someone copies the files by hand, and the copies drift.

Plugins solve that. A plugin packages a setup so it installs with one command and updates from one place. This guide covers what a plugin is, when you need one, how to run a team marketplace, and how admins require plugins across an organization, from Anthropic's plugins, marketplace, and organization documentation, checked on 16 November 2026.

What a plugin is

A Claude Code plugin is a directory of components that Claude Code installs and loads as one unit. It usually has a manifest at .claude-plugin/plugin.json with a name, and optionally a version and description. Components can include:

  • Skills: SKILL.md instructions Claude loads when relevant, or you run as commands
  • Agents: subagent definitions Claude can delegate to
  • Hooks: commands Claude Code runs at lifecycle events
  • MCP servers: tool servers Claude Code connects to while the plugin is enabled

Plugin skills are namespaced, like /my-plugin:review, so several plugins can coexist without name clashes.

Do you need a plugin?

Often not. Skills, subagents, hooks, and MCP servers all work on their own: a skill in .claude/skills/ works for the repository, and one in ~/.claude/skills/ works across your projects.

Anthropic's guidance is to use a plugin when you want several of those pieces packaged as one unit: to give your setup to teammates, install it in many projects, or publish versioned releases. A good trigger, from the features overview: a second repository needs the same setup.

One thing to know before installing many: an enabled plugin is part of every session, not only the sessions where you use it.

Installing plugins

Run /plugin in Claude Code and use the Discover tab, which lists plugins from the marketplaces you've added. From the command line:

claude plugin marketplace add your-org/claude-plugins
claude plugin install release-tools@your-org-plugins
claude plugin list

The install ID is the plugin's name, @, and the marketplace's name. Anthropic's official marketplace is claude-plugins-official, which is where plugins such as Figma's and Exa's install from.

Building a team marketplace

A marketplace is a directory, usually a git repository, with a .claude-plugin/marketplace.json that lists plugins and where to fetch each one. It can be private.

claude-plugins/
  .claude-plugin/
    marketplace.json
  plugins/
    release-tools/
      .claude-plugin/plugin.json
      skills/
      agents/

marketplace.json needs a name, an owner, and a plugins array:

{
  "name": "your-org-plugins",
  "owner": { "name": "Platform team" },
  "plugins": [
    {
      "name": "release-tools",
      "source": "./plugins/release-tools",
      "description": "Release checklist, changelog skill, and version bump hook"
    }
  ]
}

Before you share it:

  1. Run claude plugin validate ./claude-plugins to check the JSON and every entry.
  2. Install from it on your own machine. Some problems, such as a missing source directory, only appear at install.
  3. Keep each entry's name the same as the name in that plugin's plugin.json, or installs by name fail.
  4. Write relative source paths from the marketplace root, never with ...

A plugin entry can also point to its own GitHub repository, a subdirectory of a monorepo, a URL, an archive, or an npm package. Then push the repository and give teammates the marketplace add command. Plugins also install in CI; see Claude Code GitHub Actions.

Requiring plugins across an organization

Admins can make sure every machine has the right plugins, and users can't override it. In managed settings, set two keys together:

  • extraKnownMarketplaces registers your marketplace on each machine.
  • enabledPlugins names the plugins to install and enable from it.

Managed settings reach machines three ways:

MechanismHowGood for
Server-managed settingsJSON in the claude.ai admin console, under Claude Code managed settings; needs an Owner roleTeams and Enterprise organizations without full MDM coverage
MDM policyA plist on macOS, a registry value on WindowsFleets already under MDM
Managed settings filemanaged-settings.json at the system path, plus drop-ins in managed-settings.d/Servers, containers, and CI

The organization page also covers restricting which marketplaces users can add, update policy, and auditing what's installed. For settings precedence, see Claude Code settings.json.

What a marketplace doesn't tell you

A marketplace distributes a plugin. It doesn't tell you which teams got which version, which repositories should get a rule and which shouldn't, or whether a developer edited a skill locally. Those are rollout questions, and they matter more as the number of plugins and teams grows.

Where Lockstep fits

Lockstep's Standards & Skills covers the rollout side. An engineering lead publishes versioned standards and skills once, written in Lockstep or imported from a public GitHub repository at an exact commit. Rollouts target a team, repository, path, or task type, with a preview, a pilot, expansion, and rollback. Enrolled checkouts receive skills in .claude/skills/lockstep-org-*/, kept out of git, hash-verified, and never overwriting a developer's local edits. An adoption view shows which version reached which checkout and which sessions started with it. Whether Claude actually invoked a skill is reported as unobservable, not guessed.

It works alongside a plugin marketplace rather than replacing it, and supports Claude Code today. See how it works.

Sources checked 16 November 2026

For writing the skills that go into a plugin, see Claude Code skills: 6 examples. For choosing between extensions, see CLAUDE.md vs skills vs hooks vs subagents. For sharing what agents learn, see Claude Code team memory. For the full rollout plan, see how to roll out Claude Code to an engineering team.

Frequently asked questions

What is a Claude Code plugin?
A directory of skills, subagents, hooks, MCP servers, or other components that Claude Code installs and loads as one unit. Its manifest, .claude-plugin/plugin.json, gives it a name and can add a version and description.
Do I need a plugin, or just a skill?
Skills, subagents, hooks, and MCP servers all work on their own. Use a plugin when you want several of them packaged as one unit: to share a setup with teammates, install it in many projects, or publish versioned releases.
How do I create a team plugin marketplace?
Make a git repository with a .claude-plugin/marketplace.json listing your plugins, each with a name and a source. Validate it with claude plugin validate, push it, and have teammates run claude plugin marketplace add <owner>/<repo>, then install plugins by name@marketplace.
How do I require a plugin for everyone in my organization?
In managed settings, set extraKnownMarketplaces to register your marketplace on every machine and enabledPlugins to install and enable the plugins. Deliver them as server-managed settings from the claude.ai admin console, through MDM, or with a managed-settings.json file. Users can't override them.
Does an installed plugin cost context in every session?
An enabled plugin is part of every session, not only the sessions where you use it. Skills still load their full body only when used, but install the plugins you need rather than every one you find.

Keep reading