How to install, update and remove skills with npx skills
Updated
To uninstall a skill, run npx skills remove followed by its name. npx skills remove --all clears every installed skill without asking first, and npx skills update on its own brings all of them up to date. Here are the four commands you'll use most:
# Install a skill
npx skills add https://seoskills.sh --skill content-decay-predictor
# See what's installed in this project
npx skills list
# Update everything
npx skills update
# Uninstall a skill
npx skills remove content-decay-predictor
add takes a GitHub repository, a git or download URL, a local folder, or a site that publishes a skills index, like https://seoskills.sh. Skills go into your agent's folder for the current project, or into your home directory for every project if you add -g.
Install skills with npx skills add
The CLI behind the command is vercel-labs/skills, and it needs no account. Run it from your project's root, since a project install writes into folders under the current directory. Pass -a to choose the agent; without it, the CLI detects the coding agents you have installed and asks you to pick when it finds none.
From seoskills.sh
npx skills add https://seoskills.sh
npx skills add https://seoskills.sh --skill content-decay-predictor
The first command lists every skill our index serves and asks which ones to install. The second installs one of our own skills, Content Decay Predictor, by its slug, together with its scripts and reference files. Keep the https://: the CLI only looks up a site's index for a full URL, and it reads seoskills.sh/content-decay-predictor as a GitHub repository.
From a GitHub repository
npx skills add agricidaniel/claude-seo
npx skills add https://github.com/agricidaniel/claude-seo --skill seo-sitemap
The owner/repo shorthand and the full GitHub URL point at the same repository, and --skill names the skill you want. The second line is the form seoskills.sh shows for other authors' skills, as on the SEO Sitemap page. It is also what skills.sh shows, so the install is credited to the author. Private repositories take the same command, with the Git authentication you already have for that URL.
Other sources
- A path to one skill inside a repository, such as
https://github.com/vercel-labs/agent-skills/tree/main/skills/web-design-guidelines - GitLab and Azure Repos URLs, or any git URL, such as
git@github.com:vercel-labs/agent-skills.git - A local folder:
npx skills add ./my-local-skills - A direct download URL for a single
SKILL.mdor a.zip,.tar,.tar.gzor.tgzarchive, which the CLI tries after well-known discovery
Choose skills and agents with flags
| Flag | What it does |
|---|---|
-s, --skill | Installs specific skills by name. '*' means all of them. Quote a name that contains spaces. |
-a, --agent | Installs into specific agents, such as claude-code, cursor or codex. '*' means all agents. |
-g, --global | Installs to your user directory instead of the project |
-l, --list | Lists the available skills without installing any |
--copy | Copies files instead of symlinking them into agent directories |
-y, --yes | Skips all confirmation prompts |
--all | Installs all skills to all agents, without prompts |
To pass several skills or agents, repeat the flag:
# See what a repository holds before installing
npx skills add agricidaniel/claude-seo --list
# Two skills from one repository
npx skills add agricidaniel/claude-seo --skill seo-sitemap --skill seo-maps
# Every skill in the seoskills.sh index, into Claude Code only
npx skills add https://seoskills.sh --skill '*' -a claude-code
# One skill, global, two agents, no prompts
npx skills add https://seoskills.sh --skill content-decay-predictor -g -a claude-code -a cursor -y
Install for one project or globally
A project install, the default, writes into the agent's folder under the current directory, so you can commit the skills and your team gets the same set. -g writes to your home directory instead, for every project on the machine.
| Agent | -a value | Project (default) | Global (-g) |
|---|---|---|---|
| Claude Code | claude-code | .claude/skills/ | ~/.claude/skills/ |
| Cursor | cursor | .agents/skills/ | ~/.cursor/skills/ |
| Codex | codex | .agents/skills/ | ~/.codex/skills/ |
The CLI's README has the paths for every supported agent, and where agents keep skills explains the folders in more detail.
Installing interactively, you also choose how the files are placed. A symlink, the recommended option, links each agent to one canonical copy: a single source of truth that is easy to update. A copy gives each agent independent files. Choose it, or pass --copy, where symlinks aren't supported.
List, update and remove skills
See what is installed
npx skills list
npx skills ls -g
npx skills ls -a claude-code -a cursor
list, alias ls, shows the skills installed in the current project. Add -g to see your global skills instead, -a to show only the agents you name, or --json for output a script can read.
Update installed skills
npx skills update
npx skills update full-site-seo-auditor
npx skills update -g
npx skills update -y
With no names, update (or its alias upgrade) covers every installed skill and asks which scope to update. Give it names to update only those skills. -g limits the run to global skills and -p to project skills. -y skips the scope question and picks for you: project scope inside a project directory, global anywhere else.
Remove (uninstall) skills
npx skills remove
npx skills remove full-site-seo-auditor
npx skills remove full-site-seo-auditor -a claude-code
npx skills remove --global full-site-seo-auditor
npx skills remove --all
To uninstall a skill, use remove, or its alias rm. With no names, it lets you pick from the skills you have installed. -a removes a skill from the agents you list and leaves the others alone; without it, the skill comes out of every agent. --global targets global installs, and -y skips the confirmation. --all removes every installed skill with no confirmation, so don't combine it with skill names.
How the seoskills.sh index works
When the source is an https URL, the CLI looks for an index under the Agent Skills Discovery RFC at that address. seoskills.sh publishes one at https://seoskills.sh/.well-known/agent-skills/index.json. It lists every installable skill with a sha256 digest, and each entry is one of two kinds:
| Entry | Path | Used for |
|---|---|---|
SKILL.md | /.well-known/agent-skills/<name>/SKILL.md | A skill that is a single file |
| Archive | /.well-known/agent-skills/<name>/skill.tar.gz | A skill that needs more than one file, packed as a gzipped tar of its folder |
The CLI checks each download against its digest and skips one that doesn't match, and update compares digests to find the skills that changed. Our own skills are served as archives of their whole folder, which is how npx skills add https://seoskills.sh --skill content-decay-predictor brings scripts and reference files along.
The index holds one skill per name. When two skills share a name, the more-installed one gets it, and the other installs from its GitHub repository. A skill is listed only while it passes a static security scan. If a listed skill changes upstream and the new version fails the scan, it's taken off the site and out of the index, since a GitHub-form command fetches the author's repository as it is when you run it.
Command reference
| Command | What it does | Flags |
|---|---|---|
npx skills add <source> | Install skills from a repository, URL, local path or site index | -s, -a, -g, -l, --copy, -y, --all |
npx skills list (ls) | List the skills installed in this project, or globally with -g | -g, -a, --json |
npx skills update [skills] (upgrade) | Update installed skills to their latest versions | -g, -p, -y |
npx skills remove [skills] (rm) | Remove installed skills from agents | -g, -a, -s, -y, --all |
npx skills find [query] | Search for skills interactively or by keyword | --owner |
npx skills use <source>@<skill> | Print a prompt that uses one skill without installing it | --skill, --agent |
npx skills init [name] | Create a new SKILL.md template | none |
Next
- How to install skills in Claude Code: where Claude Code keeps skills and how it picks one
- Skill safety: what to check before you install
- How to write a SKILL.md: the format behind
npx skills init