Claude Skills Marketplace: What It Is, How It Works, and Which One to Use (2026)

A Claude skills marketplace is a catalog you point Claude Code at to discover and install skills and plugins. The term covers two different things: in-product marketplaces, which are git repos or JSON feeds that the claude plugin marketplace add command consumes directly, and directory sites, which rank and curate skills across every source so you can decide what is worth installing. Most developers need one directory for choosing and one or two marketplaces for distribution.

Key takeaways

• An in-product marketplace is just a repo with a .claude-plugin/marketplace.json manifest; Claude Code reads it after one claude plugin marketplace add command.
• The ecosystem has three layers: registries count installs (skills.sh), directories rank and curate across sources (Skillselion), and in-product marketplaces distribute the actual plugins.
• The catalog tracks 10,264 marketplaces (skills.sh registry, July 2026), so "which marketplace" is a real filtering problem, not a shortage problem.
• Evaluate a marketplace on four signals: install counts, freshness of the underlying repos, security audit status, and official-vendor provenance.
• If you want one specific skill, skip the marketplace question entirely: find it in a directory and install it with one command.

What is a skills marketplace in the Claude Code sense?

In Claude Code, a marketplace is a source of plugins: a git repository (or a URL serving a JSON feed) containing a .claude-plugin/marketplace.json manifest that lists installable plugins, each of which can bundle skills, commands, agents, hooks, and MCP servers. When you run claude plugin marketplace add anthropics/skills, Claude Code fetches that manifest and everything in it becomes installable through the /plugin menu. Anyone can publish one; that is why the count is 10,264 marketplaces (skills.sh registry, July 2026), most containing a single plugin.

That is a narrower meaning than how the phrase gets used casually. Sites that list and rank skills are also called marketplaces, but they are directories: you browse them in a browser, not through the CLI. If you are new to skills themselves, start with what Claude Code skills are before choosing where to get them.

How do registries, directories, and marketplaces differ?

Three layers do different jobs, and conflating them is the main source of confusion around this topic:

• Registries are the install-count source of truth. The skills.sh registry records installs when developers run its CLI, which is where figures like 649,620 installs for Anthropic's frontend-design skill come from (skills.sh registry, July 2026).
• Directories rank and curate across every source: registries, GitHub, and in-product marketplaces. Skillselion's marketplaces hub lists 12,649 marketplaces and plugins ranked by real usage signals, and the leaderboard ranks the skills themselves. A directory answers "which of these is actually good", which a raw registry or a single marketplace repo cannot.
• In-product marketplaces distribute. They are the delivery pipe Claude Code pulls from; they have no opinion about quality beyond what the maintainer includes.

The practical workflow: choose in a directory, install from a registry or marketplace. This guide is about choosing; if you want the registry-vs-registry comparison, that is a separate topic.

How do you add a marketplace to Claude Code?

Two commands, one minute:

# Add the marketplace (owner/repo, full git URL, or JSON feed URL)
claude plugin marketplace add anthropics/skills

# Install a plugin from it
claude plugin install [plugin-name]@skills

Inside a session, /plugin marketplace add and the /plugin browse menu do the same job interactively. Marketplaces you add are recorded in your settings, and claude plugin marketplace update refreshes the manifest. For the single-skill path that skips marketplaces entirely, see how to install a Claude skill.

How should you evaluate a marketplace before adding it?

Adding a marketplace means trusting its maintainer's judgment about what runs inside your agent. Four checks, in order:

1. Install counts. Not for the marketplace itself, but for the skills in it. A marketplace whose contents nobody installs is unvetted by definition. Cross-check names on the leaderboard; numbers like 271,156 installs for brainstorming (skills.sh registry, July 2026) tell you thousands of developers ran this code before you. 2. Freshness. Check the last push date on the underlying repo. Skills targeting fast-moving tools go stale in months; a manifest pointing at abandoned repos is a liability. 3. Security audits. Skills are instructions plus executable scripts. Prefer sources where contents have been audited or at least had their file trees inspected; read the SKILL.md and bundled scripts before installing anything that touches credentials or CI. 4. Official-vendor provenance. A marketplace published from the vendor's own GitHub org (Anthropic's anthropics/skills, Upstash's context7) carries accountability a personal fork does not. Directories flag official-vendor listings for exactly this reason.

Which marketplace should you use?

Depends on what you are actually trying to do:

• You want one specific capability. Do not add a marketplace at all. Search a directory, verify install count and audit status, and install the single skill. Example: 454,396 installs for web-design-guidelines (skills.sh registry, July 2026) is a stronger signal than any marketplace membership.
• You want a proven general-purpose workflow bundle. Add one curated community marketplace with high aggregate installs, such as obra/superpowers, and stop there. Every added marketplace widens your trust surface.
• You are standardizing a team. Prefer official vendor marketplaces for the tools already in your stack, plus a private marketplace repo of your own; any internal git repo with a marketplace.json works with claude plugin marketplace add. Plugins and skills interact here, so read the Claude Code plugins guide before rolling this out.

Install counts come from the skills.sh registry via the Skillselion catalog, snapshot July 2026.

Common questions