Build your own plugin & marketplace

A plugin bundles the pieces from today — commands, skills, sub-agents, hooks — into one thing you can install in a single step, and share with your whole team or even the world.

01Why plugins

You’ve been creating loose files in .claude/. A plugin gathers them into a named, versioned package. Publish a few for your team and everyone gets the same commands, skills and safety hooks in one click — consistency across a whole company.

02Anatomy of a plugin

We’ll build independent-reviewer — a plugin that runs an independent review of recent changes (via Codex, or Claude if you prefer). It’s just a folder with a specific structure:

.claude-plugin/
  plugin.json        # the manifest: name, description, version
commands/            # optional: slash commands
skills/              # optional: skills
agents/              # optional: sub-agents
hooks/
  hooks.json         # the hook config (moved here from settings.json)

{
  "name": "independent-reviewer",
  "description": "Carry out an independent review of all changes since last commit",
  "version": "0.1.0"
}

03Make a marketplace

To install a plugin properly (and let others add it), you publish it through a marketplace — another small JSON file at the top of the repo:

{
  "name": "edtools",
  "owner": { "name": "Ed", "email": "ed@example.com" },
  "plugins": [
    { "name": "independent-reviewer", "source": "./independent-reviewer" }
  ]
}

04Install & test it

With the JSON in place, use the /plugin menu. Add your local marketplace (./ points at the current repo), browse it, install the plugin at project scope, and restart.

05Wrapping up the day — and looking ahead

That was a lot: slash commands, agents and sub-agents, a Codex cameo, hooks, and now plugins and marketplaces. If your head is spinning, that’s fine — most of these you’ll rarely need. The goal was a tour of what’s possible, so you know it exists and where to look.