Find skills on GitHub: three different starting points
To find Agent Skills on GitHub, search for the task, inspect the actual SKILL.md, and install only the skill and client you intend to use. You do not need to install a discovery skill before you can search.
Three names often get mixed together:
| Name | What it is | Where to start |
|---|---|---|
| GitHub search | A way to find repositories and files | Search for the task or a SKILL.md path |
find-skills |
A specific discovery skill in Vercel Labs' repository | Read its instructions before installing it into an agent |
skills CLI |
The command-line installer and discovery tool | Use its find, add, list and remove commands |
The official CLI repository is vercel-labs/skills. This guide reviewed source revision a80e4c9d12d607631249d4d7d059f835d4b2f13a on October 26, 2026. Its package manifest declares version 1.7.4 and Node.js 22.20.0 or later. We did not install skills, execute repository scripts, change local agent configuration or test an agent response.
Search GitHub for the file and the task
For an unknown publisher, begin with ordinary repository search using the task you need, such as code review or documentation. A repository title containing “skills” does not tell you whether it contains installable Agent Skills.
Once you have an owner or repository, use GitHub's Code search to narrow the files. For example:
repo:vercel-labs/skills path:SKILL.md
To look for a task across matching paths, try:
path:SKILL.md "code review"
These are example queries, not a promise of particular search results. GitHub's code-search syntax guide documents repo:, path: and quoted exact strings. Code search syntax differs from repository or issue search. A path: term matches paths; it is not a package-install command.
Open the file in its repository. Check the owner, directory, branch or revision, and links to companion files before copying an installation command. Keep the source URL with your notes so you can identify the same skill later.
Use the CLI to discover candidates
The upstream README documents the CLI search:
npx skills find code review
The command reference also supports narrowing a search to a GitHub owner:
npx skills find react --owner vercel-labs
Running npx skills find without a query opens interactive search. Discovery gives you candidates; it is not an installation or proof that a skill works in your client. Search terms should describe the job. If “deploy” is unhelpful, a more specific task or “deployment” may produce a different set of candidates.
A quiet result does not establish that no suitable file exists anywhere on GitHub. Inspect a known publisher's repository directly when you already have one.
Judge the contents before installing
Read the actual find-skills instructions if that is the skill you want. They describe a workflow for understanding a request, finding candidates and presenting options. Other skills may contain a completely different workflow despite a similar name.
For each candidate, answer these questions:
- Task fit: does its description cover your job and specify a useful result?
- Source: who maintains the repository, and can you trace the installation command back to it?
- Dependencies: does it reference scripts, services, accounts or tools you do not have?
- Effects: what could the instructions ask your agent to read, run, modify or send?
- Maintenance: does the documentation match the files and client you will use?
Stars and install counts can help you find established projects, but they do not establish permission to run a script or prove correctness. A smaller, well-scoped skill you understand can be a better fit than a popular bundle that adds unrelated instructions.
List the repository, then install one skill
For the specific find-skills skill, list the repository's available skills first:
npx skills add vercel-labs/skills --list
The documented --list option lists available skills without installing them. If you choose to proceed, this example targets Claude Code in the current project:
npx skills add vercel-labs/skills --skill find-skills --agent claude-code
For Codex, replace claude-code with codex. The default scope is the project from which you run the command; add --global only when you want a user-level installation across projects. Review the prompts instead of adding --yes or installing every skill to every agent.
The CLI's supported-agent table lists these paths:
| Client | Project skills | User-level skills |
|---|---|---|
| Claude Code | .claude/skills/ |
~/.claude/skills/ |
| Codex | .agents/skills/ |
~/.agents/skills/ |
The CLI supports symlink and copy installation methods. Inspect the reported destination rather than assuming the same physical folder is used for every client. A source repository containing a skill is separate from the client loading that installed skill.
Check the result and diagnose a missing skill
For the Claude Code project example, the documented listing command is:
npx skills list --agent claude-code
For a user-level installation, include --global; use the matching agent name for another client. Expect the installed skill to appear in that scope's listing. Then follow your agent's own loading instructions and check that it can identify the skill. A successful file copy does not demonstrate an end-to-end task result.
The troubleshooting guide identifies three common failures. “No skills found” calls for checking valid SKILL.md files with name and description in YAML frontmatter. A skill that does not load calls for checking the destination path and the client's loading requirements. Permission errors call for checking write access to the selected directory. Diagnose that layer before installing to additional clients or broadening permissions.
To remove the project-level example:
npx skills remove find-skills --agent claude-code
Use the same scope as installation, adding --global for a user-level copy. The goal is one understood skill in the intended client, with a known source and removal route. None of the examples above was executed for this article.