What Are the skills CLI and find-skills? Vercel's Skill Installer, npx skills add, Supported Agents and Security
You type a command like `npx skills add vercel-labs/agent-skills` in the terminal; Vercel Labs' skills CLI installs the skill (an instruction folder containing a SKILL.md) for Claude Code, Codex, Cursor, OpenCode and, according to the README, 75 more agents; with the same tool you search, list, update and remove skills. find-skills, in the same repository, is a skill: it lets your agent ask "is there a ready-made skill for this" and search the skills.sh directory. Free (MIT), no account, requires Node.js 22.20 or later. The CLI sends anonymous usage data (`DISABLE_TELEMETRY=1` turns it off), and skills.sh does not guarantee the safety of every skill; read the SKILL.md before installing.
- What it does
- Finds, installs, updates and removes skills for agents
- Type
- Command-line tool (npm package) + a skill
- Where
- Claude Code, Codex, Cursor, OpenCode and ~75 more agents
- Requirements
- Node.js 22.20+ and a terminal
- Data
- Sends anonymous usage data (can be turned off)
- Latest version
- skills 1.7.2 (October 9, 2026)
- Cost
- Free (MIT); no account
What Do the skills CLI and skills.sh Do?
A skill is an instruction folder that tells an AI agent how to do a specific job; it contains a SKILL.md file with a name, a description and steps. The skills CLI is a command-line tool (npm package skills) that downloads these folders from repositories such as GitHub and puts them in the folder that agents like Claude Code, Codex and Cursor read. The README describes it as the CLI for the open agent skills ecosystem and labels it a Vercel Labs product.
skills.sh is the same team's skill directory: a leaderboard ranking skills by install count, topics, and an install command for every skill. The ranking comes from the anonymous install data the CLI collects (skills.sh docs).
| Command | What it does |
|---|---|
npx skills add <source> | Installs a skill. The source can be a GitHub shorthand, a full URL or a local path. |
npx skills use <source> | Uses a single skill without installing it: generates prompt text or launches the agent with --agent. |
npx skills find [query] | Searches for skills; interactively or by keyword, and with --owner in one owner's repositories. |
npx skills list (ls) | Lists installed skills. |
npx skills update [skill] | Updates installed skills. |
npx skills remove [skill] (rm) | Removes skills. |
npx skills init [name] | Creates a new SKILL.md template. |
Who it's for: anyone who wants to add ready-made skills to agents like Claude Code, Codex and Cursor. Who it's not for: people who don't use a terminal; the tool has no interface (official sources mention none).
How Do You Install a Skill With npx skills add?
The CLI needs no installation; it runs directly with npx. You need a terminal and Node.js 22.20.0 or later (the npm package's engines field; the README states no version). The commands are exactly as given in the README and on the skills.sh page. During installation the CLI detects the agents on your computer itself; if it finds none, it asks which one to install for.
› npx skills add vercel-labs/agent-skills› npx skills add vercel-labs/agent-skills --list› npx skills add vercel-labs/agent-skills --skill frontend-design -g -a claude-code -y› npx skills add https://github.com/vercel-labs/skills --skill find-skillsThis command puts find-skills into your agent's folder as a skill; then you can ask your agent for skills (see the find-skills section).
› npx skills use vercel-labs/agent-skills@web-design-guidelines | claude› npx skills use vercel-labs/agent-skills --skill web-design-guidelines --agent claude-codeuse writes the selected skill files to a temporary folder; without --agent it only prints the generated prompt text. With --agent, it launches a single supported agent interactively with that prompt.
For private repositories you use the same command; the CLI uses the credentials you've already configured for the repository URL. For GitHub it first tries your normal Git credentials; if that fails, gh repo clone if you're signed in to the GitHub CLI, then SSH. The README states that it does not run gh auth token and does not copy stored GitHub CLI credentials.
› npx skills add acme/private-skillsOptionally, a GITHUB_TOKEN or GH_TOKEN environment variable can be provided explicitly for GitHub API requests.
| Option | What it does |
|---|---|
-g, --global | Installs to the user folder instead of the project. |
-a, --agent <agent...> | Installs for specific agents (e.g. claude-code, codex). |
-s, --skill <skill...> | Installs specific skills by name; '*' for all. |
-l, --list | Lists the repository's skills without installing. |
--copy | Copies files instead of creating symlinks. |
-y, --yes | Skips all confirmation prompts. |
--all | Installs all skills for all agents without prompting. |
| Scope | Flag | Folder | When |
|---|---|---|---|
| Project | (default) | ./<agent>/skills/ | Committed with the project, shared with the team. |
| Global | -g | ~/<agent>/skills/ | Available in all projects. |
There are two install methods: symlink (recommended; every agent links to a single copy, easy to update) and copy (--copy; when symlinks aren't supported). Operating system differences are not covered in the README.
What Is find-skills?
find-skills is not a program but a skill in Vercel's skills repository (skills/find-skills), meaning a set of instructions given to the agent. According to its SKILL.md it kicks in when: you ask questions like "how do I do X", say "find a skill for X" or "is there a skill that does X", want to extend the agent's capabilities, or ask for help in an area such as design, testing or deployment.
- Understands the need: the domain (such as React, testing, design) and the task.
- Checks the leaderboard first: whether there's a well-known skill in that area in the skills.sh ranking.
- Otherwise, searches: runs
npx skills find [query]. - Verifies: install count (prefers over 1,000, flags caution under 100), the source's reputation and the repository's GitHub stars (skeptical under 100).
- Presents: the skill name, what it does, install count, install command and skills.sh link.
- Installs if you want:
npx skills add <owner/repo@skill> -g -y.
!The SKILL.md says the agent can run the install with -g -y if the user asks: -g installs at the user level for everything, -y skips confirmation. To keep the agent from installing on your behalf, write "don't install without my approval" in your prompt. The criteria it checks (install count, stars, source) measure popularity, not security.
How Do You Search, Update and Remove Skills?
After installation, the agent's own skill mechanism loads the skill; how it's triggered varies by agent and is not covered in the skills CLI docs (the README links to each agent's own docs). The CLI's job is to install and manage.
› npx skills find typescript› npx skills find react --owner vercel› npx skills ls -g› npx skills update› npx skills update frontend-design› npx skills init my-skill| update option | What it does |
|---|---|
-g, --global | Updates only global (user-level) skills. |
-p, --project | Updates only project skills. |
-y, --yes | Skips the scope prompt (project if you're in one, otherwise global). |
Installing and updating fetch the skill as it is at that moment; its content may have changed. Before updating an important skill, read the new SKILL.md.
Which Agents Does the skills CLI Work With?
The README's first line says "OpenCode, Claude Code, Codex, Cursor and 75 more" and gives each agent's --agent name and project/global folder path in a table. The table below counts as "yes" only those named in that table.
| Claude CodeYes | --agent claude-code; .claude/skills/ for the project, ~/.claude/skills/ for global. In the README compatibility table, allowed-tools, context: fork and hooks are "Yes" here. |
|---|---|
| CodexYes | --agent codex; project .agents/skills/, global ~/.agents/skills/. |
| CursorYes | --agent cursor; project .agents/skills/, global ~/.cursor/skills/. |
| OpenCodeYes | --agent opencode; project .agents/skills/, global ~/.config/opencode/skills/. |
| Gemini CLI, GitHub Copilot, Windsurf, Cline, Roo Code, Goose, Antigravity and the other agents in the READMEYes | The --agent name and folder path for each are in the README table. |
| Features such as allowed-tools, context: fork and hooksPartly | Varies by agent: in the README compatibility table, for example, context: fork is "Yes" only in Claude Code, and hooks only in a few agents. |
| Claude.ai and the Claude appUnclear | Not named in the docs. The CLI writes to local folders; "not in the docs" doesn't mean it won't work. |
| Windows, macOS, LinuxUnclear | The README doesn't describe operating system differences. |
VS Code is not named in the README; GitHub Copilot (github-copilot) is.
What Does the skills CLI Access, and Does It Send Data?
The skills.sh directory; SKILL.md files in GitHub, GitLab, Azure Repos or any Git repository; direct SKILL.md or archive download URLs. For private repositories, the Git credentials you configured.
Writes the skill folders you choose to the project or user folder (for example .claude/skills/, ~/.claude/skills/) as symlinks or copies. update and remove touch these folders, init writes a new SKILL.md. remove --all deletes everything without confirmation.
Default limits for direct download URLs: 10 MiB download, 25 MiB extracted content, 1000 files. For sources you trust, raise them with SKILLS_DOWNLOAD_MAX_BYTES, SKILLS_EXTRACT_MAX_BYTES and SKILLS_EXTRACT_MAX_FILES.
README: the CLI collects anonymous usage data and no personal information. GitHub repository and skill identifiers are sent only for repositories GitHub confirms are public; for other remote sources, the source and skill identifier may be included in install data. DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1 turns it all off. The skills.sh docs list the same data as "skill name, skill files and timestamp"; the two documents word it slightly differently.
A skill you install is an instruction given to the agent; if its content is malicious, it can steer the agent into the wrong task. skills.sh states on its own page that it can't guarantee the quality or security of every skill and asks you to review before installing. Read the SKILL.md before installing; stars and install counts are not proof of security.
!Security check (October 15, 2026): GitHub Security Advisories (vercel-labs/skills) list no entries, and OSV has no record for the skills npm package. The repository has no SECURITY.md; the skills.sh docs point to security.vercel.com for security reports. The package has no preinstall, install or postinstall script that runs during installation; releases are signed with npm provenance. No recorded advisories are listed; this does not mean "safe".
The skills.sh/audits page shows Gen Agent Trust Hub, Socket and Snyk results for skills side by side. On October 15, 2026, find-skills showed Gen "Safe", Socket "0 alerts" and Snyk "Med Risk" (Snyk "Warn" on the skill page). These are third-party scans, not guarantees.
Is the skills CLI Free?
Yes. The skills CLI is MIT-licensed open source; it doesn't require a plan, an account or an API key, and the README mentions no fee. No prices or plans appear on the skills.sh pages. The skills you install have their own licenses and required services; your agent's (Claude Code, Codex, Cursor) plan and limits also apply separately. Official sources list no paid plan, so there is no price to show.
- MIT: free to use, modify and distribute; copyright and license notices must be kept
- Can be used in commercial projects
- A skill you install may have a different license; check the license in that skill's repository before using it
Source: vercel-labs/skills README, GitHub license info and npm registry (October 15, 2026). This is not legal advice.
Common Problems and Fixes
| What happens | What to do |
|---|---|
| The skill doesn't load in the agent | README: verify the skill was installed to the right folder, check the skill loading conditions in the agent's own docs, and make sure the SKILL.md frontmatter is valid YAML. |
| "No skills found" | README: the repository must contain valid SKILL.md files with both name and description. |
| Permission error | README: make sure you have write permission to the target folder. |
| Symlinks not supported | The README points to the copy method (--copy) for this case. |
Reported by users The name you pass with --skill isn't found | Open issues: #2504 (October 15, 2026; per its title, names with spaces or underscores don't match the hyphenated form) and #2492 ("No matching skills found for: *"). No official fix; the README says to use quotes for names with spaces. |
| Reported by users Some agent folders aren't searched during discovery | Open issue #2502 (October 15, 2026): reports that 30 agent folders from the docs are missing from the discovery list. If you run into this, pass the skill by its folder path directly. |
Based on issue titles only; check the issue itself for its resolution status.
How Do You Remove Skills and the skills CLI?
- Remove a skill:
npx skills remove <skill-name>. Remove a global one with--global, from a specific agent with--agent; to delete everything,npx skills remove --all(no confirmation). - Remove find-skills: It's a skill too:
npx skills remove find-skills. - The CLI itself: If you ran it with
npx, there's no permanent install; only the package manager's cache remains. - Turn off data sending: Environment variable
DISABLE_TELEMETRY=1(orDO_NOT_TRACK=1).
Frequently asked questions
What are skills.sh and the Vercel skills directory?
skills.sh is the skills CLI's skill directory: it ranks skills by install count and shows an install command for each one. The ranking comes from the CLI's anonymous install data. The site states that it can't guarantee the quality or security of every skill.
What is find-skills?
A skill in Vercel's skills repository. When you ask your agent "is there a ready-made skill for this", it checks the skills.sh ranking and an npx skills find search, filters by install count, source and GitHub stars, and suggests the install command.
How do you install a skill with npx skills add?
In the terminal you type npx skills add followed by the source: a GitHub shorthand (vercel-labs/agent-skills), a full URL or a local folder. The CLI detects the agents on your computer. Use --skill for a specific skill, -g for all users, -y to skip prompts.
Which agents does the skills CLI work with?
The README lists install paths for OpenCode, Claude Code, Codex, Cursor and 75 more agents (including Gemini CLI, GitHub Copilot, Windsurf, Cline and Roo Code). In Claude Code it writes to .claude/skills/ for the project and ~/.claude/skills/ for the whole user.
How does npx skills update work?
It brings installed skills to their latest version. You can update one at a time by name, only global ones with -g, or only project ones with -p; -y skips prompts. An update fetches the skill as it is at that moment.
Related guides
Sources
- skills CLI README (vercel-labs/skills)
- find-skills: SKILL.md
- skills.sh: find-skills
- skills.sh docs
- skills.sh: CLI
- skills.sh: security audits
- npm: skills
- vercel-labs/skills: GitHub issues
Not clear in the official sources: Windows, macOS and Linux differences (not mentioned in the README) · use in Claude.ai and the Claude app (not in the docs) · how agents trigger a skill (varies by agent, not covered in the CLI docs) · the exact scope of data sent in telemetry (the README and skills.sh docs describe it slightly differently) · pricing of skills.sh Packs and the custom skill service · current status of open issues · Turkish support (docs are in English). Each is covered in the relevant section.





