The Free Skill That Searches Every Other Claude Skill For You
find-skills is a free skill from Vercel Labs that searches the public skills registry for you. One install command, then ask Claude whether a skill exists for the job. Read what it finds before you install it. Checked on 2026-10-26.
Too many skills to browse by hand
A skill is a saved set of instructions Claude loads when a job calls for it. So many are public that you cannot scroll the whole list. find-skills is a skill that searches the list for you.
It comes from Vercel Labs (github.com/vercel-labs/skills, MIT license). You ask Claude whether a skill exists for what you are doing. It searches the public skills registry at skills.sh, checks the install count and the source, and hands back the install command. On skills.sh it ranks first, with 4.1 million installs (checked 2026-10-26).
Before you start
- Claude Code — already installed and signed in. It needs a paid Claude plan.
- Node.js 22.20 or newer — the skills tool that installs and searches requires it. Run node -v to check.
- A terminal — one command installs it. Claude does the searching after that.
Install it
npx skills add vercel-labs/skills@find-skills -g -a claude-code -yThe flags do three jobs. -g installs it for you in every project, in ~/.claude/skills/find-skills. -a claude-code installs it for Claude Code only. -y skips the confirmation prompts. Drop the flags and the tool asks where to install instead.
If Claude Code was already open, type /reload-skills or restart it so it sees the new skill.
Ask for a skill
Say what you are trying to do:
is there a skill for reviewing pull requests?
find a skill for writing changelogs
how do I make my React app faster?These match the phrases in the skill's own trigger list. Specific words work better than general ones: "react testing" beats "testing".
You can also type /find-skills. Claude Code turns every installed skill into a slash command named after it, and find-skills does not opt out, so the command exists.
What happens next
Following the skill's own instructions, Claude:
- Checks the skills.sh leaderboard for a well-known skill in that area.
- Runs a keyword search with
npx skills findif the leaderboard has nothing. - Checks install count, source and GitHub stars before it recommends anything.
- Shows you the options with the install command and a skills.sh link, then offers to install.
You can run the same search yourself in any terminal:
npx skills find pdfIt prints each result as owner/repo@skill with an install count and a skills.sh link. On 2026-10-26 the top hit was anthropics/skills@pdf, with 217.1K installs.
Read it before you install it
Skills run with full permissions in your agent, and the tool prints that warning after every install. A skill is mostly a SKILL.md file of instructions, sometimes with scripts next to it. You can read it first.
- Open the SKILL.md. The skills.sh page for each skill shows it, and so does the GitHub repo.
- Use the checks find-skills uses itself. It prefers skills with 1K+ installs, treats anything under 100 with caution, trusts official sources (vercel-labs, anthropics, microsoft) over unknown authors, and treats a repo with fewer than 100 stars with skepticism.
- Read the audits. Skill pages on skills.sh show security audits. For find-skills on 2026-10-26, Gen Agent Trust Hub passed it, Socket passed it, and Snyk gave it a medium-risk warning. Snyk's reason is third-party content exposure: find-skills reads community-written skill descriptions, and a bad one could carry instructions meant for Claude.
When find-skills offers to install something, its install command uses -y, which skips the tool's confirmation prompts. Say yes after you have read the SKILL.md.
Keep your skills tidy
npx skills list
npx skills check
npx skills update
npx skills remove find-skillslist shows what is installed. check looks for updates, update applies them, and remove uninstalls a skill.
Three things that trip people up
- Typing find-skill — the name is plural: find-skills.
- Skipping the Node check — the tool needs Node 22.20 or newer. Run node -v before you install.
- Installing the first result — the top hit has the most installs. It may not fit your job, and it may not be the safest pick. Read before you say yes.
Frequently asked questions
- Is it free?
- Yes. The skills repo is MIT-licensed. You need a paid Claude plan for Claude Code itself.
- Is there a slash command?
- Yes. Claude Code makes every skill a slash command named after it, so /find-skills works, and so does asking in plain English.
- Does it only work with Claude?
- No. The skills tool supports Claude Code, Codex, Cursor, OpenCode and dozens of other agents. The command above targets Claude Code with
-a claude-code. - Does it need an account or an API key?
- No. The install and search commands above ran without either.
- Does the tool track me?
- It collects anonymous usage data. Set DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1 to turn that off.
- Will it install things without asking?
- It shows you its picks first and offers to install. Its install step skips the tool's own prompts, so read the SKILL.md before you agree.
Get it
- find-skills — skills.sh/vercel-labs/skills/find-skills (opens in a new tab)
- The skills tool — github.com/vercel-labs/skills (opens in a new tab)
- The directory — skills.sh (opens in a new tab)
Checked 2026-10-26 against github.com/vercel-labs/skills, skills.sh and code.claude.com/docs. We ran the install and a search. The /find-skills slash command comes from the Claude Code docs, not from a live session.