claudekit / tools / find-skills
[ Skill · Claude Code Utilities ]

Find Skills

A meta-skill that activates when users ask "how do I do X" or "is there a skill that can…", then searches the open agent skills ecosystem and walks the user through installation.

vercel-labs/skills/tree/main/skills/find-skills ·updated
$ npx skills add vercel-labs/skills --skill find-skills copy

What it does

The skills ecosystem is growing fast, but figuring out which skill to install — and where to find it — is the biggest onboarding hurdle. With Find Skills installed, users describe what they want to accomplish and the agent searches skills.sh plus the broader catalog, presenting vetted recommendations with one-line install commands.

How find-skills relates to vercel-labs/skills

find-skills is a single SKILL.md. The vercel-labs/skills repository it lives in is bigger and bundles two things together:

  1. The npx skills CLI — the command-line tool that searches, installs, and updates skills. It supports 54+ agents (Claude Code, Codex CLI, Cursor, Cline, Gemini CLI, and more) as install targets.
  2. A bundle of SKILL.md files — find-skills is one of them; others include frontend-design, skill-creator, and so on.

find-skills itself doesn’t search or install anything directly. It’s a meta-skill: user intent → find-skills (recommendation flow) → npx skills CLI (actual search and install) → the agent’s skills directory (where the chosen skill lands).

Activation triggers

The skill auto-activates when users:

  • Ask procedural questions — “how do I…”
  • Explicitly seek skills for specific tasks
  • Inquire about specialized capabilities
  • Want to extend functionality in particular domains
  • Search for tools, templates, or workflows

How it works

  1. Identify the domain and the specific task the user needs
  2. Check the skills.sh leaderboard for established solutions
  3. Run npx skills find [query] if the leaderboard doesn’t cover it
  4. Verify quality by checking install counts (prefer 1K+), source reputation, and GitHub stars
  5. Present options with installation commands and links
  6. Install via npx skills add <owner/repo@skill> once the user consents

Reference: npx skills CLI commands

These belong to the underlying CLI that find-skills calls into; you can run them directly from your shell with the same effect.

CommandPurpose
npx skills find [query]Interactive or keyword-based search
npx skills add <package>Install a skill
npx skills checkCheck for updates
npx skills updateUpdate installed skills

Notes

  • find-skills’s role is recommendation, not execution — the actual search and install work runs through the npx skills CLI, and the work itself is done by whatever skill gets installed.
  • Activation reach ≠ install reach — the find-skills SKILL.md activates wherever SKILL.md auto-activation is supported, while the npx skills CLI underneath it covers a broader set of 54+ agents as install targets.
  • Pairs with skills.sh, the public skills directory, for users who want to browse manually.
  • Public-index bias — recommendations come from popularity signals (install counts ≥1K and similar), so internal or private skill catalogs aren’t surfaced.
  • Install counts come from skills.sh — the install number on the card is collected by the npx skills CLI on opt-in, then anonymized and hourly-deduplicated by skills.sh (full methodology at skills.sh /about).
§ 7

See also

same category · curated
[01]
[Tool] Herdr · A terminal-native agent multiplexer in a single Rust binary. Herdr combines tmux-style session persistence and pane splits with agent awareness — a sidebar that shows whether each pane's agent is idle, working, blocked, or done — for Claude Code and other CLI agents. The direct Claude Code integration (`herdr integration install claude`) adds full state detection, semantic state forwarding over a local socket API, and agent-session restoration after a server restart.
tool · claudekit.io / tools / herdr
[02]
[Tool] CC Workflow Studio · Design workflows on a canvas in VS Code and export them as Markdown your AI agent already understands — skills, commands, and agents for Claude Code, Cursor, Copilot, and more. An MCP server runs in the background so you can refine workflows in natural language with 'Edit with AI'.
tool · claudekit.io / tools / cc-wf-studio
[03]
[Plugin] Caveman · why use many token when few token do trick — a Claude Code skill that cuts output tokens by ~65-75% by talking like caveman.
tool · claudekit.io / tools / caveman
§ 8

Frequently Asked Questions

frequently asked
§ 8.1
What is Find Skills?
A meta-skill that 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.
§ 8.2
Where does it run?
find-skills itself runs in any agent that supports SKILL.md auto-activation (Claude Code, etc.). The `npx skills` CLI it invokes covers a broader set — 54+ coding agents, including Claude Code, Codex CLI, Cursor, Cline, and Gemini CLI — as install targets.
§ 8.3
How do I install it?
Run `npx skills add vercel-labs/skills --skill find-skills`. It auto-activates on the next session — no extra config.
§ 8.4
What's it good for?
Users who don't know the skills ecosystem yet. Saying what you want to do ("draft a PR", "generate release notes") is enough — Find Skills surfaces vetted, popular skills with install commands.
§ 8.5
How does it work under the hood?
Five steps: identify the domain and task → check the skills.sh leaderboard → run `npx skills find [query]` if needed → verify quality (install counts ≥1K preferred, source reputation, GitHub stars) → present options with install commands and install via `npx skills add <owner/repo@skill>` once the user consents.