Find Skills
This skill helps you discover and install skills from the open agent skills ecosystem.
安装目标规则(必须遵守)
- 安装 skill 前必须确认目标 agent 工具(如
trae/codex/cursor/claude-code),通过-a <agent>指定。 - 用户明确指定安装到哪个 agent 时,只装到该 agent 的 skills 目录。
- 用户未指定时,默认安装到当前对话所在的 agent(本 skill 运行在 Trae,就装到 Trae)。
- 禁止全局安装:不要使用
-g,不要写入~/.agents/skills等跨工具共享目录,避免重复安装与污染。
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] [--owner <owner>]- Search for skills interactively or by keyword, optionally scoped to a GitHub ownernpx skills add <owner/repo@skill> -a <agent> -y --copy- Install a skill to the specified agent(默认取当前对话所在 agent)npx skills update- Update 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 most popular and battle-tested options.
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] [--owner <owner>]
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:
- Install count — Prefer skills with 1K+ installs. Be cautious with anything under 100.
- 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 (当前对话在 Trae,默认装到 Trae;也可指定其他 agent):
npx skills add vercel-labs/agent-skills@react-best-practices -a trae -y --copy
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> -a <agent> -y --copy
<agent>为用户指定或当前对话所在的 agent(本 skill 在 Trae 中运行时默认trae)。-y跳过确认;--copy复制文件到目标 agent 的 skills 目录。- 禁止使用
-g全局安装。
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-skillsorComposioHQ/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