Find Skills
Find Skills is an agent skill that helps solo builders search skills.sh and install agent skill packages whenever they need specialized workflows before committing to custom prompts or code.
npx skills add https://github.com/vercel-labs/skills --skill find-skills| Installs | 2M |
|---|---|
| GitHub stars | ★ 21.7k |
| Security audit | 2 / 3 scanners passed |
| Last updated | June 5, 2026 |
| Repository | vercel-labs/skills ↗ |
What it does
You know what you want the agent to do but have no idea which installable skill or repo already solves it.
Who is it for?
Indie builders who want to extend Claude Code, Cursor, or Codex with vetted SKILL.md packages instead of improvising every workflow from scratch.
Skip if: Teams that already pin a fixed skill set in-repo and forbid ad-hoc installs, or tasks that need a one-off MCP server rather than a skills.sh package.
When should I use this skill?
User asks how to do X, requests finding a skill for X, wonders if a skill exists, wants to extend agent capabilities, or searches for tools, templates, or workflows in the skills ecosystem.
What you get
You get a shortlist of matching skills, clear `npx skills add` commands, and a decision on whether to install from the open ecosystem.
- Ranked skill recommendations from `npx skills find` or skills.sh
- Concrete `npx skills add` install commands for chosen packages
- Brief rationale for install vs. custom workflow
Related skills
Skill CreatorScaffold, document, and package reusable agent skills so solo builders can ship consistent Claude Code–style capabilities without reinventing SKILL.md structure.277k148k
Lark Skill MakerAuthor new lark-cli Skills (SKILL.md) that wrap single APIs or multi-step Feishu/Lark workflows for reuse by agents.246k14.4k
Skills CliDiscover, install, and sync Agent Skills from skills.sh so Claude Code, Cursor, or Codex can reuse proven workflows instead of reinventing them in chat.222k61
Write A SkillGather requirements, draft SKILL.md with progressive disclosure, optional REFERENCE/EXAMPLES/scripts, and iterate with the user on coverage and depth.221k121k
Using SuperpowersInstall this as the default ritual so your coding agent always loads the right SKILL.md before planning, coding, or answering—instead of guessing from chat alone.150k221k
Find SkillsSearch skills.sh, Clawhub, and GitHub in one run to shortlist installable agent skills with per-registry popularity, match relevance, and optional security scans.134k6How it compares
Use the Skills CLI and skills.sh catalog instead of guessing repo names in chat or rewriting procedural guides by hand.
FAQ
Who is find-skills for?
Solo and indie builders using agentic IDEs who regularly need new workflows—testing, deploy, docs, growth—and want a repeatable way to search and install skills from the open ecosystem.
When should I use find-skills?
Use it when you ask how to do X, want a skill for a domain, or need capability extension—examples include discovering validation skills during Idea, integration skills during Build, QA skills during Ship, or distribution skills during Launch, all via `npx skills find`.
Is find-skills safe to install?
Treat any installed skill like third-party code: read SKILL.md, review the Security Audits panel on this Prism page, and only add packages you trust before running shell or network commands from their instructions.
SKILL.md
# 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 <package>` - 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: Check the Leaderboard First Before running a CLI search, check the [skills.sh leaderboard](https://skills.sh/) 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: ```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 4: Verify Quality Before Recommending **Do not recommend a skill based solely on search results.** Always verify: 1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100. 2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors. 3. **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: 1. The skill name and what it does 2. The install count and source 3. The install command they can run 4. 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: npx skills add vercel-labs/agent-skills@react-best-practices 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: ```bash npx skills add <owner/repo@skill> -g -y ``` The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts. ## Common Skill Categories When search