Vercel Labs / find-skills
How do you find a skill that already does what you need?
Search before you write. Most of what people build already exists.
What to remember
- Search first. The duplicate you avoid writing is the whole return.
- The CLI supports many agents, not only Claude Code.
- Discovery is not endorsement. Read what you install.
- Directory listings age. Check the source repository's activity before adopting.
01What it changes in practice
The skill ecosystem is spread across repositories, marketplaces and directories, so the practical failure is not lack of skills but not knowing they exist. Search from inside the agent removes the browsing step entirely.
It also changes the default instinct. Once discovery is one command away, checking becomes cheaper than writing, which is the correct order.
02Where it disappoints
A directory ranks by popularity and recency, not by whether a skill is right for you, and popularity is a poor proxy for quality in a young ecosystem.
Security matters here more than anywhere else in this catalogue: installing a skill means giving instructions to an agent that can run commands, so read the source first.
Install and first run
- Install with the skills CLI from vercel-labs, published under MIT.
- Search for the task in plain words before writing anything yourself.
- Read the source of anything you install, because a skill runs with your agent's permissions.
Questions people actually ask
- What is the skills CLI?
- A command line tool from Vercel Labs for finding and installing agent skills, supporting many agents rather than one.
- Is everything in the directory safe?
- No. Listing is not review. Read the source of any skill before installing it.
- Why install this first?
- Because it stops you writing a skill that already exists, which is the most common waste in this ecosystem.
Sources
Machine readable versions of this page