Claude Skills Marketplace: Where to Find Skills

As of mid-2026, there is no single official “Claude skills marketplace” or app store. The official distribution path is plugins and plugin marketplaces — git-repo-based catalogs that list installable plugins — and skills ship inside those plugins. Alongside that official channel, people find skills through the anthropics/skillsreference repo, community “awesome” lists, and third-party directory sites. The ecosystem is decentralized by design: anyone can host a marketplace, and no one controls a central index.

Is there an official Claude skills marketplace?

No — not in the sense most people expect. There is no centralized storefront where you browse, rate, and one-click-install Claude skills the way you would VS Code extensions. As of mid-2026, the official, supported way to distribute and discover skills is through plugins and plugin marketplaces. A skill on its own is a small unit; to publish it for others, you bundle it into a plugin, and you make that plugin discoverable by hosting (or pointing at) a marketplace.

That distinction matters because the searches for “claude skills marketplace” usually assume a single destination. In practice you’re assembling skills from severalsources, and the “marketplace” concept is a decentralized, git-based mechanism rather than one website.

How are Claude skills distributed?

Skills travel through plugins. A plugin can bundle commands, subagents, hooks, and skills together. A plugin marketplace is a git repository (or even a local directory) that contains a .claude-plugin/marketplace.json file listing the plugins it offers. You add a marketplace once, then install any plugin it lists; the skills inside become available automatically.

Because a marketplace is just a repo, the model is fully decentralized. Anthropic doesn’t gatekeep a registry, and there’s no approval queue. Anyone — an individual, a team, an open-source project — can publish a marketplace and share the owner/repofor others to add. That is powerful, but it also means there’s no single authoritative list of what exists.

A skill itself is simple: a directory with a SKILL.md file. The YAML frontmatter requires only two fields — name and description — written in the third person to describe what the skill does and when Claude should reach for it. (For the full anatomy, see the skills guide.)

However it arrives, an installed skill resolves from one of three places on disk:

Where to find Claude skills today

Since there’s no single index, it helps to know the handful of sources people actually use. Here’s the landscape as of mid-2026:

For a curated starting point with real, copy-pasteable examples, see our roundup of Claude skills examples.

How to install a skill from a marketplace

Installation happens at the plugin level, and it’s a two-step flow inside Claude Code. First you register the marketplace (the git repo that lists plugins), then you install a specific plugin from it. Any skills the plugin bundles become available right away.

# 1. Add a marketplace (a git repo with .claude-plugin/marketplace.json)
/plugin marketplace add owner/some-marketplace

# 2. Install a plugin from that marketplace
/plugin install my-plugin@some-marketplace

# Skills bundled in the plugin now load from <plugin>/skills/

1. 1

   Add the marketplace

   Register the git repo that lists plugins with /plugin marketplace add <owner/repo>. You do this once per marketplace.
2. 2

   Install the plugin

   Pull a specific plugin from it with /plugin install <name>@<marketplace>.
3. 3

   The skill is available

   Any skills bundled in that plugin load automatically from <plugin>/skills/ — no extra step.

That’s the whole loop for marketplace-delivered skills. For standalone skills shared as a plain repo of SKILL.mddirectories, there’s no install command — you copy the skill folder into ~/.claude/skills/(global) or your project’s .claude/skills/ (repo-scoped). Both approaches end up in one of the three locations Claude resolves skills from.

How to share your own Claude skills

Sharing is the mirror image of installing. You have two realistic paths:

• Publish through a marketplace. Package your skill (or a set of skills) inside a plugin, then host a plugin marketplace — a git repo with a .claude-plugin/marketplace.json that lists your plugin. Share the owner/repo; others run /plugin marketplace add and /plugin install to pull it in. This is the discoverable, official route.
• Share as a plain skills repo. Put each skill in its own directory with a SKILL.md and publish the repo. People copy the folders they want into .claude/skills/. Simpler to produce, but not installable as a unit and not centrally discoverable.

Either way, the quality of your description frontmatter is what determines whether Claude reaches for the skill at the right moment — write it in the third person and say exactly when it applies. If your skills bundle automation, the same plugin can also ship subagents and hooks.

Finding skills is easy — managing them is the hard part

Here’s the pattern that shows up over and over once teams get past the “where do I find skills” question: discovering a good skill takes five minutes; keeping it consistentacross every repo and every tool takes ongoing effort. A skill you grabbed from a marketplace lives in one project. The next project doesn’t have it. A teammate’s copy has drifted. Cursor and the other tools want the same intent in a different format entirely.

Plugin marketplaces solve distribution— getting a skill onto your machine. They don’t solve governance: versioning your own skills, deploying the same set to twenty projects, and keeping the Claude-format, Cursor-format, and AGENTS.md-format copies in sync. That gap is exactly what people run into after the marketplace search is over.

Your own skills library across projects

This is the wedge Skillwright is built for. Instead of scattering marketplace-installed skills across project folders and hoping they stay in sync, you keep one canonical libraryof your rules and skills, version it, and compile it out to every project and every tool’s native format. Find skills wherever you like — the anthropics/skills repo, a marketplace, an awesome list — then make them part of a library you actually control, rather than copies that drift.

To make that easy to start, Skillwright ships six MIT-licensed starter skills at templates— code-review, commit-conventions, typescript-strict, security-review, tdd-workflow, and accessibility-a11y. Use them as-is, adapt them, or treat them as a model for writing your own. If you’re juggling skills and rules across several editors, read how to manage AI coding rules across tools next — that’s where the “one library, every format” idea pays off.

Frequently asked questions