Claude Skills Marketplace 2026: Where to Find, Install, and Build Skills

The Claude Skills marketplace is the loose ecosystem of catalogs, GitHub repos, and plugin marketplaces where developers find, install, and share Claude Skills, the bundled instruction packs that Claude Code, Claude Plugins, and the Anthropic API can load on demand. There is no single official storefront the way the App Store is one storefront. Instead, there is the official anthropic/skills repo, the Claude Code plugin marketplace primitive in the docs, a fast-growing list of community catalogs like SkillsMP and claudemarketplaces.com, and thousands of skills published as their own GitHub repos with a SKILL.md file. This guide unpacks how the Claude Skills marketplace actually works in 2026, which 12 Skills are pulling the most weight in real production work, how to install them in Claude Code, and how to publish your own. If you are building a real product on top of Claude Skills, the last section shows how Totalum pairs with a Skills-driven agent loop to turn that loop into a deployed app with auth, a database, and a custom domain.

Quick Answer

• The "Claude Skills marketplace" is not one site. It is the union of the official anthropic/skills repo, Claude Code's /plugin marketplace primitive, third-party catalogs (SkillsMP, claudemarketplaces.com, claudeskillsmarket.com), and the long tail of one-off GitHub repos with a SKILL.md.
• A Claude Skill is a folder containing a SKILL.md file plus optional supporting files. Claude loads it when the task matches its description.
• You install Skills three ways: drop them into ~/.claude/skills/, add a plugin marketplace via /plugin marketplace add, or upload skill bundles to the Anthropic API via the Skills tool.
• The 12 Skills with the most production leverage in 2026 are document creation (docx, pdf, pptx, xlsx), webapp testing, brand guidelines, slack-formatter, skill-creator, mcp-builder, artifacts-builder, and the official skill-creator from Anthropic.
• Skills handle reasoning. They do not handle hosting, payments, or a database. To ship a real product around a Skills-driven agent, you pair Claude Skills with a builder layer like Totalum that gives the agent a full Next.js app with auth, storage, and a custom domain. Try it free at totalum.app.

What a Claude Skill actually is

A Skill is a self-contained folder of context that Claude loads when a task matches its description. The format is dead simple. You need a directory, a SKILL.md file with YAML frontmatter at the top, and any number of supporting files (scripts, templates, reference docs, examples). The frontmatter looks like this:

---
name: pdf-creator
description: Use this skill when the user asks to generate a PDF from structured data, a markdown document, or a template.
---

When Claude reads a folder of Skills, it scans the frontmatter, picks the Skill whose description best matches the current task, then injects the rest of the SKILL.md (and any files it explicitly opens) into the conversation. That is the entire trick. Skills are progressive disclosure: you load 50 Skills, Claude only consumes the tokens for the ones it actually uses on this turn.

This is the part that makes a marketplace useful. If installing a Skill is one folder, every team can package their patterns once and distribute them like an npm package. The marketplace question becomes: where do I find a Skill, and how do I trust it?

Where to find Claude Skills today (the four real sources)

The Claude Skills marketplace is fragmented across four kinds of places. Knowing the difference saves time and avoids dead ends.

1. The official anthropic/skills repository

Anthropic maintains a public repo at github.com/anthropics/skills with first-party Skills the company has tested. Today it ships document-creation Skills (docx, pdf, pptx, xlsx), brand guidelines, slack-formatter, skill-creator (the meta-skill that helps you write new Skills), and a small set of utility examples. These are the safest Skills to start with because they are maintained by Anthropic and the model has been tuned alongside them.

2. Claude Code plugin marketplaces (the closest thing to an official store)

Anthropic shipped Claude Code plugin marketplaces in early 2026. A "marketplace" is a Git repo with a .claude-plugin/marketplace.json file at the root and one folder per plugin. Each plugin can bundle Skills, agents, hooks, MCP servers, and LSP servers. You add a marketplace by running:

/plugin marketplace add github.com/some-org/some-marketplace
/plugin install pdf-creator@some-marketplace

The marketplace.json schema is documented at code.claude.com/docs/en/plugin-marketplaces. Any GitHub org can run a marketplace. This is the official primitive that all the third-party catalogs are wrapping.

3. Community catalogs and directories

Three independent catalogs index thousands of Skills and rank them, the way npm wraps the package registry:

• SkillsMP indexes 1.2M+ agent skills compatible with Claude Code, Codex CLI, and ChatGPT under the open SKILL.md format. Search, tags, install instructions.
• claudemarketplaces.com is a curated, community-voted directory of plugins, Skills, and MCP servers. Smaller catalog, more curation.
• claudeskillsmarket.com focuses on small business and agency use cases (writing, sales, ops Skills) rather than developer tooling.

These catalogs do not host Skills themselves. They index Skills hosted on GitHub. The actual install always comes from a Git URL.

4. The long tail of standalone GitHub repos

Most Skills live as a single repo with a SKILL.md at the root, no marketplace.json, no plugin packaging. You install them by cloning into ~/.claude/skills/ or by adding the parent repo as a marketplace if the author has packaged it. The Reddit r/ClaudeAI community has been collecting these. One community member maintains a directory of 2300+ such Skills.

For most teams, the practical workflow is: start with anthropic/skills, add one curated marketplace from claudemarketplaces.com for daily-driver Skills, then pull individual repos for specialized needs.

How a real "marketplace" actually works in 2026

In April 2026, Anthropic landed the plugin-marketplace primitive in Claude Code as a stable feature. A marketplace is a Git repository with a specific structure. The minimal layout looks like this:

my-marketplace/
  .claude-plugin/
    marketplace.json
  plugins/
    pdf-creator/
      SKILL.md
      scripts/
        render.py
    docx-creator/
      SKILL.md

The marketplace.json file lists every plugin in the repo, the path, the version, and (optionally) the source if the plugin lives in another repo. Once a user runs /plugin marketplace add , Claude Code clones it, validates the schema, and shows the catalog. Installing a plugin pulls its files into the user's ~/.claude/plugins/ directory. Updating uses standard Git operations.

This means the practical "Claude Skills marketplace" is whatever marketplace repos a team trusts plus the official anthropic/skills repo. There is no centralized server because the model lives client-side in Claude Code. Centralization is a layer that community catalogs add on top.

Top 12 Claude Skills worth installing in 2026

These twelve are pulled from the official anthropic/skills repo, top community catalogs, and the Skills that appear most often in production agent loops we have audited. Each entry lists the source, what it does, and why we keep it in the daily-driver kit.

Skill	Source	What it does	Why it earns its slot
docx-creator	anthropic/skills	Generates Word documents from structured input	Most-shipped Skill in business workflows; replaces hand-rolled templating
pdf-creator	anthropic/skills	Renders PDFs from markdown or templates	Reliable headless PDF without a separate microservice
pptx-creator	anthropic/skills	Builds PowerPoint decks from outlines	Cuts a 2-hour slide deck to 8 minutes
xlsx-creator	anthropic/skills	Creates Excel workbooks with formulas	Replaces brittle "give me a CSV and I'll format it" loops
skill-creator	anthropic/skills	Meta-skill that writes new Skills	Bootstraps the next Skill in 5 minutes; non-negotiable for any team writing Skills
brand-guidelines	anthropic/skills	Enforces brand voice and visual rules	Keeps every output on-brand across long-running agent loops
slack-formatter	anthropic/skills	Formats outputs for Slack mrkdwn	Fixes the "wall of markdown" problem when piping agent output into Slack
webapp-testing	anthropic/skills	Runs Playwright-style test loops	The fastest way to plug Claude Code into a real E2E test step
artifacts-builder	community	Generates Claude Artifacts (HTML, React, charts)	Heaviest hitter for "show me a working prototype" requests
mcp-builder	community	Scaffolds new MCP servers	Pairs with the marketplace pattern: the Skill that builds the Skill's neighbors
n8n-creator	community	Drafts n8n workflow JSON	Bridges the agent to the no-code automation layer most teams already run
code-reviewer	community	Strict PR review with project conventions	Catches the regressions a junior reviewer would miss; the highest-saved-hours Skill in agency workflows

The pattern: Anthropic's first-party Skills are mostly document and formatting tooling. Community Skills handle the "scaffold the next thing" jobs (MCP servers, n8n workflows, full review loops). A starter kit of 8 to 12 Skills covers ~80% of real agent workflows.

How to install Claude Skills (three patterns)

There are exactly three install patterns in 2026. Pick by where the Skill lives.

Pattern A: drop folder into ~/.claude/skills/

For single-Skill repos that do not ship a marketplace.json:

cd ~/.claude/skills
git clone https://github.com/some-author/cool-skill.git

Restart Claude Code. Type /skills to confirm the Skill is loaded. This is the cleanest path for one-off Skills.

Pattern B: add a plugin marketplace

For marketplaces (the official Anthropic primitive):

/plugin marketplace add github.com/anthropics/skills
/plugin install docx-creator@anthropics

This works for any repo that ships a marketplace.json. You can have multiple marketplaces installed at once. The lockfile lives in ~/.claude/marketplaces.lock.json.

Pattern C: Anthropic API Skills tool

For programmatic use (you are calling claude.messages.create from Python or Node), pass a Skills bundle to the skills parameter on a request. The Skill is a base64-encoded zip; Anthropic loads it for that conversation only. This is how you wire a Skill into a production app without giving the user a CLI. We unpack the API pattern further in Claude Code Skills and Totalum, the parent post for the Skills cluster.

For teams already running an MCP loop, our Claude Code MCP tutorial walks through the install layer that sits below Skills in the same client.

Building your own Skill: the 7-step pattern

Once you have used a few Skills, your next move is to write one. The shortest path:

1. Install skill-creator from anthropic/skills. It is the meta-skill that drafts new Skills with you.
2. Pick one repetitive task your agent is doing today and write down the prompt you reuse for it.
3. Run /skills new in Claude Code with skill-creator loaded. It walks you through the YAML frontmatter and the body.
4. Add 2-3 worked examples to the SKILL.md. Example-driven Skills outperform purely descriptive ones because Claude pattern-matches on the examples.
5. Add a scripts/ folder if the Skill calls out to deterministic code (PDF rendering, image processing, API calls). Skills can shell out via the Bash tool.
6. Test on 5 real inputs before publishing. Skills look correct in isolation and break on the 6th input you did not anticipate.
7. Package and publish. Either commit it to your team's marketplace repo (with a marketplace.json entry) or push it as a standalone repo and submit to the community catalogs.

The Skills that move the needle in production are short (under 200 lines of SKILL.md), have explicit examples, and bundle scripts for any non-deterministic step.

How Claude Skills compose with a deployment-grade app builder

A Skills-driven agent is a great way to compose reasoning. It is not a way to ship a product. The skill answers "what should I do." It does not answer "where does this run when a customer hits it."

This is the part most marketplace posts skip. A real product around Claude Skills needs:

• An app shell (frontend + backend + database).
• Auth so customers can log in.
• File storage so the Skill's PDF/docx output is reachable.
• A custom domain, payments, and a hosting plan.
• A control panel so a non-engineer can edit data.

That is what Totalum does. Totalum is an AI app builder that creates a real, production Next.js project from a description, with database, auth, file storage, and hosting included from the first deploy. The agent integration is inverted from "your Claude Code writes code, then deploy somewhere." With Totalum, your Claude Code (or any agent) calls Totalum via MCP or REST API to create and maintain the full project itself. Skills handle the reasoning; Totalum materializes the app.

A common pattern in 2026 agent stacks:

1. A Claude Code session with 8-12 Skills loaded (docx, pdf, brand, code-reviewer, skill-creator, etc.).
2. The Totalum MCP attached as a tool. The agent uses it to spin up a Next.js project, add tables, generate UI pages, deploy.
3. The Skill produces the artifact (PDF, slide deck, generated component). The Totalum-built app exposes that artifact behind a customer-facing route.
4. The same agent can iterate on the deployed app the same day, because Totalum runs the project it built and serves the code editor and the data admin panel out of the box.

This pairing is why the Skills marketplace matters for builders, not just hobbyists: a Skill that took 30 minutes to write becomes a product the moment you wire it into a real app. We benchmark how this composes against other agent platforms in our AI agent platform 2026 guide, and against the wider field of coding agents in Best AI coding agents 2026. For the MCP server side of the same stack, see Best MCP servers 2026.

A worked example: "Generate Q3 board PDF" Skill on a real app

The clearest way to see Skills + Totalum compose is a small end-to-end example. Say you are building a finance dashboard for a portfolio company and the recurring ask is "give me a Q3 board PDF."

1. Write a board-pdf Skill. SKILL.md describes when to invoke it ("user asks for a quarterly board deck or PDF"). The body specifies the sections (Cover, KPIs, P&L, Risks, Next quarter). A scripts/render.py calls a PDF library.
2. Drop the Skill into your Claude Code marketplace. Anyone on the team can /plugin install board-pdf@yourorg.
3. Build the dashboard on Totalum. "Create a portfolio dashboard with companies, quarters, KPIs, and a Reports page." Totalum stands up the Next.js project, database tables, the admin panel.
4. Wire the Skill into the deployed app. From your Totalum project, add an API route that calls Claude with the board-pdf Skill enabled and the quarter's data inlined. Save the resulting PDF to the project's file storage.
5. Expose a "Generate board PDF" button on the Reports page. Customer clicks, your API route invokes the Skill, Totalum stores the PDF, the page shows a download link.

The Skill is reusable across customers. The Totalum app is the productized container. You ship in a day what would otherwise be a week of glue work.

FAQ

Is there an official Claude Skills marketplace?

There is no single official store. Anthropic ships the marketplace primitive in Claude Code (the /plugin marketplace add command and the marketplace.json schema) plus a first-party anthropic/skills repo. Third-party catalogs like SkillsMP and claudemarketplaces.com aggregate community Skills on top. In 2026, "the marketplace" is the union of these.

What is the difference between a Claude Skill and a Claude plugin?

A plugin is the packaging layer. A Skill is one type of content a plugin can ship. A plugin can bundle Skills, agents, hooks, MCP servers, and LSP servers in one install. A pure-Skill plugin contains a SKILL.md and supporting files only. For a deeper compare, see our parent post on Claude Code Skills.

Do Claude Skills work outside Claude Code?

Yes. The SKILL.md format is supported in Claude Code, in the Anthropic API via the Skills tool, and in some third-party clients that follow the open format (Codex CLI, certain ChatGPT custom-GPT setups via the SKILL.md adapter). The marketplace primitive is Claude Code-specific.

How do I trust a community Skill before installing it?

Read the SKILL.md and the scripts folder before installing. Pin to a specific commit if the Skill is critical. Run it against test inputs in a throwaway Claude Code session first. The catalogs (claudemarketplaces.com, SkillsMP) surface stars and downloads but do not vet code.

Can I sell Skills?

Yes. The plugin marketplace can point to a private Git URL with auth. Several community efforts (AgentPowers, paid marketplaces) are building monetized layers on top of the open format. The format itself is free and open.

How does this fit with a production app, not just a CLI?

Skills are loaded into the agent loop, not the runtime. A production app that uses a Skill calls Claude (via the API or via an agent like Claude Code) with that Skill enabled, then takes the Skill's output and writes it back into the app. Totalum's pairing pattern (agent calls Totalum via MCP to build the app, app calls Claude with Skills enabled to do reasoning) is the cleanest fit we have seen.

Ready to ship Skills as a real product?

A Skill is a great reasoning module. It is not a product. Pair your Skills with an app builder that gives you a real Next.js project, a database, auth, file storage, deployment, and a custom domain from the first prompt. Start free at totalum.app and connect Claude Code (or any agent) to Totalum via MCP so your Skills compose into a deployed app the same day.

If you are an agency or a SaaS founder building a Skills-driven product for clients, book a 30-minute call to see Totalum's API and MCP live and decide whether the embed path makes sense for your build.