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] - Search for skills interactively or by keyword
npx skills add <package> - Install a skill from GitHub or other sources
npx skills check - Check for skill updates
npx 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 popular options; install counts do not establish quality or task fit.
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]
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:
- Task fit and evidence — Inspect the actual instructions, license, dependencies and executable examples. Install counts are a discovery signal, not a quality gate; do not reject a well-tested niche skill solely for low popularity.
- 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-skills or ComposioHQ/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
1---2name: find-skills3description: >-4 Searches the open agent skills ecosystem (skills.sh, npx skills) and installs a matching skill5 for personal use. Use when the user asks to find a skill for X, is there a skill that can do Y,6 how to extend the agent with a capability, or to install or update skills. Not for deciding7 whether an external skill should join the shared studio repo (use market-skill-ingestion).8metadata:9 source: https://skillmd.com/skills/the-utopia-studio/find-skills10---1112# Find Skills1314This skill helps you discover and install skills from the open agent skills ecosystem.1516## When to Use This Skill1718Use this skill when the user:1920- Asks "how do I do X" where X might be a common task with an existing skill21- Says "find a skill for X" or "is there a skill for X"22- Asks "can you do X" where X is a specialized capability23- Expresses interest in extending agent capabilities24- Wants to search for tools, templates, or workflows25- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)2627## What is the Skills CLI?2829The 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.3031**Key commands:**3233- `npx skills find [query]` - Search for skills interactively or by keyword34- `npx skills add <package>` - Install a skill from GitHub or other sources35- `npx skills check` - Check for skill updates36- `npx skills update` - Update all installed skills3738**Browse skills at:** https://skills.sh/3940## How to Help Users Find Skills4142### Step 1: Understand What They Need4344When a user asks for help with something, identify:45461. The domain (e.g., React, testing, design, deployment)472. The specific task (e.g., writing tests, creating animations, reviewing PRs)483. Whether this is a common enough task that a skill likely exists4950### Step 2: Check the Leaderboard First5152Before running a CLI search, check the [skills.sh leaderboard](https://skills.sh/) to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the popular options; install counts do not establish quality or task fit.5354For example, top skills for web development include:55- `vercel-labs/agent-skills` — React, Next.js, web design (100K+ installs each)56- `anthropics/skills` — Frontend design, document processing (100K+ installs)5758### Step 3: Search for Skills5960If the leaderboard doesn't cover the user's need, run the find command:6162```bash63npx skills find [query]64```6566For example:6768- User asks "how do I make my React app faster?" → `npx skills find react performance`69- User asks "can you help me with PR reviews?" → `npx skills find pr review`70- User asks "I need to create a changelog" → `npx skills find changelog`7172### Step 4: Verify Quality Before Recommending7374**Do not recommend a skill based solely on search results.** Always verify:75761. **Task fit and evidence** — Inspect the actual instructions, license, dependencies and executable examples. Install counts are a discovery signal, not a quality gate; do not reject a well-tested niche skill solely for low popularity.772. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.783. **GitHub stars** — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.7980### Step 5: Present Options to the User8182When you find relevant skills, present them to the user with:83841. The skill name and what it does852. The install count and source863. The install command they can run874. A link to learn more at skills.sh8889Example response:9091```92I found a skill that might help! The "react-best-practices" skill provides93React and Next.js performance optimization guidelines from Vercel Engineering.94(185K installs)9596To install it:97npx skills add vercel-labs/agent-skills@react-best-practices9899Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices100```101102### Step 6: Offer to Install103104If the user wants to proceed, you can install the skill for them:105106```bash107npx skills add <owner/repo@skill> -g -y108```109110The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.111112## Common Skill Categories113114When searching, consider these common categories:115116| Category | Example Queries |117| --------------- | ---------------------------------------- |118| Web Development | react, nextjs, typescript, css, tailwind |119| Testing | testing, jest, playwright, e2e |120| DevOps | deploy, docker, kubernetes, ci-cd |121| Documentation | docs, readme, changelog, api-docs |122| Code Quality | review, lint, refactor, best-practices |123| Design | ui, ux, design-system, accessibility |124| Productivity | workflow, automation, git |125126## Tips for Effective Searches1271281. **Use specific keywords**: "react testing" is better than just "testing"1292. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"1303. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`131132## When No Skills Are Found133134If no relevant skills exist:1351361. Acknowledge that no existing skill was found1372. Offer to help with the task directly using your general capabilities1383. Suggest the user could create their own skill with `npx skills init`139140Example:141142```143I searched for skills related to "xyz" but didn't find any matches.144I can still help you with this task directly! Would you like me to proceed?145146If this is something you do often, you could create your own skill:147npx skills init my-xyz-skill148```