anthropics/claude-plugins-community: the read-only plugin mirror Claude Code points at

What the community plugin mirror actually is

The README opens with a sentence that is easy to skim past: this is a read-only mirror of the community plugin marketplace. Nothing in the repository is the plugin. The repository is the index. The single file that matters is .claude-plugin/marketplace.json, which the README describes as the list of community plugins available to install.

The audience is narrow and specific. It is for people running Claude Code or Claude Cowork who want a plugin that someone else wrote, and for plugin authors who have already gone through Anthropic's submission process. It is not a framework, not a runtime, and not a library you import. If you arrived expecting source code for the plugins themselves, the top-level entries will look wrong: alongside LICENSE and README.md there are directories named eli5, quickdesign, testdino and tres-finance-plugin, which read like individual plugin payloads rather than shared infrastructure.

The value proposition is the review gate. The README states that every plugin listed here has been submitted through clau.de/plugin-directory-submission, passed automated security scanning, and been approved for distribution. That approval is the product. You are trading the ability to publish instantly for the assurance that someone ran a scanner and a human signed off.

How the marketplace.json sync pipeline works

The data flow is one-directional and the README is explicit about it. Plugins are submitted through a web form, they enter Anthropic's internal review pipeline, and .claude-plugin/marketplace.json is synced nightly from that pipeline into this repository. The mirror is downstream of the decision, never upstream of it.

That ordering explains the sharpest line in the README: pull requests opened directly against this repository are closed automatically, because all changes flow from the internal review pipeline. A merged pull request here would be overwritten by the next nightly sync, so the project does not pretend to accept them. It closes them.

The practical consequence is that the git history of this repository is a log of what the review pipeline approved on each night, not a log of community contributions. If you want to know when a plugin appeared, the commit that touched marketplace.json is the record. If you want to know why a plugin was rejected, the repository cannot tell you, because rejections never reach it. The README does not document the review criteria, the scanning tooling, or the expected turnaround time for a submission.

Installing a community plugin in Claude Code

The README gives two commands for Claude Code. The first registers the marketplace, the second installs a plugin from it. Run them in that order, and replace the placeholder with a name that appears in .claude-plugin/marketplace.json.

claude plugin marketplace add anthropics/claude-plugins-community
claude plugin install <plugin-name>@claude-community

The @claude-community suffix is the marketplace identifier, not part of the plugin name. If you type the plugin name without it, the CLI has no reason to look in this marketplace. After the add command succeeds the marketplace is registered locally; after the install command succeeds the plugin is available to Claude Code.

Claude Cowork does not use these commands. The README directs Cowork users to claude.com/plugins and stops there. There is no CLI path documented for Cowork and no self-hosted or offline installation route described anywhere in the repository.

To see what is installable before you commit to anything, read the manifest directly rather than guessing names. It is a JSON file at a fixed path, and the repository is public, so the list is inspectable without installing the marketplace at all.

The mirror model has real costs

The first limitation is latency you cannot measure. The README says the sync is nightly but does not say how long a submission takes to clear review, so a plugin author has no documented expectation to plan against. A plugin can be approved and still be invisible here for a day.

The second is that this repository cannot be your distribution channel if you want control. You cannot patch a plugin here, cannot pin a version here, and cannot roll back a bad release here, because the file is regenerated from a pipeline you do not operate. The README does not document rollback, version pinning or yanking. If a plugin you depend on is removed upstream, the next sync removes it from the manifest and the repository offers no archive of the previous state beyond git history.

The third is that the review gate is a floor, not a guarantee. Automated security scanning catches classes of problems that scanners catch. It is not a code review of business logic, and the README makes no claim about what the plugins do once installed. A plugin that passes scanning can still be a bad fit for your environment, and the manifest gives you a name, not a risk assessment.

Finally, the wrong-tool case: if you are developing a plugin and want fast iteration with collaborators, this repository is useless to you. There is no path from a local plugin directory into this marketplace except the submission form, and no staging area documented for testing before review.

Where it sits next to the official and knowledge-work repositories

The README lists two related repositories, and the distinction is the whole point of having three. anthropics/claude-plugins-official holds Anthropic-maintained plugins. anthropics/knowledge-work-plugins holds role-specific knowledge-work plugins. This repository holds community-contributed plugins.

The difference in approach is governance, not code. The official repository is maintained by Anthropic directly, so its contents move at Anthropic's release cadence and carry Anthropic's own support expectations. This repository is a mirror of a review pipeline that ingests outside submissions, so its contents move at the speed of the queue and depend on third-party authors continuing to maintain their plugins. The knowledge-work repository is scoped by job function rather than by authorship.

For an adopter, the practical rule is that anything you would put in a production workflow and need supported should come from the official repository, and anything experimental or niche is more likely to exist only here. That is a judgement about accountability, not about code quality, since a community plugin can be better written than an official one. But when something breaks, the official repository has an owner and this one has a submission form.

Licence, maintenance and what upgrading costs you

The repository carries Apache-2.0. That covers this repository's own contents, which in practice means the manifest and the README. It does not automatically cover the plugins the manifest points at, because those are separate works by separate authors with their own licences. The README does not state that per-plugin licence terms are surfaced anywhere in the manifest, so anyone redistributing or vendoring a plugin should check that plugin's own repository. This is a description of what the licence file covers, not legal advice.

On maintenance, the last push to this repository was on 2026-08-25. That is consistent with a mirror that only changes when the upstream pipeline approves something, and it means long gaps between commits are expected rather than a sign of abandonment. The README does not describe a support channel, an issue triage process, or a deprecation policy for plugins that stop being maintained by their authors.

Upgrade cost is close to zero for the mirror itself, since you never edit it. The cost sits with the plugins. Because the manifest is regenerated nightly, an installed plugin can change underneath you without a version bump you control. The README documents no pinning mechanism, so the only verification available is reading .claude-plugin/marketplace.json and the plugin's own repository before you install.

Editorial conclusion

Adopt it if you already run Claude Code and want plugins that have passed automated security scanning and review, or if you are publishing a plugin and want it distributed through Anthropic's pipeline rather than your own README. Do not adopt it if you need a plugin that is not in the catalogue, because there is no route to add one from this repository. Before installing anything, verify that .claude-plugin/marketplace.json lists the plugin under the name you intend to type, and confirm the licence of each plugin's own repository, since this mirror does not carry per-plugin licence terms.

Frequently asked questions

Official sources

1. anthropics/claude-plugins-community on GitHub
2. Issues
3. License: Apache-2.0
4. README