97 lines
3.0 KiB
Markdown
97 lines
3.0 KiB
Markdown
---
|
|
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", or "is there a skill that can help with X".
|
|
---
|
|
|
|
# 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` - 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:
|
|
|
|
1. The domain (e.g., React, testing, design, deployment)
|
|
2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
|
|
3. Whether this is a common enough task that a skill likely exists
|
|
|
|
### Step 2: Search for Skills
|
|
|
|
Run the find command with a relevant query:
|
|
|
|
```bash
|
|
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 3: Present Recommendations
|
|
|
|
When you find relevant skills, present them to the user with:
|
|
|
|
1. The skill name and what it does
|
|
2. The installation command
|
|
3. A link to the skill's page
|
|
|
|
**Example response:**
|
|
|
|
> I found a skill that might help!
|
|
>
|
|
> **vercel-react-best-practices**
|
|
> Vercel's official React performance guidelines for AI agents.
|
|
>
|
|
> To install it:
|
|
> `npx skills add vercel-labs/agent-skills@vercel-react-best-practices`
|
|
>
|
|
> Learn more: <https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices>
|
|
|
|
If the user wants to proceed, you can install the skill for them:
|
|
|
|
```bash
|
|
npx skills add vercel-labs/agent-skills@vercel-react-best-practices
|
|
```
|
|
|
|
### Step 4: Verify Installation (Optional)
|
|
|
|
After installing, you can verify it was installed correctly:
|
|
|
|
```bash
|
|
npx skills list
|
|
```
|
|
|
|
## When No Skills Are Found
|
|
|
|
1. Try a broader search term
|
|
2. Check the [skills.sh](https://skills.sh/) website manually if you suspect a network issue
|
|
3. Suggest the user could create their own skill with `npx skills init`
|