There's no single Claude skills marketplace as of October 2026. Skills come from four places: the directory inside Claude (Customize, then Skills, then Browse skills), Claude Code plugin marketplaces such as Anthropic's own anthropics/skills, your organisation's own directory on Team and Enterprise plans, and third-party Agent Skills directories such as skills.sh.
If you meant Anthropic's Claude Marketplace for connectors, partner agents and service partners, that's a separate thing, and my guide to the Claude Marketplace covers it. This page is only about where skills come from and how to judge them.
Short answer: four places, no single store
| Place | What you find | Who it suits | Check before adding |
|---|---|---|---|
| The directory inside Claude | Anthropic's skills and partner skills from companies such as Notion, Figma and Atlassian | Anyone using Claude chat or Cowork | Who made it; it's view-only once added |
| Claude Code plugin marketplaces | Catalogues of plugins, which bundle skills, listed in a marketplace file | Claude Code users | Whose repository hosts it, and every file in the plugin |
| Your organisation's directory | Skills colleagues published and skills owners provisioned | Team and Enterprise plans | Who owns it and whether it passed review |
| Third-party directories such as skills.sh | Community skills from many repositories, ranked by installs | People comfortable reading code | The source repository and every bundled file |
Inside Claude: the directory
The closest thing to a skills store is the directory built into Claude. It now holds skills, connectors and plugins in one place, each on its own tab. For skills, go to Customize, then Skills, click the plus button and choose Browse skills. Click Add, and the skill lands in your list, enabled by default, so Claude can use it when relevant.
Partner skills here come from companies such as Notion, Figma and Atlassian, and are designed to work with those companies' MCP connectors, so they're most useful if you've already set up the matching Claude connector. Anything you add from the directory is view-only. If you want to change one, download a copy, edit it and upload it as your own.
In Claude Code: plugin marketplaces
In Claude Code, the word marketplace means something very specific. It's a directory or repository containing a file at .claude-plugin/marketplace.json that lists plugins and where to fetch each one. That file needs a name, an owner and a plugins array, and each plugin entry needs a name and a source. You register a marketplace with one command, then install plugins from it. Plugins bundle skills with other pieces, which my Claude plugins guide explains.
Anthropic's own skills repository works exactly this way. Add it, then install the document skills or the example skills:
Copy these commands
/plugin marketplace add anthropics/skills
/plugin install document-skills@anthropic-agent-skills
One safeguard worth knowing: official Anthropic marketplace names are reserved. If someone tries to add a marketplace using a name such as claude-plugins-official, Claude Code refuses it with a message saying the name is reserved for official Anthropic marketplaces. That stops a copycat catalogue passing itself off as Anthropic's.
Your own team marketplace
You don't have to rely on anyone else's catalogue. A team can build its own plugin marketplace, check it with claude plugin validate, push it to a git host, and teammates register it with claude plugin marketplace add followed by the owner slash repo name. On Team and Enterprise plans in the Claude app, the simpler route is your organisation's directory: colleagues publish skills to it, owners can require review before anything appears, and the Your organization tab lists everything available to the company. Plugins your organisation distributes through a marketplace also show up on the Discover tab.
Third-party skills directories
Outside Anthropic, directories list skills from many authors. skills.sh describes itself as the open Agent Skills ecosystem and shows a leaderboard of skills with their source repositories and install counts, sorted by all time, trending and hot. You install from it with an npx command followed by the owner slash repo name. Anthropic's own repository README even carries a skills.sh badge.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Treat these directories as discovery, not endorsement. A high install count tells you a skill is popular, not that it's safe or that it suits your business. Because skills follow the open Agent Skills format, many will work in Claude and in other tools, which my Agent Skills explainer covers.
How to check a skill before you add it
Skills can run code. Anthropic's Platform docs say to use skills only from trusted sources, meaning ones you created or got from Anthropic, and to treat anything else like installing software. If you're adding one from elsewhere:
- Check who published it and where the source repository lives.
- Read SKILL.md and every bundled file, including scripts and images.
- Look for network calls, or instructions to connect to outside sources, that don't match what the skill says it does. Skills that fetch content from web addresses carry extra risk, because that content can contain malicious instructions.
- Remember that even a trustworthy skill can change if something it depends on changes later.
- Test it on work with no client or customer data first.
- On Enterprise, ask your owner whether skill scanning is on; it checks uploaded skills and plugins for malicious content.
Where I'd look first
I'd use the directory inside Claude first, because its skills come from Anthropic, named partners or your own organisation, and adding a skill takes one click. If you use Claude Code, add Anthropic's own marketplace next. Skip third-party directories unless you, or someone on your team, can read the code in a skill before it goes anywhere near client work. A popular skill you haven't read is still a stranger's code running with your files.
If your team is working out where to source Claude skills and how to vet them before they touch client work, that's the kind of AI enablement I help with. I run AI training and workshops for teams, and help businesses with AI enablement and workflow automation, so the busywork runs itself and people get time back. Most of that work is with SaaS marketing teams and small businesses. Here's how we can work together.
Frequently asked questions
Is there a Claude skills marketplace?
Not a single store. As of October 2026 skills come from the directory inside Claude, Claude Code plugin marketplaces, your organisation's directory, and third-party directories such as skills.sh.
How do I browse Claude skills?
Go to Customize, then Skills, click the plus button and choose Browse skills. Click Add on any skill to put it in your list.
How do I add Anthropic's skills marketplace to Claude Code?
Run /plugin marketplace add anthropics/skills, then install a plugin such as /plugin install document-skills@anthropic-agent-skills.
Is skills.sh run by Anthropic?
No. skills.sh is a third-party Agent Skills directory. Anthropic's repository README shows a skills.sh badge, but treat it as a place to discover skills, not an endorsement.
Are skills from third-party directories safe?
Not automatically. Anthropic says to use skills you made or got from Anthropic, and to audit every bundled file before enabling a skill from anywhere else.
