find-skills
- Use it when:
- You ask "is there a skill for X?" or "how do I do X?".
- It does:
- Looks up the skills.sh leaderboard and searches with the npx skills CLI.
- You get:
- A few vetted skills, each with its install count, source and install command.
- Needs:
- Node.js, for npx skills.
TL;DR
It turns the agent into a scout for the open skills ecosystem. When you ask how to do something, the agent first checks the skills.sh leaderboard for a well-known skill, then searches with npx skills find using specific keywords. Before recommending anything it vets it: the install count, whether the publisher is a known source, and the repo's GitHub stars, with caution under 100 installs or stars. It presents each option with what it does, its numbers, the install command and a link, and can install the one you pick. If nothing fits, it says so, offers to help directly, and suggests writing your own skill with npx skills init.
Summarizes the skill at a80e4c9.
npx skills add https://github.com/vercel-labs/skills --skill find-skills skills.sh pageSource on GitHubAll skills from vercel-labs/skills
- Total Downloads
- 4,269,512 on skills.sh, Nov 9, 2026
- Repo stars
- 38,643 vercel-labs/skills
- First seen
- Jan 26, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 105,144 |
| Sep 28 | 103,601 |
| Oct 5 | 107,199 |
| Oct 12 | 110,524 |
| Oct 19 | 121,189 |
| Oct 26 | 121,665 |
| Nov 2 | 115,285 |
| Nov 9 | 110,096 |
| Category |
Find, write, vet and route to other skills. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
Operates a CLI, API, app or bundled script to get something done. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
A specific command-line tool or desktop app must be installed, such as gh, agent-browser, LibreOffice, Obsidian or a vendor CLI. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics |
SKILL.md
From vercel-labs/skills at a80e4c9. Checked daily, last changed Oct 20, 2026.
Frontmatter
name: find-skills
description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.Find Skills
This skill helps you discover and install skills from the open agent skills ecosystem.
When to Use This Skill
Use this skill when the user:
- Asks "how do I do X" where X might be a common task with an existing skill
- Says "find a skill for X" or "is there a skill for X"
- Asks "can you do X" where X is a specialized capability
- Expresses interest in extending agent capabilities
- Wants to search for tools, templates, or workflows
- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
What is the Skills CLI?
The Skills CLI (npx skills) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
Key commands:
npx skills find [query] [--owner <owner>]- Search for skills interactively or by keyword, optionally scoped to a GitHub ownernpx skills add <package>- Install a skill from GitHub or other sourcesnpx skills update- Update all installed skills
Browse skills at: https://skills.sh/
How to Help Users Find Skills
Step 1: Understand What They Need
When a user asks for help with something, identify:
- The domain (e.g., React, testing, design, deployment)
- The specific task (e.g., writing tests, creating animations, reviewing PRs)
- Whether this is a common enough task that a skill likely exists
Step 2: Check the Leaderboard First
Before running a CLI search, check the skills.sh leaderboard to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the most popular and battle-tested options.
For example, top skills for web development include:
vercel-labs/agent-skills— React, Next.js, web design (100K+ installs each)anthropics/skills— Frontend design, document processing (100K+ installs)
Step 3: Search for Skills
If the leaderboard doesn't cover the user's need, run the find command:
npx skills find [query] [--owner <owner>]
For example:
- User asks "how do I make my React app faster?" →
npx skills find react performance - User asks "can you help me with PR reviews?" →
npx skills find pr review - User asks "I need to create a changelog" →
npx skills find changelog
Step 4: Verify Quality Before Recommending
Do not recommend a skill based solely on search results. Always verify:
- Install count — Prefer skills with 1K+ installs. Be cautious with anything under 100.
- Source reputation — Official sources (
vercel-labs,anthropics,microsoft) are more trustworthy than unknown authors. - GitHub stars — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.
Step 5: Present Options to the User
When you find relevant skills, present them to the user with:
- The skill name and what it does
- The install count and source
- The install command they can run
- A link to learn more at skills.sh
Example response:
I found a skill that might help! The "react-best-practices" skill provides
React and Next.js performance optimization guidelines from Vercel Engineering.
(185K installs)
To install it:
npx skills add vercel-labs/agent-skills@react-best-practices
Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
Step 6: Offer to Install
If the user wants to proceed, you can install the skill for them:
npx skills add <owner/repo@skill> -g -y
The -g flag installs globally (user-level) and -y skips confirmation prompts.
Common Skill Categories
When searching, consider these common categories:
| Category | Example Queries |
|---|---|
| Web Development | react, nextjs, typescript, css, tailwind |
| Testing | testing, jest, playwright, e2e |
| DevOps | deploy, docker, kubernetes, ci-cd |
| Documentation | docs, readme, changelog, api-docs |
| Code Quality | review, lint, refactor, best-practices |
| Design | ui, ux, design-system, accessibility |
| Productivity | workflow, automation, git |
Tips for Effective Searches
- Use specific keywords: "react testing" is better than just "testing"
- Try alternative terms: If "deploy" doesn't work, try "deployment" or "ci-cd"
- Check popular sources: Many skills come from
vercel-labs/agent-skillsorComposioHQ/awesome-claude-skills
When No Skills Are Found
If no relevant skills exist:
- Acknowledge that no existing skill was found
- Offer to help with the task directly using your general capabilities
- Suggest the user could create their own skill with
npx skills init
Example:
I searched for skills related to "xyz" but didn't find any matches.
I can still help you with this task directly! Would you like me to proceed?
If this is something you do often, you could create your own skill:
npx skills init my-xyz-skill