Find Skills
A Vercel skill that searches the open skills ecosystem when you ask how to do something that might already be packaged.
Skills
Who it’s for. People who already use an agent and want to know whether a skill exists before they write one. It is a search step, not a skill that does the job itself.
What it is
A useful starting point—not another unexplained bookmark.
Find Skills is for the moment you ask “how do I do this?” or “is there a skill for that?”. It teaches the agent to search skills.sh and the Skills CLI, then show you a candidate with an install command. You still read the skill before you trust it.
Who it is for
Use it when the missing piece might already exist.
- You
Ask for a capability
You say how to do X, find a skill for X, or that you wish the agent knew a domain such as testing, deployment, or design.
- The agent
Search, then show options
It names the domain and the task, checks the skills.sh leaderboard, then runs a keyword search if the leaderboard does not cover it.
- Not for
Doing the task by itself
Finding a React performance skill does not make your app faster. The installed skill is a separate package you still have to read.
How a search should go
Specific words, then a source you can name.
- 01
Name the domain and the task
“React performance” is a better query than “make it better”. Testing, deploy, docs, review, and design are the usual starting categories.
- 02
Look at popular skills first
The skill points at the skills.sh leaderboard before a CLI search. Well-known sources named there include vercel-labs and anthropics.
- 03
Search if the leaderboard misses
The documented command is npx skills find, with the query, and an optional owner when you want one publisher.
- 04
Check quality before you install
Prefer skills with many installs and a publisher you recognize. A search hit alone is not a recommendation. Read the skill file.
Useful for
When to use it
- Checking whether a repeated job already has a skill
- Installing a skill from a known publisher
- Avoiding a custom skill for a common task
What you will find
Inside the resource
- When the skill should trigger
- A search path through skills.sh and npx skills find
- A quality check before a recommendation
- The install command shape
Quick start
How I would use it
- 01
Say the job in plain words
Include the tool and the outcome, such as “review a pull request” or “write a changelog”.
- 02
Let the search return a short list
You want the skill name, what it does, where it comes from, and the install command. Not a dump of every match.
- 03
Open the skill before you add it
Install with npx skills add only after the description matches your job. Global install is a separate flag. Skip confirmation only when you already decided.
- 04
Write your own if nothing fits
The skill’s own fallback is to help with the task directly, then suggest npx skills init when you will repeat the job.
Ready?
Continue to GitHub · vercel-labs
Keep exploring
Where to go next
Next step
Want to use one of these in a real product?
Tell me the user problem. I will help you choose the resource and the safest first integration.