What you can do with Claude Plugins Official

4 use cases

• Install a vetted plugin from the official marketplace

  Add a ready-made Claude Code plugin from the official directory in one command.

  • Claude Plugins Official
  • Claude Code
  • Software and DevOps
  • Beginner
  View prompt

  Using the anthropics/claude-plugins-official repo, install the plugin <plugin-name> with `/plugin install <plugin-name>@claude-plugins-official` in Claude Code. Report the install result and the plugin's homepage URL. Verify the plugin appears under `/plugin` before reporting success.

  Share Save

• Build a plugin in the standard layout for submission

  Scaffold a Claude Code plugin with the required manifest and submit it for review.

  • Claude Plugins Official
  • Claude Code
  • Software and DevOps
  • Intermediate
  View prompt

  In the anthropics/claude-plugins-official repo, scaffold a plugin folder named <plugin-name> that follows the standard structure with .claude-plugin/plugin.json and README.md, using /plugins/example-plugin as the reference. Output the list of created files. Verify that .claude-plugin/plugin.json exists and is valid JSON before preparing the submission.

  Share Save

• Publish existing SKILL.md files as a marketplace bundle

  List skill folders from a source repo in a marketplace entry with strict set to false.

  • Claude Plugins Official
  • Claude Code
  • Software and DevOps
  • Intermediate
  View prompt

  Using the strict false skill-bundle format in the anthropics/claude-plugins-official README, draft a marketplace entry for the skills at <skill-path> in <source-repo-url>. Output the JSON entry. Verify that every path in the skills array points to a directory containing a SKILL.md file.

  Share Save

• Change a published plugin's label without breaking installs

  Update displayName or add a renames entry so existing users keep working.

  • Claude Plugins Official
  • Claude Code
  • Software and DevOps
  • Intermediate
  View prompt

  In the anthropics/claude-plugins-official repo, update the marketplace entry for <plugin-name> so its UI label changes to <new-label> by setting displayName, without changing name. Output the diff. Verify that the name field is unchanged.

  Share Save

How to use Claude Plugins Official

1. Check you have what it needs: Claude Code with its plugin system; A plugin name listed in the claude-plugins-official marketplace; Git and a text editor for building or publishing a plugin.
2. Open anthropics/claude-plugins-official on GitHub and read the README and license.
3. Open Claude Code and run /plugin > Discover to browse the marketplace, or note the plugin name you want.
4. Read the plugin's homepage and confirm you trust it before installing.
5. Run /plugin install {plugin-name}@claude-plugins-official, replacing {plugin-name} with the plugin you chose.
6. Open /plugin to confirm the plugin is listed as installed.

These steps come from our top use case, Install a vetted plugin from the official marketplace, which also has a copy-paste agent prompt.

Claude Plugins Official alternatives · Best AI repos for Software and DevOps

About this repo

• Who it is forClaude Code users who want to install vetted plugins, and partners or maintainers who want to publish plugins or skill bundles.
• Why it is hot
• LanguagePython
• Sourcegithub.com/anthropics/claude-plugins-official · Back to Hot repos

Requirements

• Claude Code with its plugin system
• A plugin name listed in the claude-plugins-official marketplace
• Git and a text editor for building or publishing a plugin

Related repos

• #1 this week Harness2 Harness² is a Python framework from Google Research that refines the harness around a fixed model (prompts, tools, memory, skills, orchestration) so it performs better on agent tasks.
• #8 this week iFixAi iFixAi is an open-source Python tool that audits whether an AI agent is doing the job it is supposed to do, using 60 inspections that combine red-teaming with operational checks.
• #9 this week Orca Orca is a desktop app, with a mobile companion, for running several CLI coding agents side by side, each in its own git worktree, and tracking them in one place.