$npx -y skills add OpsinTech/opsintech-platform --skill find-skillsHelps 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 a
| 1 | # Find Skills |
| 2 | |
| 3 | This skill helps you discover and install skills from the open agent skills ecosystem. |
| 4 | |
| 5 | ## When to Use This Skill |
| 6 | |
| 7 | Use this skill when the user: |
| 8 | |
| 9 | - Asks "how do I do X" where X might be a common task with an existing skill |
| 10 | - Says "find a skill for X" or "is there a skill for X" |
| 11 | - Asks "can you do X" where X is a specialized capability |
| 12 | - Expresses interest in extending agent capabilities |
| 13 | - Wants to search for tools, templates, or workflows |
| 14 | - Mentions they wish they had help with a specific domain (design, testing, deployment, etc.) |
| 15 | |
| 16 | ## What is the Skills CLI? |
| 17 | |
| 18 | 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. |
| 19 | |
| 20 | **Key commands:** |
| 21 | |
| 22 | - `npx skills find [query]` - Search for skills interactively or by keyword |
| 23 | - `npx skills check` - Check for skill updates |
| 24 | - `npx skills update` - Update all installed skills |
| 25 | |
| 26 | **Browse skills at:** https://skills.sh/ |
| 27 | |
| 28 | ## How to Help Users Find Skills |
| 29 | |
| 30 | ### Step 1: Understand What They Need |
| 31 | |
| 32 | When a user asks for help with something, identify: |
| 33 | |
| 34 | 1. The domain (e.g., React, testing, design, deployment) |
| 35 | 2. The specific task (e.g., writing tests, creating animations, reviewing PRs) |
| 36 | 3. Whether this is a common enough task that a skill likely exists |
| 37 | |
| 38 | ### Step 2: Search for Skills |
| 39 | |
| 40 | Run the find command with a relevant query: |
| 41 | |
| 42 | ```bash |
| 43 | npx skills find [query] |
| 44 | ``` |
| 45 | |
| 46 | For example: |
| 47 | |
| 48 | - User asks "how do I make my React app faster?" → `npx skills find react performance` |
| 49 | - User asks "can you help me with PR reviews?" → `npx skills find pr review` |
| 50 | - User asks "I need to create a changelog" → `npx skills find changelog` |
| 51 | |
| 52 | The command will return results like: |
| 53 | |
| 54 | ``` |
| 55 | Install with bash /path/to/skill/scripts/install-skill.sh vercel-labs/agent-skills@vercel-react-best-practices |
| 56 | |
| 57 | vercel-labs/agent-skills@vercel-react-best-practices |
| 58 | └ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices |
| 59 | ``` |
| 60 | |
| 61 | ### Step 3: Present Options to the User |
| 62 | |
| 63 | When you find relevant skills, present them to the user with: |
| 64 | |
| 65 | 1. The skill name and what it does |
| 66 | 2. The install command they can run |
| 67 | 3. A link to learn more at skills.sh |
| 68 | |
| 69 | Example response: |
| 70 | |
| 71 | ``` |
| 72 | I found a skill that might help! The "vercel-react-best-practices" skill provides |
| 73 | React and Next.js performance optimization guidelines from Vercel Engineering. |
| 74 | |
| 75 | To install it: |
| 76 | bash /path/to/skill/scripts/install-skill.sh vercel-labs/agent-skills@vercel-react-best-practices |
| 77 | |
| 78 | Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices |
| 79 | ``` |
| 80 | |
| 81 | ### Step 4: Install the Skill |
| 82 | |
| 83 | If the user wants to proceed, use the `install-skill.sh` script to install the skill and automatically link it to the project: |
| 84 | |
| 85 | ```bash |
| 86 | bash /path/to/skill/scripts/install-skill.sh <owner/repo@skill-name> |
| 87 | ``` |
| 88 | |
| 89 | For example, if the user wants to install `vercel-react-best-practices`: |
| 90 | |
| 91 | ```bash |
| 92 | bash /path/to/skill/scripts/install-skill.sh vercel-labs/agent-skills@vercel-react-best-practices |
| 93 | ``` |
| 94 | |
| 95 | The script will install the skill globally to `skills/custom/` |
| 96 | |
| 97 | ## Common Skill Categories |
| 98 | |
| 99 | When searching, consider these common categories: |
| 100 | |
| 101 | | Category | Example Queries | |
| 102 | | --------------- | ---------------------------------------- | |
| 103 | | Web Development | react, nextjs, typescript, css, tailwind | |
| 104 | | Testing | testing, jest, playwright, e2e | |
| 105 | | DevOps | deploy, docker, kubernetes, ci-cd | |
| 106 | | Documentation | docs, readme, changelog, api-docs | |
| 107 | | Code Quality | review, lint, refactor, best-practices | |
| 108 | | Design | ui, ux, design-system, accessibility | |
| 109 | | Productivity | workflow, automation, git | |
| 110 | |
| 111 | ## Tips for Effective Searches |
| 112 | |
| 113 | 1. **Use specific keywords**: "react testing" is better than just "testing" |
| 114 | 2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd" |
| 115 | 3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills` |
| 116 | |
| 117 | ## When No Skills Are Found |
| 118 | |
| 119 | If no relevant skills exist: |
| 120 | |
| 121 | 1. Acknowledge that no existing skill was found |
| 122 | 2. Offer to help with the task directly using your general capabilities |
| 123 | 3. Suggest the user could create their own skill with `npx skills init` |
| 124 | |
| 125 | Example: |
| 126 | |
| 127 | ``` |
| 128 | I searched for skills related to "xyz" but didn't find any matches. |
| 129 | I can still help you with this task directly! Would you like me to proceed? |
| 130 | |
| 131 | If this is something you do often, you could create your own skill: |
| 132 | npx skills init my-xyz-skill |
| 133 | ``` |