Claude Skills Marketplace: Where to Find and Submit Claude Skills (2026)

There is no single official "Claude Skills Marketplace." Skills ship inside plugins, and plugins live in two Anthropic-run catalogs (claude-plugins-official and claude-community) plus Anthropic's own demonstration repo on GitHub (anthropics/skills). A handful of independent sites, including SkillsMP, AugmentClaude, and ClaudeSkillsMarket, index or curate community skills separately, but none of them are run by Anthropic and none certify quality or safety. To submit a skill for wide distribution, package it as a plugin and run it through the community marketplace review process.

What a Claude Skill actually is

A Skill is a folder with a SKILL.md file at its root: YAML frontmatter (name, description, and a few optional fields) followed by markdown instructions. Claude reads the frontmatter description to decide when a skill is relevant, then loads the full body only at that point. That lazy loading is the whole design goal: a skill can carry a long reference document, a checklist, or a multi-step procedure without costing any context tokens until Claude actually needs it.

Skills can also bundle supporting files: scripts in any language, templates, reference docs. A skill that generates an interactive HTML report, for instance, ships the Python script alongside SKILL.md and tells Claude to run it with ${CLAUDE_SKILL_DIR} resolving the path regardless of where the skill is installed.

Claude Code skills follow the Agent Skills open standard (documented at agentskills.io), which is meant to work across multiple AI tools, not just Claude. Claude Code layers a few extensions on top of that standard: invocation control (who can trigger a skill, you or Claude), subagent execution, and dynamic context injection. If you're authoring a skill you want to reuse outside Claude Code, stick to the frontmatter fields the standard defines and treat the Claude-specific fields as optional extras.

Custom commands and skills are the same mechanism now. A file at .claude/commands/deploy.md and a skill at .claude/skills/deploy/SKILL.md both produce a /deploy command. Older .claude/commands/ files still work; skills just add the option of a supporting-files directory, automatic invocation, and frontmatter-level access control.

Where skills actually live and load from

Claude Code looks for skills in a defined set of locations, in this order of proximity:

• Project skills: .claude/skills/ inside the repo, committed to version control so the whole team gets them.
• Personal skills: a user-level skills directory that applies across every project you open.
• Plugin skills: a skills/ folder inside an installed plugin.
• Managed skills: deployed org-wide through managed settings, for teams that need central control.
• Synced skills: pulled in from claude.ai when your account has skills configured there.

Claude Code also watches for live changes to skill files and re-reads nested directories, so adding a new SKILL.md mid-session doesn't require a restart. If you only need a skill for one project, a project skill is the right scope. If you're distributing something for other people to install, package it as a plugin.

Where to actually find and browse Claude Skills right now

Anthropic's own sources

• anthropics/skills on GitHub. Anthropic's demonstration repository, organized into creative/design, development/technical, enterprise/communication, and document skill sets. Most are Apache 2.0 licensed; the docx, pdf, pptx, and xlsx skills that power Claude's built-in document creation are source-available rather than open source. Anthropic is explicit that these are demonstration and educational material, not a guarantee that Claude's live behavior will match every implementation detail.
• claude-plugins-official. The curated marketplace Claude Code registers automatically on first interactive launch. Browse it inside the CLI with /plugin and the Discover tab, or at claude.com/plugins. Skills distributed as first-party or partner plugins show up here. Inclusion is entirely at Anthropic's discretion; there's no public application queue for this catalog.
• claude-community. The public marketplace where third-party plugin (and skill) submissions land once they pass Anthropic's review pipeline. Add it with /plugin marketplace add anthropics/claude-plugins-community and install with the @claude-community suffix.
• agentskills.io. Documentation for the underlying Agent Skills open standard itself, separate from Anthropic's product docs. Useful if you're building a skill meant to work outside Claude Code too.

Independent community sites

These are third-party projects, not run or endorsed by Anthropic. Descriptions below are what each site says about itself; none of them is a claim we can independently verify for accuracy, uptime, or moderation quality, and none of them certifies the skills they list.

• SkillsMP (skillsmp.com). Describes itself as an index of public GitHub SKILL.md files, organized by field and occupation, with a stated count in the millions of collected files as of this writing. The site says outright that it does not certify the quality or safety of what it indexes.
• AugmentClaude (augmentclaude.com). A community marketplace claiming several hundred free skills organized into curated bundles, plus its own submission flow, an install-commands reference, and a page comparing marketplaces. It also distributes an MCP server that loads its catalog into an agent directly.
• ClaudeSkillsMarket (claudeskillsmarket.com). Self-described as an "independent" Claude Skills marketplace with several dozen free community skills, plus guides and courses on writing skills.
• mcpservers.org. Primarily an MCP server directory. Any skills-specific coverage on this site wasn't verifiable from a static fetch at the time of writing; treat it as an MCP resource first and check the live site directly if you're looking for skills specifically.

None of the independent sites above run a review pipeline comparable to Anthropic's plugin validation and safety screening. A skill from anthropics/skills or one installed through claude-plugins-official or claude-community has gone through Anthropic's process. A skill you pull from an index site has not, by that site's own admission in at least one case above. Read the SKILL.md before you run anything, especially if it ships a script.

How to actually submit or publish a Claude Skill

There's no separate "submit a skill" form, because Anthropic distributes skills as a payload inside plugins. If you want a skill to reach people beyond your own team, package it as a plugin and submit the plugin.

1. Package the skill inside a plugin. A plugin is a directory with a .claude-plugin/plugin.json manifest and a skills/ folder (it can also carry agents, hooks, and MCP servers). If you already have skills sitting in .claude/skills/, Anthropic's migration steps walk through converting that directory into a plugin structure without rewriting the skill content itself.
2. Validate locally. Run claude plugin validate ./your-plugin before submitting anything. This runs the same check the review pipeline runs. A clean pass prints "Validation passed"; warnings don't block submission unless you add --strict.
3. Submit for community review. Use one of two in-app forms: claude.ai/admin-settings/directory/submissions/plugins/new if you're an Owner on a Team or Enterprise organization, or platform.claude.com/plugins/submit if you're an individual author outside an org. Submissions go through automated safety screening plus the same validation check.
4. Wait for the catalog sync. Approved plugins get pinned to a specific commit SHA in the anthropics/claude-plugins-community catalog, and the public catalog syncs nightly. There's a real gap between "approved" and "installable," so check the community catalog by name if a user reports it's missing.
5. The official marketplace is a different, closed door. Getting into claude-plugins-official isn't something the submission forms control. Anthropic curates that list at its own discretion, and there's no public application process for it.
6. Or skip the review pipeline entirely. You can also just share a plugin (or a bare skill) as a Git repository and tell people to add it with /plugin marketplace add <your-repo>, or point them at a community index site directly. That route reaches fewer people by default but gives you full control over updates and doesn't wait on anyone's review queue.

FAQ

Is there an official Claude Skills Marketplace? Not as a standalone product. Skills distribute through Anthropic's two plugin marketplaces, claude-plugins-official (curated by Anthropic) and claude-community (third-party submissions that passed review), plus Anthropic's own anthropics/skills GitHub repo for examples. Independent sites like SkillsMP and AugmentClaude use "marketplace" in their own names but aren't affiliated with Anthropic.

What's the difference between a Claude Skill and a Claude Code plugin? A skill is one SKILL.md file plus optional supporting files: a single capability. A plugin is the distribution unit, a directory that can bundle one or more skills alongside agents, hooks, and MCP servers, plus the manifest Claude Code needs to install and version it. You write skills; you distribute them by wrapping them in a plugin.

Can I use a skill without going through any marketplace? Yes. Drop a SKILL.md file into .claude/skills/your-skill-name/ inside a project (or your personal skills directory) and Claude Code picks it up on the next session, no marketplace or plugin required. Marketplaces only matter once you want other people to install it.

Do the community skills sites vet what they list? Not by their own description. SkillsMP states directly that it indexes public GitHub files without certifying quality or safety. Treat any skill sourced outside Anthropic's own review pipeline (claude-plugins-official or an approved claude-community plugin) as unaudited, and read the SKILL.md and any bundled scripts before running them.

How long does community marketplace review take? Anthropic's documentation doesn't publish a fixed SLA. What it does say: the public catalog syncs nightly after approval, so there's a lag between "approved" and "shows up when a user searches for it." Run claude plugin validate locally first so you're not waiting on the queue to catch something you could have caught yourself.

Does AY Automate build custom Claude Skills for clients? Yes. Skill and plugin authoring is part of the Claude Code stacks we set up for agency and product teams, alongside MCP server selection and the rest of the agent configuration. If you want a skill built for an internal workflow rather than pulled from a public catalog, start with our Claude Code agency services, or see the companion best Claude Code plugins guide if you're picking a broader stack first.