Claude Code Marketplace Complete Plugin List | How to Use Curated Plugins

What Is Claude Code Marketplace — The 3-Layer Architecture

Claude Code Marketplace is the official mechanism for listing and distributing Plugins and Skills. At its center is the official marketplace operated by Anthropic (claude-plugins-official), and independently from that, any Git repository can host its own marketplace (Source: Creating and Distributing Plugin Marketplaces).

Here is how the 3 layers relate to each other.

Two terms that appear frequently throughout this article: LSP (Language Server Protocol) provides Claude Code with code completion, type diagnostics, and definition jumping for various programming languages. MCP (Model Context Protocol) is the standard protocol for connecting Claude to external services such as GitHub and Slack. Keeping these two terms in mind will make the reference tables much easier to follow.

From a user perspective, you add a marketplace with /plugin marketplace add owner/repo, then install only the Plugins you want from it using /plugin install <name>@<marketplace>. A Plugin can contain multiple Skills, and individual Skills can be invoked as slash commands via /<skill-name>. If a Plugin has a namespace, the format is /plugin-name:skill-name.

The Role of the Official Marketplace

The official marketplace claude-plugins-official lists Anthropic-certified Plugins. It becomes available automatically when you launch Claude Code, and you can browse it via the Discover tab in /plugin. Separately, the anthropics/claude-code repository contains a demo marketplace that requires manual addition (adding it via /plugin marketplace add anthropics/claude-code registers it under the identifier anthropics-claude-code), which includes example plugins demonstrating the possibilities of the plugin system. Internal tools and client-specific scripts can be distributed via your own private marketplace, and hosting it on a GitHub Private repository combined with extraKnownMarketplaces enables internal-only distribution.

Note that names such as claude-code-marketplace, claude-code-plugins, claude-plugins-official, anthropic-marketplace, anthropic-plugins, agent-skills, knowledge-work-plugins, and life-sciences are officially reserved and cannot be used as third-party marketplace names. Names that impersonate official sources, such as official-claude-plugins, are also blocked.

Large Table 1 — Complete List of Public Marketplaces (20+ Entries)

Below is a complete list of plugins available in the official marketplace (claude-plugins-official) and the demo marketplace (anthropics/claude-code). The install command format is /plugin install <name>@<marketplace> (Source: Discovering and Installing Plugins).

Plugins in the Official Marketplace claude-plugins-official

Install with /plugin install <name>@claude-plugins-official.

Plugins in the Demo Marketplace anthropics/claude-code (anthropics-claude-code)

Add with /plugin marketplace add anthropics/claude-code, then install with /plugin install <name>@anthropics-claude-code (Source: Discovering and Installing Plugins).

Large Table 2 — Complete Reference of Plugin Source Types (15+ Entries)

Each plugin entry in marketplace.json requires a source field that tells Claude Code where to fetch the plugin from. There are 5 source types available (Source: Creating and Distributing Plugin Marketplaces).

Pinning Strategy with sha and ref

For github, url, and git-subdir sources, both ref (branch / tag) and sha (full 40-character commit SHA) can be specified. Use sha to pin to a specific release, or ref: main to track the latest. Note that the marketplace source side only supports ref and does not accept sha — this asymmetry is by design to reduce maintenance burden on the marketplace side.

Using git-subdir for Monorepos

When a single repository like acme-corp/monorepo contains a large number of internal tools, git-subdir lets you use Git sparse checkout to fetch only the specified directory. Even for a 500MB monorepo, only the few megabytes of the required subdirectory are fetched, significantly reducing bandwidth consumption. The url field accepts GitHub shorthand (owner/repo) or SSH URLs.

Large Table 3 — Complete Field Reference for marketplace.json / plugin.json / SKILL.md (20+ Entries)

All Fields in marketplace.json

All Fields in marketplace.json Plugin Entries

All Fields in plugin.json

All Fields in SKILL.md Frontmatter

5 Plugin Source Types — Detailed Fetch Paths

The large table 2 above covered all source types comprehensively. Here we show configuration JSON examples for each source (Source: Creating and Distributing Plugin Marketplaces).

GitHub Source

{
  "name": "deployment-tools",
  "source": {
    "source": "github",
    "repo": "company/deploy-plugin",
    "ref": "v2.0.0",
    "sha": "a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0"
  }
}

ref is the branch or tag to track; sha pins to an exact commit for reproducibility. Either one alone is sufficient.

git-subdir Source (for Monorepos)

{
  "source": {
    "source": "git-subdir",
    "url": "https://github.com/acme-corp/monorepo.git",
    "path": "tools/claude-plugin",
    "ref": "v2.0.0"
  }
}

Even for a 500MB monorepo, only the few megabytes of the required subdirectory are fetched via sparse clone. The url field also accepts the owner/repo shorthand or SSH URLs like git@github.com:....

npm Source

{
  "name": "my-npm-plugin",
  "source": {
    "source": "npm",
    "package": "@acme/claude-plugin",
    "version": "^2.0.0",
    "registry": "https://npm.example.com"
  }
}

version accepts semver ranges (^2.0.0, ~1.5.0, etc.). Specify a private registry using registry.

Creating Your Own Marketplace — Minimum 5 Steps

Here is the procedure for creating a "marketplace containing 1 Plugin" with minimal configuration, using a Plugin with a single Skill called /quality-review as an example (Source: Creating and Distributing Plugin Marketplaces).

# Step 1: Create directory structure
mkdir -p my-marketplace/.claude-plugin
mkdir -p my-marketplace/plugins/quality-review-plugin/.claude-plugin
mkdir -p my-marketplace/plugins/quality-review-plugin/skills/quality-review

# Step 2: Create SKILL.md
cat > my-marketplace/plugins/quality-review-plugin/skills/quality-review/SKILL.md <<'EOF'
---
description: Review code for bugs, security, and performance
disable-model-invocation: true
---
Review the code I've selected or the recent changes.
EOF

# Step 3: Create plugin.json
cat > my-marketplace/plugins/quality-review-plugin/.claude-plugin/plugin.json <<'EOF'
{
  "name": "quality-review-plugin",
  "description": "Adds a /quality-review skill for quick code reviews",
  "version": "1.0.0"
}
EOF

# Step 4: Create marketplace.json
cat > my-marketplace/.claude-plugin/marketplace.json <<'EOF'
{
  "name": "my-plugins",
  "owner": { "name": "Your Name" },
  "plugins": [
    {
      "name": "quality-review-plugin",
      "source": "./plugins/quality-review-plugin",
      "description": "Adds a /quality-review skill for quick code reviews"
    }
  ]
}
EOF

# Step 5: Local test → share
# /plugin marketplace add ./my-marketplace
# /plugin install quality-review-plugin@my-plugins

Once pushed to GitHub, team members can import the catalog with /plugin marketplace add owner/my-marketplace.

Version Resolution Pitfalls

When you set the version field in plugin.json or a marketplace entry, Claude Code will not detect updates unless that version string changes. Even if you push new commits while keeping "version": "1.0.0", users will continue using the cached old code. The workaround is either (1) bump the version on every release, or (2) remove the version field and let Claude Code use the Git commit SHA as the version automatically. For internal tools where you want everyone to always have the latest version, option (2) is the better choice.

Strict Mode (strict) and Organization Distribution

Behavior of strict: true / false

The strict field in a marketplace.json plugin entry controls whether plugin.json or the marketplace entry itself is the authority for component definitions (Source: Creating and Distributing Plugin Marketplaces).

Using strict: false gives the marketplace operator full control over the component configuration when packaging raw files as a Plugin. This is useful when you want to expose content from a different angle than the plugin author intended.

Organization Distribution — Complete strictKnownMarketplaces Configuration Examples

To deploy a marketplace as the default for an organization while blocking any external additions, combine two settings in the management configuration .claude/settings.json (Source: Creating and Distributing Plugin Marketplaces).

{
  "extraKnownMarketplaces": {
    "company-tools": {
      "source": { "source": "github", "repo": "your-org/claude-plugins" }
    }
  },
  "enabledPlugins": {
    "code-formatter@company-tools": true,
    "deployment-tools@company-tools": true
  },
  "strictKnownMarketplaces": [
    { "source": "github", "repo": "your-org/claude-plugins" },
    { "source": "hostPattern", "hostPattern": "^github\\.example\\.com$" },
    { "source": "pathPattern", "pathPattern": "^/opt/approved/" }
  ]
}

The behavior corresponding to each strictKnownMarketplaces value is shown in the table below.

Using hostPattern with a regex that matches your GitHub Enterprise Server hostname allows all repositories under that domain. For automatic updates from private repositories, set the GITHUB_TOKEN / GITLAB_TOKEN / BITBUCKET_TOKEN environment variables to enable background authentication.

Container Pre-seeding and Environment Variables

For CI / production containers, you can use the CLAUDE_CODE_PLUGIN_SEED_DIR environment variable to specify a pre-seeded directory. By building the ~/.claude/plugins structure once at build time, the runtime can use it read-only. This is essential for air-gapped environments or offline CI. Additionally, setting CLAUDE_CODE_PLUGIN_KEEP_MARKETPLACE_ON_FAILURE=1 will retain the existing cache when a git pull fails, allowing the system to continue with the last known good state. The timeout for Git operations can be adjusted with CLAUDE_CODE_PLUGIN_GIT_TIMEOUT_MS (default: 120,000ms).

Summary — Decision Criteria for Operating Claude Code Marketplace

Claude Code Marketplace is a 3-layer catalog mechanism for distributing Plugins and Skills, built on a lightweight design that requires only a Git repository and a marketplace.json. The official marketplace includes 20+ plugins covering LSP, MCP, and workflows, available instantly via /plugin install <name>@claude-plugins-official. When building your own marketplace, understand the 3 files — marketplace.json, plugin.json, and SKILL.md — and choose from 5 source types (relative path / github / url / git-subdir / npm) based on your use case. Use git-subdir for monorepos, npm for npm-managed packages, and github for simple OSS distribution. For organization distribution, the standard approach is to combine extraKnownMarketplaces for automatic team-wide provisioning with strictKnownMarketplaces to enforce security policies. For version management, omitting the version field and relying on git SHA reduces unnecessary overhead for actively developed plugins.

Sources (Primary Information)

• Creating and Distributing Plugin Marketplaces (Claude Code Official Documentation)
• Discovering and Installing Existing Plugins (Claude Code Official Documentation)
• Creating Plugins (Claude Code Official Documentation)
• Plugin Reference (Claude Code Official Documentation)
• Extending Claude with Skills (Claude Code Official Documentation)
• anthropics/claude-code Plugin List (GitHub)

Related Articles

• Introduction to Claude Code — 9 Features That Work Even for Non-Engineers
• Getting Started with Custom Claude Skills — The Minimal SKILL.md
• What Can You Do with Claude's 4 Official Plugin Types and Custom Ones
• What Is Claude MCP — Full Feature List and 5 Connection Steps
• Pitfalls of Claude Code Computer Use