skillsrun

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:

  1. Name the skill in the prompt. Use the pdf skill to… is unambiguous.
  2. Name the artefact. A file path, a format, a concrete deliverable. Skills key off the job, not the mood.

Where it usually goes wrong

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.

Questions people actually ask

How do I know a skill is actually loaded?
Claude Code does not announce it. The sign that a skill loaded is behavioural: the model starts following the procedure without being re-taught it. You can also ask directly — “which skill are you using for this?” — and it will name the one it loaded. If nothing loads, the usual cause is that the skill's description did not match how you phrased the task; name the skill explicitly once.
Do I have to use the plugin marketplace?
No. The plugin route adds a tested bundle of skills to a specific tool. For one skill you can also point Claude at the folder's SKILL.md, or upload a custom skill in Claude.ai on a paid plan. The plugin is just the least error-prone way to get all of them at once.
Why does the source repository matter so much?
Because a skill is instructions and sometimes scripts, not a sandbox. One that reads files or runs code can touch whatever you give it access to. Install skills from repositories you trust, read the SKILL.md before the first run, and try anything that writes files on a copy of the data first.
What is npx skills add anthropics/skills?
It is the short version: skills.sh describes itself as a directory for agent skills and installs them for whichever agent you use by copying the skill folders rather than registering a plugin. Same SKILL.md files, fewer moving parts, no Claude Code plugin menu.