3 -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.
8 -This skill helps you discover and install skills from the open agent skills ecosystem.
10 -##
When to Use This Skill 12 -Use this skill when the user:
14 -- Asks "how do I do X" where X might be a common task with an existing skill
15 -- Says "find a skill for X" or "is there a skill for X"
16 -- Asks "can you do X" where X is a specialized capability
17 -- Expresses interest in extending agent capabilities
18 -- Wants to search for tools, templates, or workflows
19 -- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
21 -##
What is the Skills CLI? 23 -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.
27 -- `npx skills find [query] [--owner <owner>]` - Search for skills interactively or by keyword, optionally scoped to a GitHub owner
28 -- `npx skills add <package>` - Install a skill from GitHub or other sources
29 -- `npx skills check` - Check for skill updates
30 -- `npx skills update` - Update all installed skills
32 -**Browse skills at:** https://skills.sh/
34 -## How to Help Users Find Skills
36 -###
Step 1: Understand What They Need 38 -When a user asks for help with something, identify:
40 -1. The domain (e.g., React, testing, design, deployment)
41 -2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
42 -3. Whether this is a common enough task that a skill likely exists
44 -###
Step 2: Check the Leaderboard First 46 -Before 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 most popular and battle-tested options.
48 -For example, top skills for web development include:
50 -- `vercel-labs/agent-skills` — React, Next.js, web design (100K+ installs each)
51 -- `anthropics/skills` — Frontend design, document processing (100K+ installs)
53 -###
Step 3: Search for Skills 55 -If the leaderboard doesn't cover the user's need, run the find command:
58 -npx skills find
[query
] [-
-owner <owner>
] 63 -- User asks "how do I make my React app faster?" → `npx skills find react performance`
64 -- User asks "can you help me with PR reviews?" → `npx skills find pr review`
65 -- User asks "I need to create a changelog" → `npx skills find changelog`
67 -###
Step 4: Verify Quality Before Recommending 69 -**Do not recommend a skill based solely on search results.** Always verify:
71 -1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100.
72 -2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.
73 -3. **GitHub stars** — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.
75 -###
Step 5: Present Options to the User 77 -When you find relevant skills, present them to the user with:
79 -1. The skill name and what it does
80 -2. The install count and source
81 -3. The install command they can run
82 -4. A link to learn more at skills.sh
87 -I found a skill that might help! The "react-best-practices" skill provides
88 -React and Next.js performance optimization guidelines from Vercel Engineering.
92 -npx skills add vercel-labs/agent-skills@react-best-practices
94 -Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
97 -###
Step 6: Offer to Install 99 -If the user wants to proceed, you can install the skill for them:
102 -npx skills add
<owner/repo@skill
> -g -y
105 -The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
107 -##
Common Skill Categories 109 -When searching, consider these common categories:
111 -| Category | Example Queries |
112 -| --------------- | ---------------------------------------- |
113 -| Web Development | react, nextjs, typescript, css, tailwind |
114 -| Testing | testing, jest, playwright, e2e |
115 -| DevOps | deploy, docker, kubernetes, ci-cd |
116 -| Documentation | docs, readme, changelog, api-docs |
117 -| Code Quality | review, lint, refactor, best-practices |
118 -| Design | ui, ux, design-system, accessibility |
119 -| Productivity | workflow, automation, git |
121 -##
Tips for Effective Searches 123 -1. **Use specific keywords**: "react testing" is better than just "testing"
124 -2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
125 -3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
127 -##
When No Skills Are Found 129 -If no relevant skills exist:
131 -1. Acknowledge that no existing skill was found
132 -2. Offer to help with the task directly using your general capabilities
133 -3. Suggest the user could create their own skill with `npx skills init`
138 -I searched for skills related to "xyz" but didn't find any matches.
139 -I can still help you with this task directly! Would you like me to proceed?
141 -If this is something you do often, you could create your own skill:
142 -npx skills init my-xyz-skill