Skip to content
Research

Find Skills

Find existing agent workflows for a specific task and inspect candidates before installing.

Install with Skills CLI
npx skills add vercel-labs/skills --skill find-skills

What it does

A task description does not tell you which agent skill is worth adding. Find Skills gives the agent a discovery workflow that connects a concrete need to candidate packages and their original sources.

What changes after install

  • Frames searches around the task and domain rather than a vague tool category.
  • Uses the Skills CLI and the ecosystem directory to find candidates.
  • Separates recommending a candidate from installing the selected skill.

Install

Run this command with Node.js 22.20 or later and select your agent in the Skills CLI.

Install with Skills CLI
npx skills add vercel-labs/skills --skill find-skills

Before using Find Skills

  • Provide a specific task and access to skills.sh or upstream repositories so the agent can inspect candidates. CLI discovery also needs a terminal with the Skills CLI available through npx.

Read the reviewed setup instructions for the selected workflow.

When to use it

  • Finding a reusable workflow before writing new instructions.
  • Exploring options for a specific task such as PDF extraction or React performance.

When not to use it

  • Treating download counts or repository stars as proof of security or quality.
  • Reading scanned invoices or reconstructing their tables directly.
  • Creating a workbook or editing a Word document once the required skill is known.

A worked example

Give the agent this request: “Find a skill that can extract the line items from a scanned supplier invoice. I need one spreadsheet row per item, with description, quantity and line total. Show me a candidate before installing it.”

Start with the skills.sh directory, then run npx skills find invoice OCR to look for a closer match. One result in our November 18 search was zhangchenlai-dev/hermes-skill-store@invoice-ocr-sorter. The name makes it worth inspecting: a sorter might file invoices by vendor while returning none of the line items you need.

Open each candidate’s SKILL.md. Look for the step that reads a scanned page and an example showing what comes back. Ask the agent to return the source link, install command and one sentence explaining whether the output contains individual line items. If the guide leaves that open, mark it as unknown. After choosing a candidate, try one invoice and compare its line totals with the original.

Troubleshooting

  • The search command fails. If the shell reports that npx is missing, the search never ran. Browse skills.sh for the candidate now, or make npx available in the agent’s shell and repeat the query.
  • Claude Code cannot find Find Skills. From the project where you want to use it, run npx skills add vercel-labs/skills --skill find-skills -a claude-code. Then ask Claude Code to use Find Skills and give it the task you want to search for.
  • A task search misses a known skill. Retry with the exact skill name. If the publisher is known, check its GitHub repository directly. A directory entry and its search ranking can differ even when the instructions are available.

How it chooses an approach

When the request is “find something for invoices,” ask what arrives and what the user needs back. Filing attachments, checking a purchase order and returning spreadsheet rows are three different jobs. One example input and an acceptable output usually give you better search terms than a longer list of synonyms.

Browse skills.sh when the task is clear and the publisher is open. Compare candidates by the operation they document. Use the publisher and install count to decide which guides to read first. A popular document generator can still be a poor match for someone who needs to read existing invoices.

Go directly to GitHub when the user names a publisher, gives you a repository link, or remembers a skill that directory search missed. Start under that owner, open the skill folder, and check the name and description in its SKILL.md. A repository can contain several skills. Carry the exact folder and skill name into the recommendation so the user can review the same instructions you read.

When to use another skill

  • If an existing skill covers the input, operation and output, finish discovery and use that skill on a representative example. For invoices, the PDF skill is one candidate to review before writing your own.
  • If the tools are already available but every run needs the same team-specific instructions, use Skill Creator. Bring an example of a correct result and one that misses a requirement so you can test the new instructions.
  • If the missing step is an action the agent cannot perform, such as looking up a purchase order in an internal service, use MCP Builder to expose that operation as a tool.

What to check after it runs

  • Match the owner, repository and skill name in the suggested install command to the source you reviewed.
  • Open the directory listing to verify the install count. If no candidate documents the required operation, record that gap before choosing a package.

FAQ

Why does asking a how-to question sometimes start a Skills CLI search?
Find Skills is a set of instructions that can interpret a how-to request as a request for a specialist skill. It then uses the separate Skills CLI. If you want the agent to answer directly, say so in the request.
Why can the CLI find a skill but then report that there is no valid skill to install?
Search can return a listing before the installer checks the source. Open the exact repository and confirm that the selected skill has a SKILL.md with a name and description. A search result alone does not confirm installation.
Why can I find a skill by name but miss it when searching for the task?
Upstream users have observed different results for a task description and an exact name. Try the skill name or narrow the search to its GitHub owner, then inspect the candidate's documented workflow.
Where can I check a repository's stars if the search results omit them?
Open the source repository on GitHub for its star count. The install count on skills.sh measures a different activity. Check the skill instructions against your task before choosing it.