Skip to content

Guide · Open source

How to use skills: install agent skills with npx skills

Updated · written with AI from the project's own documentation and checked against our catalogue data

skills is an open-source command-line tool from vercel-labs that installs reusable instructions, called agent skills, for coding agents such as Claude Code and Cursor. This guide shows you how to check your setup, search for skills, install them into a project or globally, and try one without installing it. You need to be comfortable running commands in a terminal.

skillsvercel-labs/skills · ★ 37.7k · MIT

Quick start

  1. 1Check Node.js. Confirm you have Node.js 22.20 or later installed.
  2. 2Search for skills. Run npx skills find, optionally with a query, to browse what is available.
  3. 3Try one skill. Use npx skills use with --agent to launch a supported agent with a skill without installing it.
  4. 4Install into your project. Run npx skills add with the source repository, then choose the skills and agents to install to.
  5. 5Pin a single skill and agent. Use --skill and -a to install one named skill for one agent without prompts.
  6. 6Keep skills current. Run npx skills check to see updates and npx skills update to apply them.

Check the requirements

The CLI runs with Node.js. The README says you need Node.js 22.20 or later, so check your installed version before you start.

You also need a coding agent that the CLI supports. The README names OpenCode, Claude Code, Codex and Cursor, and says more are listed in the agents documentation.

  • Node.js 22.20 or later
  • A terminal and a project folder
  • A supported coding agent

Find skills you want

Skills are discovered at skills.sh. From the terminal you can search with the find command, optionally adding a query.

npx skills find

Install a skill into your project

Run the add command from your project folder and give it a source repository. The CLI then lets you choose which skills and coding agents to install to. Skills go into the current project by default.

To install one skill for one agent without the prompts, name the skill with --skill and the agent with -a. Add -g if you want the skill available across projects instead.

  • Project-only is the default; add -g for global installs.
  • Source formats, private repositories and all options are in the installation reference (docs/commands.md).
npx skills add vercel-labs/agent-skills npx skills add vercel-labs/agent-skills --skill web-design-guidelines -a claude-code

Try a skill without installing it

The use command lets you test a skill without adding it to your project. Pass the source and skill name joined by @ and a supported agent with --agent, and the CLI launches that agent with the skill. If you omit --agent, the CLI prints the prompt instead.

npx skills use vercel-labs/agent-skills@web-design-guidelines --agent claude-code

Manage installed skills over time

Once skills are installed you can list them, check for updates, update them or remove them. You can also create your own skill template and edit its SKILL.md file.

  • list: show installed skills
  • check: see whether updates are available
  • update: update installed skills
  • remove: remove installed skills
  • init: create a skill template
npx skills list npx skills check px skills update px skills remove px skills init my-skill

Know the experimental commands

Commands prefixed with experimental_ are previews. The README says their names, options and behaviour may change or be removed in any release without notice, so avoid relying on them in shared workflows if you need stability.

The README also describes experimental_sync, which syncs skills shipped by npm dependencies into your project, and experimental_install, which restores project skills recorded in skills-lock.json.

What people use it for

  • Adding a web design review skill to Claude Code in a project
  • Sharing the same agent skills across several projects with a global install using -g
  • Trying a skill from a repository before deciding to keep it
  • Creating a custom skill with npx skills init and editing its SKILL.md file

Frequently asked questions

Is skills free to use?

The project is released under the MIT License, as stated in the README. The license file in the repository sets out the terms.

What do I need to run npx skills?

The README says you need Node.js 22.20 or later. You also need a terminal and a supported coding agent such as Claude Code, Cursor, Codex or OpenCode.

Where are skills installed?

By default skills are installed to the current project. Add -g to make them available across projects. The README links to the agents documentation for installation paths.

What is the difference between add and use?

add installs a skill into your project. use runs a skill without installing it, either printing the prompt or launching a supported agent when you pass --agent.

Why did an experimental command change or stop working?

The README warns that experimental_ commands may change or be removed in any release without notice. Check the experimental commands reference if a command behaves differently after an update.

Does the CLI send data about me?

The README says the CLI collects anonymous usage data. Set DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1 to turn off telemetry and security-audit requests, and see the troubleshooting docs for what is collected.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Developers who use coding agents and want ready-made task instructions, or teams who want to share the same skills across projects, will find this CLI useful. Non-developers should look elsewhere, since it runs from a terminal and needs Node.js, and people who need a stable interface should avoid the experimental_ commands, which the README says may change without notice.

Install options & downloads