Agent skills took off fast. The open SKILL.md format landed in late 2025, and there are tens of thousands of public ones now. A skill is just a folder in a GitHub repo — trivial to share, and just as trivial to lose in the noise. So if you've built one, you list it: partly to get in front of the builders (and agents) browsing for skills, partly because each listing is a backlink that nudges your repo or site up in search. Both matter, and the same directories give you both.
I went and counted every place you can list one. Inside our product-directories dataset there are 20-odd directories built specifically for agent skills, and the spread between them is enormous — the two biggest pull ~3.8M and ~3.7M visits a month; most sit under 30K; a few are DR-4 pages spun up last week.
This is the full landscape, ranked by the two numbers that decide whether a listing is worth your time:
- Monthly visits — how many people actually pass through and might land on your skill. The number that decides whether a listing sends you anyone.
- Domain rating (DR, 0–100) — your listing links back to your repo, so a spot on a high-authority site is also a backlink for your own SEO. The secondary signal.
Both are third-party estimates — not 100% reliable, but directionally useful. But before you rush listing your skills, let's make sure you're well-prepared first.
How skills distribution works in 2026
A quick map, because where you submit follows from how the pieces fit. One asset feeds everything:
A public GitHub repo containing your skill — a folder with a SKILL.md (the open Agent Skills standard; YAML frontmatter + instructions). That's it. Anthropic created the format, released it as an open standard, and 20-plus agents now read it — Claude Code, Codex, Cursor, Gemini CLI, Copilot, Goose, OpenCode. Tag the repo with a topic like agent-skill / agent-skills / claude-skill so the crawlers can find it.
From that repo, three things pick you up:
-
npx skills(skills.sh) — the install tool basically everyone uses. It installs a skill straight from any GitHub repo:
npx skills add <author>/<repo>
Scroll any skills thread on Reddit and you'll see this exact line under every launch — npx skills add bitbonsai/mcpvault, npx skills add softaworks/agent-toolkit, and so on. skills.sh tracks installs, and through that tracking it discovers your skill and lists it on the site. Most builders know npx skills; most don't know it doubles as a directory or that the other directories exist at all.
-
ClawHub (clawhub.ai) — OpenClaw's official hub, with its own publish flow. You push a skill with the
clawhubCLI:
clawhub skill publish ./your-skill --owner <you> --version 1.0.0
It runs validation + automated security checks, then your skill lives at clawhub.ai/<owner>/<slug>. See the ClawHub publishing docs. By the numbers it's the single highest-authority destination on this whole list.
- The GitHub crawlers — a swarm of directories that index public skill repos automatically. The founder of skillsmp.com described it exactly: "Since Claude Skills launched, I've been collecting skills from GitHub and built a directory website." claude-plugins.dev: "began as an index of public Claude Code plugins on GitHub… we sort by GitHub stars and CLI installs." Get the repo right and you appear on these without lifting a finger.
There's also Anthropic's own curated Skills Directory (the partner skills from Notion, Figma, Canva et al.) — the closest thing to "official," but it's curated, not open-submit, so don't wait on it.
The shortlist, at a glance
| Directory | Monthly visits | DR | How you get in |
|---|---|---|---|
| clawhub.ai | 3.8M | 82 | clawhub skill publish |
| skills.sh | 3.7M | 78 |
npx skills (installs + lists) |
| smithery.ai | 446K | 75 | submit repo on site |
| aiagentsdirectory.com | 60K | 72 | submit · $49 dofollow |
| skillsmp.com | 931K | 61 | crawl-fed (GitHub) |
| lobehub.com | 1.4M | 56 | submit repo |
| mcpmarket.com | 1.4M | 52 | submit (has skills section) |
| allyourtech.ai | — | 37 | submit form |
| claudemarketplaces.com | 277K | 36 | crawl-fed (GitHub) |
| skillhub.club | 119K | 33 | upload SKILL.md |
| claude-plugins.dev | 26K | 30 | crawl-fed (GitHub) |
| claudeskills.info | 100K | 26 | submit (free) |
| clawtools.com | — | 25 | submit · paid $19 |
| skillsdirectory.com | 79K | 20 | submit form |
| tonsofskills.com | 2K | 20 | unclear (crawls GitHub) |
| agentskills.so | 156K | 19 | unclear (crawls skills.sh) |
| mcp.directory | 134K | 16 | submit repo |
| skillsplayground.com | 20K | 16 | submit + README badge |
| claudepluginhub.com | 168K | 13 | crawl-fed (GitHub) |
| claudeskillsmarket.com | 28K | 2 | crawl-fed |
A note on the numbers: monthly visits are SimilarWeb estimates and DR is Ahrefs' estimate — both directional, not gospel, treat them as "which league is this in." "Crawl-fed" = it indexes public GitHub repos, so the repo work above gets you in with no form.
The directories worth your time
Grouped the way I actually prioritized them. Do the GitHub repo once, publish to the Tier-1 hubs, and grab the free listings that are quick — don't sweat the low-traffic tail.
Tier 1 — do these first
The authority and the traffic. The top two are bigger than everything else combined; the rest pair high domain rating with real reach.
clawhub.ai — DR 82 · 3.8M visits/mo
OpenClaw's official skills + plugins hub, and the highest-authority destination on this list. It has a real publish flow (clawhub skill publish) with validation and security scanning baked in, so a listing here carries a trust signal the auto-aggregators can't. If your skill targets the OpenClaw crowd at all, this is the anchor submission.
skills.sh — DR 78 · 3.7M visits/mo
Not just a directory — it's the npx skills install tool nearly every skill launch on Reddit points people to, plus a Vercel-built browse site with preliminary security scanning. It lists you off install tracking, so the move is simple: put npx skills add <you>/<repo> in your README, get people installing, and you surface. The single most important name to be present on.
smithery.ai — DR 75 · 446K visits/mo
The same name MCP builders reach for, and it lists "MCP servers, agent skills, and AI agent tools" together. You submit on the site — not a passive crawl: MCP servers need a public URL, skills need a GitHub repo URL. High authority, real installs; worth the five minutes.
aiagentsdirectory.com — DR 72 · 60K visits/mo
The highest-authority directory with an open submission here — an AI-agent marketplace with a dedicated skills section, so your skill sits next to agents and tools in front of a buyer-minded audience, not only other builders. One catch: the free listing is nofollow. A faster review runs $19, and the dofollow backlink — the part that actually moves your SEO — costs $49. List free for the exposure; if you want the DR-72 link, you'll need to pay for it.
skillsmp.com — DR 61 · 931K visits/mo
Big traffic and skills-native. The founder built it by "collecting skills from GitHub" — and that's exactly how it works: it crawls agent skills straight from GitHub, so there's nothing to submit. Get your repo right (and the agent-skill topic on it) and you're in.
lobehub.com/skills — DR 56 · 1.4M visits/mo
One of the biggest traffic numbers on the list. LobeHub is an agent platform with both MCP and Agent Skills directories ("Claude, Codex & ChatGPT skills"), so the audience is people actively installing — not just browsing. Submission requires a GitHub repo; worth the effort for the reach alone.
mcpmarket.com — DR 52 · 1.4M visits/mo
Best known as an MCP marketplace, but it has a dedicated agent-skills section too — so that 1.4M-visit, DR-52 reach is genuinely in play for a skill, not just adjacent. Submit through its listing flow. A heavyweight worth doing.
Tier 2 — real reach, lower authority
Solid traffic, clean enough to submit, just lower DR. Worth doing once the Tier-1 set is handled.
claudemarketplaces.com — DR 36 · 277K visits/mo — Big traffic, crawls public GitHub repos, so you land automatically once your repo's in shape.
skillhub.club — DR 33 · 119K visits/mo — Strong traffic for the authority. Submission is a manual SKILL.md file upload. A few minutes of copy-paste for real reach.
claude-plugins.dev — DR 30 · 26K visits/mo — A GitHub-fed registry that crossed 45,000+ indexed public skills and ranks by stars + CLI installs. Cross-tool (it makes Claude skills OpenCode-compatible). Repo's right → you're already eligible.
claudeskills.info — DR 26 · 100K visits/mo — "Discover & download Claude Code skills," with a real community submission form. Free, solid mid-tier traffic, Claude-targeted.
claudepluginhub.com — DR 13 · 168K visits/mo — High visits for the authority, indexes public GitHub repos, Claude-Code-specific.
mcp.directory — DR 16 · 134K visits/mo — MCP-first but lists "3,000+ MCP servers & skills." You submit your repo. Decent traffic; a reasonable fill-out-the-set listing if you also touch MCP.
skillsdirectory.com — DR 20 · 79K visits/mo — Leans on a "secure, verified" angle and reviews submissions before listing. A clean submit form, free — just expect a security scan to flag things on the way (more on those scanners below).
Tier 3 — niche, emerging, or rough around the edges
Low traffic, friction, or a submission path I couldn't pin down. Grab the free ones if you're being completist; don't lose sleep over the rest.
skillsplayground.com — DR 16 · 20K — Lists your skill once you add their badge to your README, and gives you install tracking in return. Fair trade for the five minutes.
agentskills.so — DR 19 · 156K — Real traffic, but I couldn't find a clear way to submit — it appears to just crawl the skills.sh database, so getting onto skills.sh likely covers you here anyway.
clawtools.com — DR 25 and tonsofskills.com — DR 20 · 2K — clawtools is OpenClaw-flavored with a $19 one-time paid listing; tonsofskills is open-source and ships its own ccpi CLI, but how it actually lists a skill isn't clear — it looks like it just crawls GitHub. Both low-traffic.
The rest — allyourtech.ai (DR 37, free submit form, low traffic) and claudeskillsmarket.com (DR 2, 28K, crawl-fed). Completist territory; expect little today.
How to submit a skill well
The same moves pay off everywhere:
-
The public GitHub repo is the whole game. It's what
npx skillsinstalls from, what ClawHub publishes, and what every crawler reads. No repo, no distribution. Tag itagent-skillso the crawlers find it. -
Write the
descriptionfor a model and a skim-reading human. The agent loads only your skill'sname+descriptionat startup (progressive disclosure) and uses that to decide whether to activate it — and most directories show the same text verbatim. Lead with the capability and the trigger ("use when…"). It's worth rewriting more times than the skill body itself. -
Put
npx skills add <you>/<repo>at the top of your README. It's the install path people expect, and the installs feed skills.sh's listing. - Hit the two anchors + the high-traffic submit forms first (ClawHub, skills.sh, then smithery, aiagentsdirectory, lobehub), then let the GitHub crawlers do the long tail.
- Brace for the security scanners. ClawHub, skills.sh, and skillsdirectory run an automated security scan on every submission. It's there to protect installers — skills execute shell commands, and some have genuinely harvested API keys from thousands of users. For you, the creator, it's mostly noise: the scanners are over-cautious and will throw a red flag on a perfectly clean skill — a network call, a file write. It's a flag, not a rejection — your listing still goes up — so don't read the first warning as a verdict; more often than not it isn't about anything real.
What builders actually say
Personally, I've had the most frustration fighting security audit scanners on skills.sh — those are very cautious and run on their own schedule, so speed of iteration here is literally weeks.
My advice is to use your own agent to audit your skill and flag anything that could read as potentially leaking private data or encouraging remote prompt injection. These are two major categories where getting green lights takes a few rounds.
I've also pulled a few hundred Reddit threads on skills while writing this — partly to sanity-check the list, partly because the builders living in this space describe how it works better than any doc. A few worth reading yourself:
"How do you find and share Claude Skills? Is there anything like a proper registry yet? … There's a bunch of places — you can look at skills.sh, which even has preliminary security scanning. Claude Code has its own marketplace too."
— r/claudeskills — "Is there anything like a proper registry yet?""Since Claude Skills launched, I've been collecting skills from GitHub and built a directory website. It now has 2300+ skills indexed."
— r/ClaudeAI — the skillsmp.com founder"claude-plugins.dev began as an index of public Claude Code plugins on GitHub. When Anthropic launched skills, we expanded the registry — now 45,000+ public skills, sorted by GitHub stars and CLI installs."
— r/opencodeCLI — claude-plugins.dev
FAQ
Where's the one official place to publish a skill?
There isn't a single global registry — but there are a few well-known hubs that cover most of it. Your public GitHub repo (a SKILL.md folder, the open agentskills.io standard) is the source of truth; npx skills (skills.sh) is the de-facto install tool and the highest-traffic directory; ClawHub is OpenClaw's official hub and the highest-authority listing. Anthropic also ships a curated first-party Skills Directory. Cover the GitHub repo + those two hubs and the crawlers handle the long tail.
What's the fastest way to make my skill installable by anyone?
Push it to a public GitHub repo as a SKILL.md folder, then anyone can run npx skills add <you>/<repo> — or, for the Claude Code plugin path, /plugin marketplace add <you>/<repo>. No upload, no approval.
Do I have to submit to all 20+ directories?
No. Publish to ClawHub, get onto skills.sh, do the GitHub repo so the crawlers pick you up, and PR the curated lists if you've got five minutes. Twenty manual submissions for twenty DR-9 backlinks isn't worth your afternoon.
Are the paid placements worth it?
Only if you're long-term investing in SEO/dofollow backlinks. Most directories that actually send traffic have a free path to the listing.
What's the single most important thing to get right?
The skill's description and your README. The description is what the agent reads to decide whether to load your skill (progressive disclosure) and what most directories display; the README is what the crawlers lift and what a human judges in two seconds. Lead with the capability and the use case.
Also ship MCP servers? There's a companion guide to the best MCP server directories built the same way.
Good luck 🚀
Getting your skills used in the wild is pretty exciting! I hope this guide helps you get discovered.
Anything I missed? Got your own insights with skills distribution? Please share in comments!
Top comments (1)
I personally found the security scanners on skills.sh to be the biggest hurdle. Has anyone found a reliable way for getting green lights without weeks of waiting for rescan?