Claude Code Plugins: Marketplace Setup and Team Sharing

Still zipping up a teammate's Claude Code skills and commands, sending them over chat, and pasting config files in one by one? Setups copied this way drift apart, so when someone fixes a skill, the rest of the team never gets the fix.

A Claude Code plugin is a single folder that bundles skills, subagents, hooks, and MCP servers so you can install, enable, and disable them with one command. A catalog of plugins is called a marketplace: add a marketplace once, and you can install any plugin in it by name and receive its updates. Based on the official docs as of October 2026, this guide covers how plugins differ from standalone skills and hooks, how to add a marketplace and install or turn off a plugin, how to package your own skills as a plugin, how to share it with your team, and a security checklist. At the end, you'll see how to turn meeting notes transcribed with daglo into a task list with a plugin skill.

What is a Claude Code plugin? How it differs from skills, hooks, and MCP

Skills, hooks, and MCP servers each work on their own. A plugin is the package that bundles them for distribution. If you work alone in one project, standalone setup is enough. If you want the same setup across projects or teammates, bundle it as a plugin.

Plugin skills are prefixed with the plugin name, so two plugins can each ship a skill with the same name without colliding. For writing skills, see our Claude Code skills guide. For running commands automatically at set points, see the Claude Code hooks guide.

An enabled plugin adds its skill names and descriptions to Claude's context on every turn, so keep only the plugins you need turned on.

Add a marketplace, then install, enable, and disable plugins

Installing a plugin takes four steps: add a marketplace, install the plugin, choose a scope, and confirm it works. Anthropic's official marketplace, claude-plugins-official, is added automatically the first time you start Claude Code in a terminal, so you can install from it right away.

1. Browse: Type /plugin in Claude Code. The Discover tab lists plugins you can install. Type to search, then press Enter to open the details.
2. Add another marketplace: For a marketplace a coworker or your company publishes, run /plugin marketplace add your-org/your-repo once. A GitHub repo, any git URL, or a local folder such as ./my-marketplace all work.
3. Install: Run /plugin install commit-commands@claude-plugins-official in the form plugin-name@marketplace-name. The details pane opens. Check its Will install section for the skills, hooks, and MCP servers the plugin adds.
4. Pick a scope: Choose user to use it in every project on your machine, project to turn it on for everyone working in this repository, or local to use it only yourself in this repository.
5. Confirm: If the summary ends with "Plugin is now active.", it's ready. Type / and look for commands with the plugin prefix, such as /commit-commands:commit. If you're asked to reload, run /reload-plugins.

Manage installed plugins on the Installed tab in /plugin. Press Space to enable or disable one, or Enter for its menu with Update now and Uninstall. From your shell, claude plugin disable name@marketplace and claude plugin enable name@marketplace do the same.

Package your own skills as a plugin

A plugin is a folder with one manifest file, .claude-plugin/plugin.json, plus component folders. If you already have skills under .claude, copy them into a new folder and add a manifest, and you have a plugin.

1. Create the folders: mkdir -p meeting-tools/.claude-plugin meeting-tools/skills/action-items
2. Write the manifest: In meeting-tools/.claude-plugin/plugin.json, add {"name": "meeting-tools", "description": "Turn meeting notes into task lists", "version": "1.0.0"}. The name has no spaces and becomes the prefix on every skill.
3. Add the skill: Move your skill to skills/action-items/SKILL.md. The skills folder sits next to .claude-plugin, not inside it, or it won't load.
4. Validate: Run claude plugin validate ./meeting-tools in your shell and look for "Validation passed".
5. Test without installing: Start Claude Code with claude --plugin-dir ./meeting-tools to load the plugin for that session only. Run /meeting-tools:action-items, and after editing files, run /reload-plugins.

Share plugins with your team

The standard way to share is to create a marketplace repository that lists your plugins, and have teammates add it once. For one or two people, you can simply hand over the plugin folder or a zip.

1. Create the marketplace folder: Make team-plugins/.claude-plugin/marketplace.json and put plugin folders under team-plugins/plugins/.
2. List the plugins: Write name, owner, and plugins, for example {"name": "team-plugins", "owner": {"name": "Marketing Team"}, "plugins": [{"name": "meeting-tools", "source": "./plugins/meeting-tools", "description": "Turn meeting notes into task lists"}]}. Keep each entry's name the same as the name in its plugin.json.
3. Validate and push: Check with claude plugin validate ./team-plugins, then push to GitHub or another git host. Private repos work as long as teammates are signed in to git on their machines.
4. Teammates install: They run /plugin marketplace add your-org/team-plugins once, then /plugin install meeting-tools@team-plugins.
5. Turn it on for the repo: Installing at project scope records the plugin in .claude/settings.json. Commit that file and the plugin is enabled for everyone in the repo, though each teammate still installs it once on their own machine.

Auto-update is off by default for marketplaces you create, so after a new release, have teammates choose Update marketplace on the Marketplaces tab.

Plugin security checklist before you install

A plugin can run code with your user permissions. Hooks and MCP servers in particular run outside Claude Code's permission prompts, so install only plugins from sources you trust, and read what they contain first.

• Check the source: Marketplaces using Anthropic names such as claude-plugins-official are accepted only from github.com/anthropics repositories. Treat every other marketplace, even a coworker's, as third-party and check who owns the repo.
• Read Will install: In the /plugin details pane, review the skills, hooks, and MCP servers the plugin adds.
• Read what actually runs: Open each command in hooks/hooks.json, each server command or URL in .mcp.json, and every file in bin/. The details pane shows that a hook exists, not what it runs.
• Watch auto-updates: With auto-update on, files can change after you've reviewed them. For important repos, pin a version or review changes before updating.
• Remove what you no longer trust: Run claude plugin uninstall name --scope your-scope, and if you don't trust the marketplace either, remove it from the Marketplaces tab.

Turn daglo meeting notes into a task list with a plugin skill

Plugin skills shine when you apply them again and again to input with a steady format, like transcribed meetings. When you record a meeting with daglo, you get a transcript that shows who said what, plus a summary, which a skill can read right away.

1. With everyone's consent, record the meeting and upload it to daglo to transcribe.
2. Ask Board Chat, "List the decisions and follow-up tasks from this meeting, grouped by who raised them," and check the answer against the transcript.
3. Copy the result into meeting-notes.md in your project, then run the plugin skill in Claude Code, for example /meeting-tools:action-items meeting-notes.md. Put your team's rules in the skill, such as "make a table of each task with the related files and how to verify it."

Want the same format for every meeting? Save the request from step 2 in daglo's My Templates. daglo remembers the prompt and summarizes every new recording that way automatically.

To sum up: install one plugin from the official marketplace to learn the layout, bundle the skills you use most with a plugin.json, test with --plugin-dir, then share through a team marketplace. Commands and config formats can change between versions, so check the official plugin docs before you roll anything out.

#ClaudeCode #ClaudeCodePlugins #PluginMarketplace #ClaudeCodeSkills #MCP #AICoding #HarnessEngineering #daglo

👉 Transcribe your next meeting free