AI Skills Catalog
AI Workers

Find Skills

Find existing agent skills for a concrete task, inspect their sources and present installation options before adding them to your setup.
SKILL SCORE83How it is scored
VerifiedFreeMIT

Works with

Packaged from the source skill for Claude, Codex and 4 more.

About this skill

Find Skills helps an agent turn a capability request into a shortlist of reusable skills from the open ecosystem. It connects the task and domain to skills.sh listings and the Skills CLI, then presents candidate sources and installation options for the user to assess.

Use this skill when

  • You need to find an existing workflow for a specific task, such as React testing, changelog creation or deployment.
  • You want to compare available skills before adding another dependency to an agent setup.
  • A requested capability may already exist as a maintained public skill.

What it can do

The workflow identifies the domain and concrete job, checks established listings, and searches with focused keywords or an owner filter when the initial results are too broad. It considers installation counts, source identity and repository context before explaining the options. The output includes what each candidate does, where its source lives and the corresponding installation command; installation follows the user's decision.

Typical workflows

  1. Translate a request such as improving React test coverage into a targeted skill search.
  2. Inspect likely matches and distinguish an official source from a similarly named third-party package.
  3. Present a small comparison with source links, tradeoffs and commands the user can review before installing.

Inputs and output

Provide the task, agent environment and any preferred publishers or constraints. Expect candidate skill names, a brief fit assessment, source links and installation instructions, or a clear result when no suitable skill is found.

Limitations

Searching or installing through npx skills requires Node.js, npm and network access; the CLI is not bundled in this instruction package. Cumulative installs and repository stars are context, not proof that a skill is safe or suitable. Inspect a candidate's instructions, license and required tools before authorizing installation.

What is inside the skill

Section headings from the original SKILL.md (about 692 words of instructions). Read the full text in the source repository before installing.

  1. When to Use This Skill
  2. What is the Skills CLI?
  3. How to Help Users Find Skills
  4. Step 1: Understand What They Need
  5. Step 2: Check the Leaderboard First
  6. Step 3: Search for Skills
  7. Step 4: Verify Quality Before Recommending
  8. Step 5: Present Options to the User
  9. Step 6: Offer to Install
  10. Common Skill Categories
  11. Tips for Effective Searches
  12. When No Skills Are Found

Bundled files

  • LICENSE

Example prompts

  • Find a maintained skill for React component tests, compare the closest matches and show their original source links without installing anything.
  • Search only Vercel-published skills for a Next.js performance review and explain which candidate fits our app.
  • Check whether a reusable changelog workflow exists for our repository; show the options and installation commands for my review.

How to install Find Skills

Claude Packaged
  1. Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
  2. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
  3. For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
  4. Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
More about skills for Claude
Codex Packaged
  1. Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
  2. Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
  3. Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
  4. AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
More about skills for Codex
GPT Packaged
  1. Download the GPT package from the skill page.
  2. Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
  3. Upload the bundled reference files as knowledge so the GPT can consult them.
  4. Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
More about skills for GPT
Gemini Packaged
  1. Download the Gemini package from the skill page.
  2. For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
  3. Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
  4. Test a matching task and verify the referenced tools and files are available.
More about skills for Gemini
Cursor Packaged
  1. Download the Cursor package from the skill page.
  2. Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
  3. Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
  4. Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
More about skills for Cursor
OpenCode Packaged
  1. Download the OpenCode package from the skill page.
  2. Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
  3. Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
  4. Start OpenCode in the project and test a matching task with the model and permissions you use.
More about skills for OpenCode

Permissions & security

Low risk

Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method

Read project files
Write generated skill files

Find Skills FAQ

What does the Find Skills skill do?

Find existing agent skills for a concrete task, inspect their sources and present installation options before adding them to your setup.

Which AI agents can use Find Skills?

Packages for Claude, Codex and 4 more are built from the same source instructions.

How do I install Find Skills in Claude?

Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.

Who made Find Skills and what is the license?

Find Skills is published by Vercel Labs under the MIT license. The source is https://github.com/vercel-labs/skills/tree/main/skills/find-skills. The catalog keeps the original attribution.

What permissions does Find Skills need?

Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.

Find Skills Skill for Claude & Codex | AI Skills Catalog