find-skills

Overview

What the find-skills skill does

find-skills is a discovery-focused GitHub skill from vercel-labs/skills that helps agents identify when an installable skill may already exist for a user’s request. It is designed for moments when someone asks how to do a task, wonders whether there is a skill for a workflow, or wants to extend an agent with a more specialized capability.

Rather than solving one narrow technical task by itself, find-skills helps route users toward the right skill in the broader ecosystem. That makes it useful as an early-step skill for capability discovery, installation decisions, and marketplace-style exploration.

Who this skill is for

This skill is a good fit for:

• Agent builders who want a repeatable way to discover relevant skills
• Users exploring whether a task is already covered by an installable skill
• Teams using the Skills CLI to add modular capabilities over time
• Anyone browsing the agent skills marketplace for tools, templates, or workflows

It is especially relevant when requests are open-ended, such as "how do I do X," "is there a skill for this," or "can you help with a domain-specific workflow?"

Problems it helps solve

The find-skills skill helps reduce guesswork during skill discovery by encouraging a structured search process. Based on the repository, it is intended for cases where users:

• ask for help with a task that may already have an existing skill
• want to search for tools, templates, or workflows
• express interest in extending agent capabilities
• mention a domain where they need extra support, such as testing, deployment, or design

In practical terms, that means find-skills is useful before installation, not only after. It helps determine whether you should install a new skill at all, and if so, what to look for.

What is included in this repository entry

The available repository evidence for this skill centers on SKILL.md, which defines the skill purpose, when to use it, and how it relates to the Skills CLI. The source explicitly references the open agent skills ecosystem, the npx skills command set, and the public skills directory at https://skills.sh/.

When find-skills is a good fit

Use find-skills when you need discovery support more than direct execution support. It is a strong choice if you are:

• evaluating install options before committing to a tool
• helping users phrase their needs into searchable skill queries
• browsing the marketplace for domain-specific capabilities
• building an agent workflow that should recommend skills dynamically

When find-skills may not be the best fit

find-skills may not be the right standalone choice if you already know the exact skill you want to install and use. In that case, a direct npx skills add <package> workflow may be faster. It is also not a replacement for the implementation logic of a specialized skill; its role is discovery and selection.

How to Use

Install the find-skills skill

Install find-skills from the vercel-labs/skills repository with:

npx skills add https://github.com/vercel-labs/skills --skill find-skills

This is the most direct path if you already know you want this specific skill.

Use the Skills CLI for discovery

The repository explicitly documents the Skills CLI as the package manager for the open agent skills ecosystem. Useful commands include:

• npx skills find [query] to search for skills by keyword or interactively
• npx skills add <package> to install a skill from GitHub or another source
• npx skills check to check for skill updates
• npx skills update to update installed skills

If you are still deciding what to install, start with npx skills find [query] before adding anything.

Browse the public marketplace

The source points users to https://skills.sh/ to browse available skills. This is useful when you want a higher-level marketplace view instead of starting from a command-line query.

A practical workflow is:

1. Clarify the task or domain you need help with.
2. Search with npx skills find [query].
3. Review likely matches on https://skills.sh/ if needed.
4. Install the selected skill with npx skills add <package>.
5. Use npx skills check and npx skills update to maintain installed skills.

How to evaluate whether you need this skill

Choose find-skills if your main problem is discovery. For example, it is useful when:

• a user asks for a capability and you do not yet know whether a skill exists
• you want to search by domain, workflow, or outcome
• you are building a capability recommendation step into an agent experience

If your workflow already starts from a known package or repository, you may only need the installation command rather than the discovery layer.

What to read after installation

The repository preview shows SKILL.md as the primary file for this skill. Start there to understand the intended trigger cases and workflow. In this case, SKILL.md is the key source of truth for how find-skills should be applied in conversation or skill selection flows.

FAQ

What is find-skills used for?

find-skills is used to help discover and install relevant agent skills when a user’s request suggests that an existing skill may already cover the task. It is focused on capability discovery, not on replacing the specialized skill itself.

How do I install find-skills?

Use:

npx skills add https://github.com/vercel-labs/skills --skill find-skills

This installs the find-skills skill from the vercel-labs/skills repository.

Do I need find-skills if I already know the package I want?

Not always. If you already know the exact skill or package to install, you can usually go straight to npx skills add <package>. find-skills is most helpful earlier in the process, when you are still searching.

Is find-skills a CLI tool?

find-skills is a skill, while the repository documentation identifies the Skills CLI as npx skills. The CLI is the tool you use to search, add, check, and update skills.

Can find-skills help with marketplace browsing?

Yes. The documented workflow references both CLI-based search and browsing at https://skills.sh/, which makes find-skills relevant for marketplace-style discovery as well as command-line installation planning.

What kinds of requests should trigger find-skills?

According to the repository, good trigger cases include questions like "how do I do X," "find a skill for X," "is there a skill that can...," and requests that imply interest in expanding agent capabilities for a specific domain or workflow.