The short answer
- Claude Code: run
npx skills add <owner>/<repo> --skill <name>in your project, or copy the skill folder to~/.claude/skills/<name>/(all projects) or.claude/skills/<name>/(one repository). - Claude apps (claude.ai, Desktop): turn on code execution, zip the skill folder, then upload it under Customize > Skills.
- Codex, Cursor and other agents: the same
npx skills addcommand installs into each agent's own skills folder.
Claude Code picks up skills you add to an existing skills folder in the current session, without a restart. If you just created the skills folder itself, run /reload-skills once.
Method 1: the skills CLI (any agent)
The skills CLI is an open-source installer from Vercel Labs. It needs Node.js 22.20 or later.
Open a terminal in your project folder.
Run the install command shown on the skill's page, for example:
npx skills add anthropics/skills --skill pdfPick the agents to install for when the CLI asks. To skip the question, name the agent:
npx skills add anthropics/skills --skill pdf -a claude-codeAdd
-gto install the skill globally, so every project on your machine gets it.
Leave out --skill to choose from every skill in a repository. Other useful commands:
| Command | What it does |
|---|---|
npx skills find [query] |
Search for skills |
npx skills list |
List installed skills |
npx skills check |
Check for updates |
npx skills update |
Update installed skills |
npx skills remove <name> |
Remove a skill |
The CLI collects anonymous usage data. Set DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1 to turn that off.
Method 2: copy the folder into Claude Code
Every skill is just a folder. Download it from GitHub (the "SKILL.md on GitHub" link on each skill page takes you there) and place it in one of these locations:
| Where | Path | Who gets it |
|---|---|---|
| Personal | ~/.claude/skills/<skill-name>/SKILL.md |
You, in every project on this machine |
| Project | .claude/skills/<skill-name>/SKILL.md |
Everyone working in that repository, once you commit it |
| Plugin | <plugin>/skills/<skill-name>/SKILL.md |
Wherever the plugin is enabled |
The folder name becomes the command name, so a skill at ~/.claude/skills/pdf/ can also be run directly with /pdf. Keep the whole folder, not only SKILL.md: many skills read scripts and reference files from their own directory.
Two folder names are reserved in Claude Code: synced (used for skills downloaded from your claude.ai account) and anthropic-skills. Do not use them for your own skills.
If a personal skill and a project skill have the same name, the personal one wins.
Method 3: upload to the Claude apps
Skills work on the Free, Pro, Max, Ultra, Team and Enterprise plans, and they need code execution.
- Go to Settings > Capabilities and make sure Code execution and file creation (called Create and edit files in the newer settings layout) is on.
- Zip the skill folder so the ZIP contains the folder with
SKILL.mdinside it. - Open Customize > Skills, click +, then Create skill, then Upload a skill.
- Choose the ZIP. The skill appears in your list and you can switch it on or off.
On Team and Enterprise plans an owner may need to enable Skills under Organization settings > Plugins & skills first. Anthropic's own Excel, Word, PowerPoint and PDF skills are already built in, so you do not need to upload those.
Skills you enable on claude.ai are also synced to Claude Code when you sign in with the same account. Claude Code downloads them into ~/.claude/skills/synced/.
Install a Claude skill from GitHub
Most skills live in a GitHub repository. Point the skills CLI at the repository and name the skill folder:
npx skills add https://github.com/anthropics/skills --skill pdf
The short form owner/repo works too. Leave out --skill to pick from every skill in the repository. To do it by hand, download the folder that contains SKILL.md (not just the file) and copy it into one of the locations in Method 2.
Install a skill globally
Add -g to install for every project on your machine instead of only the current one:
npx skills add anthropics/skills --skill pdf -g -a claude-code
For Claude Code a global skill goes in ~/.claude/skills/.
Install Claude skills in Cursor, Codex and VS Code
Skills use an open format, so the same folder works in other coding agents. The skills CLI puts it in the right place when you name the agent with -a:
| Agent | Flag | Project folder | Global folder |
|---|---|---|---|
| Claude Code (terminal, VS Code and JetBrains extensions) | -a claude-code |
.claude/skills/ |
~/.claude/skills/ |
| Cursor | -a cursor |
.agents/skills/ |
~/.cursor/skills/ |
| Codex | -a codex |
.agents/skills/ |
~/.agents/skills/ |
| GitHub Copilot (VS Code and CLI) | -a github-copilot |
.agents/skills/ |
~/.copilot/skills/ |
| Gemini CLI | -a gemini-cli |
.agents/skills/ |
~/.gemini/skills/ |
For example, to use a skill in Cursor:
npx skills add anthropics/skills --skill frontend-design -a cursor
Some skills mention Claude Code features by name, such as subagents or / commands; those parts may behave differently in other agents.
Check that it worked
- In Claude Code, run
/skillsto see the skills that loaded. - Ask for the kind of task the skill describes. Claude decides on its own when to use a skill, based on its description.
- To run a skill on purpose, type
/and its name.
If a skill does not load
- Wrong folder level. The path must end in
<skill-name>/SKILL.md, not<skill-name>/<skill-name>/SKILL.md. - Broken frontmatter.
SKILL.mdmust start with---, containname:anddescription:, and close with---. Paste it into the SKILL.md validator to check. - Cloud and Cowork sessions do not read
~/.claude/skills/on your machine. Enable the skill on your claude.ai account instead, or commit it to the repository's.claude/skills/. - Name clashes. A skill whose name matches another command may show up under its full name. Run
/skillsto see what was renamed.