Skip to content
Agentic Levels
Start hereLevelsTracksPromptsAbout
Get my levelGet my level

  • Start hereYour first useful task with AI.
  • Level quiz8 questions. No AI needed.
  • Fluency ScoreYour Level and a score, from your own AI.

  • LevelsThe 11 levels, in order.
  • LessonsShort lessons, filter by level.
  • TracksGuided paths by tool, role or goal.
  • Set up your AI tool
  • Starter packFree files that help AI remember.

  • PromptsReady prompts to copy and adapt.
  • ChatGPT vs Claude vs GeminiPick the right one for the job.
  • How-tos
  • ReferenceCommands for Claude Code, Codex, Antigravity.
  • ResourcesHand-picked reading and tools.

  • Your progress
  • Your next moveAn interview that picks your next skill.
  • Your next lessonsThe next lessons at your level.
  • Updates

  • Pricing
  • About
  • FAQ & Feedback
  • Work with us
  • How we handle your data
Sign inPreferences
AboutPricingHow-tosPromptsStarter packMy stackHow we handle your data

© 2026 Fuentes Studio

PrivacyTermsRefundsAccessibilityAI content policyCredits
yourCouncil
Ready to help
✦

What do you want to understand?

Ask anything about what you're learning.

←Claude Code Fundamentals
  1. Tracks
  2. ›Claude Code Fundamentals
  3. ›How-to guide

How to use find-skills

Vercel's skill that searches skills.sh, a public directory of agent skills, and offers to install what it finds.

Goes with the lesson: Add skills and subagents with restraint →

Levels 5 to 6On GitHub

Before you build a skill, someone may have shared one already. find-skills searches the skills.sh directory for you. It sat in our setup for 90 days and never ran once on its own. This guide shows how to call it by name, and how to judge a skill before it goes in.

Before you start

You'll want a working sense of what a skill is and how your agent picks one before you search for more of them.

  1. 1Know why fewer skills work better
  2. 2Check your tool's own finder first
  3. 3Install find-skills for your tool
  4. 4Ask for it by name
  5. 5Read the skill before it goes in
  6. 6Approve the install yourself
  7. 7Use it on one real task, then keep it or cut it

Steps

01

Know why fewer skills work better

Claude Code lists the skills it can start on its own in space capped at 1% of its working memory (the context window). Codex caps its list at 2%. When a list overflows, descriptions get cut, so each new skill makes the others start less reliably.

02

Check your tool's own finder first

If your tool's own finder has what you need, stop here. In Claude Code, type /plugin to open the Discover tab. In Codex, type $skill-installer, and in Antigravity, open Customizations, then Marketplace.

03

Install find-skills for your tool

First, ask your agent (Claude Code, Codex or Antigravity) to check that you have Node.js 22.20 or newer. Node.js is a free program these install lines need. Then ask it to run only your tool's line.

Find your tool below and use only its line
Claude Code: npx skills add vercel-labs/skills --skill find-skills -g -a claude-code Codex (approve network access when it asks): npx skills add vercel-labs/skills --skill find-skills -g -a codex Antigravity: npx skills add vercel-labs/skills --skill find-skills -g -a antigravity
04

Ask for it by name

Name the skill in your request; in our setup it never started on its own. Expect up to three options, each with its install count, its GitHub page and an install line.

Ask your agent this
Use the find-skills skill to search skills.sh for a skill that helps me [YOUR_TASK]. Show me up to three options with install counts, the GitHub repo and its star count. Don't install anything.
[YOUR_TASK]The job you want a skill for e.g. turn meeting notes into a list of decisions and owners
05

Read the skill before it goes in

Install counts measure popularity, not safety. skills.sh shows a safety check before an install, but that check never blocks one. Skip a skill that runs scripts the summary can't explain, sends your files anywhere, or needs a paid account you didn't plan on.

Ask your agent this
Open the SKILL.md for [SKILL_NAME] and any scripts in its folder. In plain words, tell me what it tells you to do, what it runs, what it sends anywhere, and whether it needs keys or a paid account.
[SKILL_NAME]The option you liked, copied exactly from the list e.g. anthropics/skills@pdf
06

Approve the install yourself

When your agent runs npx skills, the command skips its own questions. Your agent asking to run the command is your last check. Approve it only after you've read the skill.

Ask your agent this
Install [SKILL_NAME] for [YOUR_TOOL] only. Show me the exact command and wait for my yes. If the skill doesn't show up afterwards, tell me to start a new chat.
[SKILL_NAME]The skill you read e.g. anthropics/skills@pdf
[YOUR_TOOL]Your agent e.g. Claude Code
07

Use it on one real task, then keep it or cut it

If the skill didn't help on a real task, remove it. In Claude Code, /skill-doctor shows how much of the skill list each skill takes and how often you use it. In Codex or Antigravity, ask your agent which skills it has that you haven't used.

Ask your agent this to remove one
Remove [SKILL] for my tool only, then tell me which skills are still installed.
[SKILL]The skill's short name e.g. pdf

How do you know it worked?

  • You checked your tool's own finder before installing anything.
  • find-skills gave you up to three options for a task you named.
  • You read one skill's plain-words summary, then approved its install yourself or skipped it.
  • You can say how to remove a skill you no longer use.

If something looks off

find-skills didn't start on its own
We saw the same: zero runs on its own in 90 days. Name find-skills in the prompt. We now use our own small hook (a check that runs on each prompt) to suggest installed skills instead.
It installed a skill without asking
When an agent runs npx skills, the command never asks. Start each request with "Don't install anything" until you've read the skill.
"command not found: npx" or an "Unsupported engine" warning
Node.js is missing or older than version 22.20. Ask your agent to install the current version, then run the install again.
The new skill doesn't show up
The skill went to a different agent, or the chat started before the install. Ask your agent which skills are installed for your tool, then start a new chat.
Your other skills stopped starting on their own
The skill list is over its budget, so some descriptions got dropped. Remove the skills you don't use. In Claude Code, run /skill-doctor to find them; in Codex or Antigravity, ask your agent which ones you haven't used.

Skills & Commands Reference

find-skills drives the skills command (npx skills). These are the lines you'll ask your agent to run. Add -g to act on every project.

Command / SkillWhat it doesWhen to use it
npx skills find [query]basicSearches skills.sh by keywordLooking for a skill without find-skills, or to check what it found
npx skills add owner/repo --skill namebasicInstalls one skill from a GitHub repoAfter you've read the skill. Add -a and your agent's name to pick the tool
npx skills listbasicLists the skills it installedA skill doesn't show up, or you're deciding what to cut
npx skills remove namebasicRemoves an installed skillA skill didn't help on a real task. Add -a and your agent's name, or it comes out of every agent
npx skills check / updateadvancedChecks for newer versions, then installs themOnce a month, after you've read what changed
DISABLE_TELEMETRY=1advancedTurns off the anonymous usage report the tool sends, and its safety-check requestsYou don't want install data leaving your computer

See also

  • Lesson: add skills and subagents with restraint
  • Matt Pocock's skills: which ones to try first, and which to skip
  • skill-creator: build your own skill when nothing fits
  • Anthropic Skills Library: the official skills to check first
  • My stack: the skill-router hook we use instead of find-skills

What you'll do, 7 steps

  1. 1Know why fewer skills work better
  2. 2Check your tool's own finder first
  3. 3Install find-skills for your tool
  4. 4Ask for it by name
  5. 5Read the skill before it goes in
  6. 6Approve the install yourself
  7. 7Use it on one real task, then keep it or cut it

Was this helpful?