Share plugins through your own marketplace

The steps

One step at a time. When a step’s check matches, tick it and the next one opens.

1. 01

   Step 1 of 5: Set up the marketplace folder

   A marketplace is a folder with .claude-plugin/marketplace.json and the plugins it lists.

   team-plugins/

   • folder .claude-plugin
     • marketplace.jsonNewthe catalog
   • folder plugins
     • folder acme-kitNewa copy of the Day 34 plugin

   The kit has these files. In your own project, ask Claude:Copy

   Create team-plugins/.claude-plugin/ and team-plugins/plugins/, then copy plugins/acme-kit into team-plugins/plugins/. Don’t change the original.

   Check it worked

   team-plugins/plugins/acme-kit/.claude-plugin/plugin.json exists.

   It worked — next step Not yet
2. 02

   Step 2 of 5: Write marketplace.json

   Name the marketplace and its owner, and add one entry per plugin.

   team-plugins/.claude-plugin/marketplace.json · JSONCopy

   {
     "name": "acme-team",
     "description": "Plugins the Acme Quotes team has reviewed and shares",
     "owner": {
       "name": "Acme Quotes team"
     },
     "plugins": [
       {
         "name": "acme-kit",
         "source": "./plugins/acme-kit",
         "description": "The client-update skill and a hook that blocks edits to .env files and test/"
       }
     ]
   }
   

   .claude-plugin/marketplace.json

   name: acme-team

   What people type after @ to install

   owner.name: "Acme Quotes team"

   Required: who maintains it

   plugins[0].name: acme-kit

   Must match the name in the plugin’s plugin.json

   plugins[0].source: ./plugins/acme-kit

   A path from the marketplace root, with no ..

   Check it worked

   claude plugin validate ./team-plugins ends with ✔ Validation passed.

   It worked — next step Not yet Back
3. 03

   Step 3 of 5: Add it and install the plugin

   Register the folder as a marketplace, then install the plugin by name.

   In Claude Code

   You type: › /plugin marketplace add ./team-plugins

   – What happens: Registers it under the name in marketplace.json: acme-team.

   You type: › /plugin install acme-kit@acme-team

   – What happens: Opens the plugin in /plugin. Choose Install for you, in this repo only (local scope).

   Check it worked

   Type /acme-kit and /acme-kit:client-update is offered.

   It worked — next step Not yet Back
4. 04

   Step 4 of 5: Push it and send the add command

   Teammates add the marketplace from your git host, then install by name.

   In order:

   1. You

      Push team-plugins/

      As its own repository

   2. You

      Send the add command

      /plugin marketplace add your-org/team-plugins

   3. Teammates install

      /plugin install acme-kit@acme-team

   4. You

      Release a change

      Raise version in plugin.json, or installs keep the old copy

   Check it worked

   The repository’s root shows .claude-plugin/ and plugins/.

   It worked — next step Not yet Back
5. 05

   Step 5 of 5: Offer it in project settings

   Commit settings so everyone who trusts the repository gets the marketplace and the plugin.

   TerminalCopy

   Run: $ claude plugin marketplace remove acme-team

   Run: $ claude plugin marketplace add your-org/team-plugins --scope project

   Run: $ claude plugin install acme-kit@acme-team --scope project

   – What happens: The first removes your local test copy. Use your own repository in the second.

   Check it worked

   .claude/settings.json now mentions acme-team and acme-kit@acme-team.

   If it didn’t work

   A teammate sees the plugin enabled but not installed

   They run claude plugin install acme-kit@acme-team --scope project once in the repository.

   It worked — finish Not yet Back