Claude Code Plugins Directory A curated directory of high quality plugins for Claude Code. ⚠️ Important: Make sure you trust a plugin before installing, updating, or using it. Anthropic does not control what MCP servers, files, or other software are included in plugins and cannot verify that they will work as intended or that they won't change. See each plugin's homepage for more information. Structure /plugins Internal plugins developed and maintained by Anthropic /external plugins Third party plugins from partners and the community Installation Plugins can be installed directly from this marketplace via Claude Code's plugin system. To install, run /plugin install {plugin name}@claude plugins official or browse for the plugin in /plugin Discover Contributing Internal Plugins Internal plugins are developed by Anthropic team members. See /plugins/example plugin for a reference implementation. External Plugins Third party partners can submit plugins for inclusion in the marketplace. External plugins must meet quality and security standards for approval. To submit a new plugin, use the plugin directory submission form. Plugin Structure Each plugin follows a standard structure: [安装/使用命令见下方] Plugin names are immutable The name field in a marketplace entry is an immutable slug . Once a plugin has been published, its name must not change — users have it installed under that slug, and renaming it breaks their install with a plugin not found error. To change how a plugin is labeled in the UI, set or update displayName instead. If a rename is genuinely unavoidable, add an entry to the top level renames map in .claude plugin/marketplace.json so existing installs auto migrate: [安装/使用命令见下方] The Claude Code plugin loader reads this map and transparently rewrites the old slug to the new one on the user's next sync. Skill bundle plugins When a plugin's source repository ships skills ( SKILL.md files) without a .claude plugin/plugin.json manifest, the marketplace entry can declare t