PluginBench
Skill
Official
Review
Audit score 70

find-skills

vercel-labs/skills

Discover and install agent skills to extend your coding agent's capabilities on demand

What is find-skills?

find-skills is a meta-skill that helps users locate, evaluate, and install skills from the open agent skills ecosystem. When you ask your agent how to do something or request a specialized capability, this skill guides the search process: querying the skills.sh leaderboard and CLI, vetting results by install count and source reputation, and presenting install commands. If no matching skill exists, it falls back to direct assistance or suggests creating a custom skill.

  • Detects when a user request might be satisfied by an installable skill
  • Searches the skills.sh leaderboard for popular, battle-tested skills
  • Runs `npx skills find [query]` to search by keyword or domain
  • Evaluates skill quality by install count, source reputation, and GitHub stars
  • Presents matching skills with name, install count, and ready-to-run install commands
  • Falls back to direct help or `npx skills init` guidance when no skill is found

How to install find-skills

npx skills add https://github.com/vercel-labs/skills --skill find-skills
Prerequisites
  • Node.js installed (to run `npx skills`)
  • Internet access to reach skills.sh and GitHub
  • A coding agent that supports SKILL.md packages (e.g., Claude Code, Cursor)
Claude Code
Cursor
Windsurf
Cline

How to use find-skills

  1. 1.Install the skill: `npx skills add https://github.com/vercel-labs/skills --skill find-skills`
  2. 2.Ask your agent a question like 'find a skill for PR reviews' or 'is there a skill for changelog generation'
  3. 3.The agent checks the skills.sh leaderboard for well-known matches first
  4. 4.If needed, the agent runs `npx skills find [query]` to search by keyword
  5. 5.Review the presented options: skill name, install count, source, and install command
  6. 6.Ask the agent to install your chosen skill, or run the install command yourself
  7. 7.If no skill is found, proceed with direct agent help or run `npx skills init` to create your own

Use cases

Good for
  • User asks 'how do I do X' and a skill already exists for that task
  • User wants to add React, Next.js, or TypeScript-specific knowledge to their agent
  • User needs specialized workflows for testing, deployment, or documentation
  • User wants to browse available skills before committing to one
  • User wants to create a custom skill for a recurring task
Who it's for
  • Developers using Claude Code, Cursor, or similar coding agents
  • Teams wanting to extend agent capabilities without writing custom tooling
  • Developers new to the skills ecosystem who need guided discovery
  • Power users who want to vet skill quality before installing
  • Anyone who frequently asks their agent 'can you help me with X'

find-skills FAQ

Does this skill install other skills automatically?

It can run `npx skills add <owner/repo@skill> -g -y` on your behalf if you confirm, but it will always present options and let you decide first.

How does the agent decide which skills to recommend?

It checks install count (prefers 1K+), source reputation (official owners like vercel-labs or anthropics), and GitHub stars before recommending anything.

What happens if no matching skill is found?

The agent acknowledges the gap, offers to help directly with its general capabilities, and suggests you can create a custom skill with `npx skills init`.

Can I scope searches to a specific GitHub owner?

Yes. The CLI supports `npx skills find [query] --owner <owner>` to limit results to a particular source.

Where can I browse available skills outside the agent?

Visit https://skills.sh/ to browse the leaderboard and explore skills ranked by total installs.

Full instructions (SKILL.md)

Source of truth, from vercel-labs/skills.


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", "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 as an installable skill.

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] [--owner <owner>] - Search for skills interactively or by keyword, optionally scoped to a GitHub owner
  • 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 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:

  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:

npx skills add <owner/repo@skill> -g -y

The -g flag installs globally (user-level) and -y skips confirmation prompts.

Common Skill Categories

When searching, consider these common categories:

CategoryExample Queries
Web Developmentreact, nextjs, typescript, css, tailwind
Testingtesting, jest, playwright, e2e
DevOpsdeploy, docker, kubernetes, ci-cd
Documentationdocs, readme, changelog, api-docs
Code Qualityreview, lint, refactor, best-practices
Designui, ux, design-system, accessibility
Productivityworkflow, automation, git

Tips for Effective Searches

  1. Use specific keywords: "react testing" is better than just "testing"
  2. Try alternative terms: If "deploy" doesn't work, try "deployment" or "ci-cd"
  3. Check popular sources: Many skills come from vercel-labs/agent-skills or ComposioHQ/awesome-claude-skills

When No Skills Are Found

If no relevant skills exist:

  1. Acknowledge that no existing skill was found
  2. Offer to help with the task directly using your general capabilities
  3. 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