\r \r

Find Skills\r

\r This skill helps you discover and install skills from the open agent skills ecosystem.\r \r

When to Use This Skill\r

\r Use this skill when the user:\r \r

• Asks "how do I do X" where X might be a common task with an existing skill\r
• Says "find a skill for X" or "is there a skill for X"\r
• Asks "can you do X" where X is a specialized capability\r
• Expresses interest in extending agent capabilities\r
• Wants to search for tools, templates, or workflows\r
• Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)\r \r

What is the Skills CLI?\r

\r 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.\r \r Key commands:\r \r

• npx skills find [query] - Search for skills interactively or by keyword\r
• npx skills add \x3Cpackage> - Install a skill from GitHub or other sources\r
• npx skills check - Check for skill updates\r
• npx skills update - Update all installed skills\r \r Browse skills at: https://skills.sh/\r \r

How to Help Users Find Skills\r

\r

Step 1: Understand What They Need\r

\r When a user asks for help with something, identify:\r \r

1. The domain (e.g., React, testing, design, deployment)\r
2. The specific task (e.g., writing tests, creating animations, reviewing PRs)\r
3. Whether this is a common enough task that a skill likely exists\r \r

Step 2: Check the Leaderboard First\r

\r 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.\r \r For example, top skills for web development include:\r

• vercel-labs/agent-skills — React, Next.js, web design (100K+ installs each)\r
• anthropics/skills — Frontend design, document processing (100K+ installs)\r \r

Step 3: Search for Skills\r

\r If the leaderboard doesn't cover the user's need, run the find command:\r \r

npx skills find [query]\r
```\r
\r
For example:\r
\r
- User asks "how do I make my React app faster?" → `npx skills find react performance`\r
- User asks "can you help me with PR reviews?" → `npx skills find pr review`\r
- User asks "I need to create a changelog" → `npx skills find changelog`\r
\r
### Step 4: Verify Quality Before Recommending\r
\r
**Do not recommend a skill based solely on search results.** Always verify:\r
\r
1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100.\r
2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.\r
3. **GitHub stars** — Check the source repository. A skill from a repo with \x3C100 stars should be treated with skepticism.\r
\r
### Step 5: Present Options to the User\r
\r
When you find relevant skills, present them to the user with:\r
\r
1. The skill name and what it does\r
2. The install count and source\r
3. The install command they can run\r
4. A link to learn more at skills.sh\r
\r
Example response:\r
\r
```\r
I found a skill that might help! The "react-best-practices" skill provides\r
React and Next.js performance optimization guidelines from Vercel Engineering.\r
(185K installs)\r
\r
To install it:\r
npx skills add vercel-labs/agent-skills@react-best-practices\r
\r
Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices\r
```\r
\r
### Step 6: Offer to Install\r
\r
If the user wants to proceed, you can install the skill for them:\r
\r
```bash\r
npx skills add \x3Cowner/repo@skill> -g -y\r
```\r
\r
The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.\r
\r
## Common Skill Categories\r
\r
When searching, consider these common categories:\r
\r
| Category        | Example Queries                          |\r
| --------------- | ---------------------------------------- |\r
| Web Development | react, nextjs, typescript, css, tailwind |\r
| Testing         | testing, jest, playwright, e2e           |\r
| DevOps          | deploy, docker, kubernetes, ci-cd        |\r
| Documentation   | docs, readme, changelog, api-docs        |\r
| Code Quality    | review, lint, refactor, best-practices   |\r
| Design          | ui, ux, design-system, accessibility     |\r
| Productivity    | workflow, automation, git                |\r
\r
## Tips for Effective Searches\r
\r
1. **Use specific keywords**: "react testing" is better than just "testing"\r
2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"\r
3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`\r
\r
## When No Skills Are Found\r
\r
If no relevant skills exist:\r
\r
1. Acknowledge that no existing skill was found\r
2. Offer to help with the task directly using your general capabilities\r
3. Suggest the user could create their own skill with `npx skills init`\r
\r
Example:\r
\r
```\r
I searched for skills related to "xyz" but didn't find any matches.\r
I can still help you with this task directly! Would you like me to proceed?\r
\r
If this is something you do often, you could create your own skill:\r
npx skills init my-xyz-skill\r
```\r