Skip to content
Find Skills

Find Skills

by Vercel vercel-labs/skills skills/find-skills

Vercel's skill for discovering agent skills: when you ask how to do something, the agent searches the open skills ecosystem with the Skills CLI, vets results by installs, source and stars, and offers the install command.

GitHub Docs
Development
Released
MIT

Install

Install with the skills CLI

One command for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf and dozens of other agents. Needs Node.js; the skill is fetched straight from vercel-labs/skills.

$ npx skills add vercel-labs/skills --skill find-skills

Run it in a terminal. The CLI finds the agents installed on your machine, asks which ones to add the skill to, and whether to install it into the folder you ran it from or for all your projects.

Other ways to install

Copy the whole skill folder — SKILL.md and any scripts or references beside it — into ~/.claude/skills/find-skills/, where Claude Code picks it up in every project. Only git is needed.

tmp=$(mktemp -d) && \
  git clone --depth 1 --branch main https://github.com/vercel-labs/skills.git "$tmp" && \
  mkdir -p ~/.claude/skills && \
  cp -R "$tmp"/skills/find-skills ~/.claude/skills/find-skills

No scripts or references next to it? Saving the SKILL.md alone as ~/.claude/skills/find-skills/SKILL.md works too.

Using another agent? Its personal skills folder
Codex
~/.agents/skills/
Cursor
~/.cursor/skills/
GitHub Copilot
~/.copilot/skills/
Gemini CLI
~/.gemini/skills/
Windsurf
~/.codeium/windsurf/skills/
OpenCode
~/.config/opencode/skills/
Open folder on GitHub

About

  • Triggers on "how do I do X" and "is there a skill for X" questions
  • Searches with npx skills find, optionally scoped to one GitHub owner
  • Quality bar before recommending: install count, source reputation, GitHub stars
  • Presents name, installs, source and the exact install command, then offers to install

Most people never go looking for an agent skill; they just ask their agent how to do something. Find Skills closes that gap. It is the discovery skill from Vercel's skills repository, the home of the npx skills CLI and the skills.sh directory, and it teaches the agent to recognise the moment a request could be served by an installable skill, whether the question is "how do I make my React app faster?", "is there a skill for changelogs?" or "can you do X?", and go find one.

The workflow is laid out in six steps. The agent first pins down the domain and the specific task, then checks the skills.sh leaderboard for a well-known option before falling back to a keyword search with npx skills find [query], which can be narrowed to a single publisher with --owner. It maps vague requests to concrete queries ("can you help me with PR reviews?" becomes npx skills find pr review) and suggests alternative terms when the first search comes up empty.

What makes it more than a search wrapper is the verification step. The skill tells the agent not to recommend anything on search results alone: prefer skills with more than 1K installs and be cautious under 100, weigh official publishers such as Vercel, Anthropic and Microsoft above unknown authors, and treat a source repository with fewer than 100 stars with scepticism. Recommendations come back with the skill's name, purpose, install count, source, install command and a skills.sh link, and the agent offers to run npx skills add <owner/repo@skill> -g -y itself.

When nothing fits, the skill says so plainly, offers to do the task directly and points to npx skills init for writing your own. It is useful for anyone using Claude Code, Cursor, Codex or another skills-compatible agent who wants the agent to extend itself on demand. MIT-licensed.

SKILL.md

The instructions your agent loads, as published by Vercel.

SKILL.md
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 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
Install

Related Skills

See all Find Skills alternatives

Skill: agent-browser

by Vercel

New

The skill for Vercel Labs' agent-browser, a fast Rust CLI that lets coding agents open sites, fill forms, click, screenshot and scrape through Chrome DevTools Protocol, using accessibility-tree snapshots with stable element refs.

DevelopmentTesting & QA

Skill: Deploy to Vercel

by Vercel

Vercel's official deployment skill — inspects project state, picks the right deploy path, and defaults to preview deployments with a claimable URL when no account is linked.

DevOps & Infrastructure
Browse all skills →