菜单
Helps users discover and install agent skills. Use when the user asks questions like "how do I do X", "find a skill for X", "is there a skill that can...", or expresses interest in extending capabilities — i.e. whenever they're looking for functionality that might exist as an installable skill.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | find-skills |
| description | Helps users discover and install agent skills. Use when the user asks questions like "how do I do X", "find a skill for X", "is there a skill that can...", or expresses interest in extending capabilities — i.e. whenever they're looking for functionality that might exist as an installable skill. |
This skill helps you discover and install skills from the open agent skills ecosystem.
Use this skill when the user:
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 <package> - Install a skill from GitHub or other sourcesnpx skills check - Check for skill updatesnpx skills update - Update all installed skillsBrowse skills at: https://skills.sh/
When a user asks for help with something, identify:
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)If the leaderboard doesn't cover the user's need, run the find command:
npx skills find [query] [--owner <owner>]
For example:
npx skills find react performancenpx skills find pr reviewnpx skills find changelogDo not recommend a skill based solely on search results. Always verify:
vercel-labs, anthropics, microsoft) are more trustworthy than unknown authors.When you find relevant skills, present them to the user with:
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:
npx skills add vercel-labs/agent-skills@react-best-practices
Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
If the user wants to proceed, you can install the skill for them:
npx skills add <owner/repo@skill> -g -y
The -g flag installs globally (user-level) and -y skips confirmation prompts.
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 |
vercel-labs/agent-skills or ComposioHQ/awesome-claude-skillsIf no relevant skills exist:
npx skills initExample:
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
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
Review or write docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", "check this page against the writing handbook" — and proactively whenever writing or editing content under docs/src/content/docs/, since that's this repo's default docs style.
Remove AI-generated code slop and clean up code style. Use when asked to "deslop", clean up AI-generated code, or review a branch diff for slop before merging.
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Use when editing wrangler.jsonc, running wrangler commands, bumping compatibility dates, or maintaining a Cloudflare Workers deployment. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Reference for Tailwind CSS v4 syntax and the differences from v3.x. Use when configuring Tailwind (CSS-first @theme config, @import "tailwindcss"), using new v4 features (container queries, 3D transforms, gradients, composable variants, @utility/@variant/@plugin), or migrating v3 patterns. This repo is on v4 — do NOT emit v3 syntax like tailwind.config.js, @tailwind directives, or bg-gradient-*.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".