Install guide
How to Install a Claude Skill (Claude Code and Claude.ai)
Installing a Claude skill takes two commands in Claude Code, or one command if you skip the plugin system entirely. This page is the short version, plus the three places it usually goes wrong.
Route 1: the Claude Code plugin marketplace
Claude Code has a built-in plugin system, and Anthropic's own repository is registered as a marketplace. Start with this unless you have a reason not to.
/plugin marketplace add anthropics/skills
That registers the repository as a source. It installs nothing yet. Next, install one of the two plugin sets:
/plugin install document-skills@anthropic-agent-skills
/plugin install example-skills@anthropic-agent-skills
document-skills holds the four file-format skills — docx, pdf, pptx, xlsx. example-skills holds everything else: frontend-design, skill-creator, webapp-testing, mcp-builder and the rest. You can install both; they do not collide.
If you prefer menus to commands, /plugin opens the browser, where you can pick the marketplace, then anthropic-agent-skills, then the set, then Install now. Same result.
Route 2: copy the folder (npx skills)
If you are not in Claude Code, or you want one skill instead of a set, the short command is:
npx skills add anthropics/skills
This pulls the skill folders from the repository and puts them where your agent looks for skills. It is the route to use with other agents that follow the Agent Skills convention, because it does not depend on Claude Code's plugin menu existing.
Route 3: Claude.ai and the API
On paid Claude.ai plans the example skills are already available — there is nothing to install. Custom skills can be uploaded from settings, which is useful for a skill you wrote yourself with skill-creator. Through the API, Anthropic's pre-built skills and your own uploaded skills are both addressable from a request.
The part that actually decides whether it works
A skill only fires when its description matches the task. Descriptions are written by whoever authored the skill, and they are usually specific: “extract form fields from a PDF” matches, “look at this file” does not. Two things fix almost every “I installed it and nothing happened” case:
- Name the skill in the prompt. Use the pdf skill to… is unambiguous.
- Name the artefact. A file path, a format, a concrete deliverable. Skills key off the job, not the mood.
Where it usually goes wrong
- Installed the wrong set. The four document skills live in
document-skills, notexample-skills. If a PDF task falls back to generic text handling, check which set you installed. - Expecting a UI. Skills have no interface. Nothing appears in a sidebar; the only evidence is that Claude starts doing the task the way the skill describes.
- Skipping the source. These are folders of instructions and sometimes scripts. Read the
SKILL.mdof anything that touches files, credentials or code before you run it.
After you install
Go back to the skill finder and pick by task rather than by name — the two questions that matter are what you are trying to produce and whether the skill was built for that output. If you want to write your own instead of installing someone else's, start with skill-creator; if you want to know what a skill is before installing one, read what are Claude skills.