skills.sh calls itself “The Agent Skills Directory” and “The Open Agent Skills Ecosystem” — a search and discovery layer for the reusable capability folders that coding agents load on demand. It is made by Vercel, and the site states that the directory itself is open source on GitHub.
The useful way to think about it: skills live in ordinary GitHub repositories, and skills.sh is an index over them with install counts attached. It does not host the skills.
What the directory gives you that a GitHub search does not
Three things, in descending order of usefulness.
Install counts and ranking. The leaderboard sorts by installs, with All Time, Trending (24h) and Hot views. For a format this young, that is the closest thing to a signal of what people actually keep using, as opposed to what got starred once.
Topic and agent filters. Skills are browsable by topic — React, Next.js, Testing among them — and by agent. The agent list is long: Claude Code, Cursor, Codex, GitHub Copilot, Windsurf, Gemini, Cline, AMP, Antigravity, OpenClaw, Droid, Goose, Kilo, Kiro CLI, Nous Research, OpenCode, Roo, Trae, VS Code and Zed. Twenty hosts for one format is a genuine sign that the skill folder has settled as a shared convention rather than a single vendor’s idea.
Packs and Official sections. Grouped bundles and a vendor-published tier, which is how you find the Anthropic or Vercel sets without sifting.
Installing from it
Skills are addressed by GitHub-style owner/repo paths, and the site shows an install command in the form:
npx skills add <owner/repo>That is a thin wrapper around fetching a repository’s skill folders into your agent’s skills directory, which is why the same command works across so many hosts — they all read skills from a directory on disk. Some tools ship their agent integration this way: Open Code Review installs its delegation-mode reviewer with npx skills add alibaba/open-code-review --skill open-code-review-delegate.
The part the site does not answer
This is where a directory needs scrutiny rather than enthusiasm. The site has an “Official” section and a “Security audits” section, both of which imply vetting. Neither explains the process: what qualifies a skill as official, who performs an audit, against what criteria, or how often. The site also links Terms and Privacy pages but names no licence for the listed skills themselves — and it could not, since each listed repository carries its own.
That matters more for skills than for most package types. A skill is instructions that your agent will follow, often with tool access, inside your repository. Installing one is closer to granting an untrusted contributor commit-adjacent influence than to adding a leaf dependency. The practical consequence: read the SKILL.md before you install, treat install count as popularity rather than safety, and check the licence in the source repository rather than assuming the directory implies one.
There is also a question the leaderboard cannot answer — whether a high-install skill is good or merely early. Install counts accumulate, and a format this new has no decay signal.
Worth using for
Finding out what exists. The honest value of skills.sh is that it turns a scattered convention into something browsable, and the per-agent filtering saves real time if you are not on Claude Code. Use it to discover and compare, then vet the actual repository before letting anything into your agent’s directory.
