Claude skills · directory
Claude skills marketplace: where skills actually live.
Free for 2 public pages.
There is no single official Claude skills marketplace as of June 2026. Anthropic ships built-in skills inside Claude and maintains a public skills repository on GitHub; everything else is shared through Claude Code plugin marketplaces and community collections. A skill itself is just a folder of instructions (a SKILL.md file plus optional scripts) that Claude loads on demand.
The format
What Claude skills are
A folder, not an app
A skill is a directory with one required file (SKILL.md) plus any helper scripts or templates. No build step, no install wizard.
Loaded on demand
Claude reads only each skill’s name and description up front. The full instructions load when a task actually matches, so skills don’t eat your context.
Works across surfaces
As of June 2026, the same skill format runs in the Claude apps, in Claude Code, and via the Claude API’s code-execution tooling, per Anthropic’s docs.
Yours to version
Because a skill is just files, it lives in Git, gets code-reviewed, and ships to your whole team like any other part of the repo.
Marketplace & directory
Is there a marketplace? Here’s the real directory
Built into Claude
Anthropic ships first-party skills with Claude itself. As of June 2026 that includes document skills for spreadsheets, slides, and PDFs. You toggle them in the app’s settings.
Anthropic’s skills repo on GitHub
The closest thing to an official directory: a public anthropics/skills repository with example and ready-to-use skills you can copy straight into your own setup.
Claude Code plugin marketplaces
Any Git repository can act as a marketplace for Claude Code plugins: bundles of skills, commands, and connectors. Teams and communities run their own.
Community collections
Curated lists and skill packs maintained by the community. Quality varies widely: read a skill’s SKILL.md and scripts before installing it, like any code.
Skills vs connectors
Skills are instructions. Connectors are tools.
Hands on
Install or create a skill
Pick your surface
In the Claude apps, skills are enabled in settings on paid plans. In Claude Code, skills are folders the agent discovers automatically.
Add the folder
For Claude Code, drop the skill into ~/.claude/skills/ (personal) or .claude/skills/ inside a repo (shared with the team via Git).
Write SKILL.md
YAML frontmatter with a name and a description, then plain-Markdown instructions. The description is the trigger: it’s what Claude reads to decide when to load the skill.
Test the trigger
Ask for a task that matches the description and confirm Claude loads the skill. If it doesn’t fire, sharpen the description: that line does the routing.
my-skill/
├── SKILL.md ← the only required file
└── scripts/ ← optional helpers
---
name: review-checklist
description: Run our code-review checklist. Use when
the user asks for a review or opens a PR.
---
# Review checklist
1. Security: inputs, auth, secrets.
2. Tests: every new path has one.
3. Naming: follow docs/conventions.md.Curated by job
The best skills for Claude Code, by job
Code review
Encode your team’s review checklist (security checks, naming rules, test-coverage expectations) so every review runs the same way, on every PR.
Testing
Teach Claude your house conventions: which framework, how fixtures are built, what coverage counts. Generated tests stop looking like a stranger wrote them.
Docs & changelogs
Carry your templates and tone in a skill so READMEs, changelogs, and release notes come out in your voice, not generic boilerplate.
Deploy & publish
The last mile: a publish skill that ships finished HTML as a live, tracked link via the Pagelive connector, password optional, noindex by default.
Example: a publish-to-web skill
Claude Code builds the HTML; this skill ships it. It pairs the instructions with Pagelive’s connector, so “publish this” becomes a live, branded Pagelive link, noindex by default, password optional, with opens, viewers, and time-on-page tracked. The connector is free for 2 public pages; passwords, full tracking and a custom domain come with Solo.
Set up the Pagelive connector →---
name: publish-to-web
description: Ship finished HTML as a live, tracked
link. Use when the user says "publish this",
"ship it", or "send it to the client".
---
When asked to publish:
1. Confirm the HTML is final.
2. Call Pagelive's publish_page tool:
title, html, optional password.
3. Reply with the live link. Stats come
later via get_page_stats.FAQ
Claude skills FAQ
Not a single one, as of June 2026. Anthropic ships built-in skills inside Claude and maintains a public skills repository on GitHub. Claude Code adds plugin marketplaces (any Git repository can serve as one), and the community curates collections. There’s no app-store-style storefront.
Start with Anthropic’s skills repository on GitHub, which holds example and ready-to-use skills. From there, look at plugin marketplaces published for Claude Code and at community-curated collections. Quality varies: read a skill before installing it.
Yes. As of June 2026, skills run in the Claude apps (on paid plans), in Claude Code, and through the Claude API’s code-execution tooling, per Anthropic’s docs. The same folder format works across all three.
A skill is instructions: a folder that tells Claude how to do something with the abilities it already has. A connector adds abilities: live tools that reach outside the chat, like Pagelive’s publish_page. They pair well: a skill can spell out when and how to use a connector’s tools.
Treat them like code, because they can bundle scripts Claude may run. Read SKILL.md and any included files first, prefer sources you trust, and keep shared skills in a repo where teammates can review changes.
Related: Claude MCP servers · Claude connectors