Auto-Pilot
Updated a month ago

claude-plugins-official

Aanthropics
4.7k
anthropics/claude-plugins-official
76
Agent Score

💡 Summary

A curated directory for discovering and installing plugins for Claude Code.

🎯 Target Audience

Claude Code users seeking to extend functionalityAI application developersProduct managers evaluating AI agent capabilitiesTechnical researchers exploring plugin ecosystems

🤖 AI Roast:It's a well-organized plugin directory, but its primary function is to point you to other things that actually do the work.

Security AnalysisLow Risk

The directory acts as a distribution point, inheriting all risks from the plugins it hosts (e.g., arbitrary code execution, network access, file system operations). The primary mitigation is the mandatory user trust check before installation, but a centralized review process for external plugins is implied yet not detailed.

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-plugin-directory

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-name/
├── .claude-plugin/
│   └── plugin.json      # Plugin metadata (required)
├── .mcp.json            # MCP server configuration (optional)
├── commands/            # Slash commands (optional)
├── agents/              # Agent definitions (optional)
├── skills/              # Skill definitions (optional)
└── README.md            # Documentation

Documentation

For more information on developing Claude Code plugins, see the official documentation.

5-Dim Analysis
Clarity8/10
Novelty6/10
Utility9/10
Completeness7/10
Maintainability8/10
Pros & Cons

Pros

  • Centralized, trusted source for plugins
  • Clear separation between internal and external contributions
  • Standardized plugin structure for consistency
  • Integrated installation via Claude Code interface

Cons

  • Relies entirely on external plugin quality
  • Limited functionality of the directory itself
  • Security vetting burden placed on the user
  • Potential for supply chain risks via third-party plugins

Related Skills

pytorch

S
toolCode Lib
92/ 100

“It's the Swiss Army knife of deep learning, but good luck figuring out which of the 47 installation methods is the one that won't break your system.”

agno

S
toolCode Lib
90/ 100

“It promises to be the Kubernetes for agents, but let's see if developers have the patience to learn yet another orchestration layer.”

nuxt-skills

S
toolCo-Pilot
90/ 100

“It's essentially a well-organized cheat sheet that turns your AI assistant into a Nuxt framework parrot.”

Disclaimer: This content is sourced from GitHub open source projects for display and rating purposes only.

Copyright belongs to the original author anthropics.