# How to Submit a New Plugin to the Claude Plugins Community Marketplace

> Submit your new plugin to the Claude Plugins Community Marketplace by completing the official web form. Learn the simple process to get your plugin listed and reach more users.

- Repository: [Anthropic/claude-plugins-community](https://github.com/anthropics/claude-plugins-community)
- Tags: how-to-guide
- Published: 2026-09-05

---

**To submit a new plugin, complete the official web form at [clau.de/plugin-directory-submission](https://clau.de/plugin-directory-submission) — do not open a pull request in the read-only mirror repository.**

The `anthropics/claude-plugins-community` repository serves as a **read-only mirror** of the official community marketplace. Understanding this architecture is essential for developers who want to distribute their Claude plugins to the broader community.

## The Submission Process Explained

The Claude plugin submission workflow operates through Anthropic's internal review pipeline rather than direct repository contributions. This ensures consistent security validation and quality control for all community plugins.

### Step 1: Submit via the Official Form

Navigate to **[clau.de/plugin-directory-submission](https://clau.de/plugin-directory-submission)** and provide the required metadata:

- Plugin name and description
- Source repository URL
- Commit SHA for verification
- Author contact information

As documented in [[`README.md`](https://github.com/anthropics/claude-plugins-community/blob/main/README.md)](https://github.com/anthropics/claude-plugins-community/blob/main/README.md#L24-L27), this form automatically forwards submissions to Anthropic's internal review system — no GitHub interaction required.

### Step 2: Automated Validation and Merging

After submission, the plugin undergoes automated security scanning through the CI pipeline defined in [[`.github/workflows/validate-plugins.yml`](https://github.com/anthropics/claude-plugins-community/blob/main/.github/workflows/validate-plugins.yml)](https://github.com/anthropics/claude-plugins-community/blob/main/.github/workflows/validate-plugins.yml). This workflow enforces strict invariants:

- Required field presence
- Proper SHA signature verification
- Schema compliance for the marketplace format

Once validation passes, the plugin entry is inserted into [[`.claude-plugin/marketplace.json`](https://github.com/anthropics/claude-plugins-community/blob/main/.claude-plugin/marketplace.json)](https://github.com/anthropics/claude-plugins-community/blob/main/.claude-plugin/marketplace.json). The repository updates nightly to reflect newly approved plugins.

### Step 3: Distribution to Users

Approved plugins become immediately installable via the Claude Code CLI. Users add the community marketplace once, then install any listed plugin by name.

## Installing and Using Community Plugins

Add the marketplace to your Claude Code installation:

```bash
claude plugin marketplace add anthropics/claude-plugins-community

```

Install any approved plugin using its slug:

```bash
claude plugin install <plugin-name>@claude-community

```

## Key Repository Files

Understanding these files clarifies why direct PRs are rejected:

| File | Purpose |
|------|---------|
| [`README.md`](https://github.com/anthropics/claude-plugins-community/blob/main/README.md) | Official documentation and submission link |
| [`.claude-plugin/marketplace.json`](https://github.com/anthropics/claude-plugins-community/blob/main/.claude-plugin/marketplace.json) | Canonical manifest of all approved plugins |
| [`.github/workflows/validate-plugins.yml`](https://github.com/anthropics/claude-plugins-community/blob/main/.github/workflows/validate-plugins.yml) | CI validation enforcing security and format requirements |

## Summary

- **Submit new plugins through [clau.de/plugin-directory-submission](https://clau.de/plugin-directory-submission)**, not GitHub pull requests
- The `anthropics/claude-plugins-community` repo is a **read-only mirror** updated nightly
- Automated validation in [`.github/workflows/validate-plugins.yml`](https://github.com/anthropics/claude-plugins-community/blob/main/.github/workflows/validate-plugins.yml) ensures security compliance
- Approved plugins appear in [`.claude-plugin/marketplace.json`](https://github.com/anthropics/claude-plugins-community/blob/main/.claude-plugin/marketplace.json) and become CLI-installable
- Users install plugins with `claude plugin install <name>@claude-community`

## Frequently Asked Questions

### Can I submit a plugin by opening a pull request to the repository?

No. The repository explicitly rejects direct contributions. All submissions must flow through the official web form at clau.de/plugin-directory-submission, which routes to Anthropic's internal review pipeline. This design maintains security standards and prevents unvetted code from entering the marketplace manifest.

### How long does plugin approval typically take?

The source code does not specify exact timelines. The repository updates nightly, suggesting the internal review pipeline operates on a cadence that aligns with this schedule. Complex plugins requiring deeper security review may take longer than simple, well-documented submissions.

### What validation checks does my plugin undergo?

The CI workflow in [`.github/workflows/validate-plugins.yml`](https://github.com/anthropics/claude-plugins-community/blob/main/.github/workflows/validate-plugins.yml) enforces multiple invariants: required metadata fields must be present, SHA signatures must match the claimed source repository, and the overall structure must comply with the marketplace JSON schema. Failures at any stage block inclusion until corrected.

### Where can I see the list of currently approved plugins?

Browse the canonical manifest at [`.claude-plugin/marketplace.json`](https://github.com/anthropics/claude-plugins-community/blob/main/.claude-plugin/marketplace.json) in the repository root. This file contains the complete, up-to-date registry of all community plugins available for installation via the Claude Code CLI.