You are currently viewing Claude Code Skills: The Complete Official List

Claude Code Skills: The Complete Official List

Claude Code Skills: The Complete Official List

Anthropic publishes nineteen Agent Skills. That is the whole official set, and it is smaller than most lists you will find, because most lists pad the number with community repositories and count them as if they shipped with the product. This is the official nineteen, grouped, with the word count of each instruction file and a link to the raw file so you can read one before you install it.

The community collections are real and some of them are good. They are further down, kept separate, because the install route is different and so is who supports them when something breaks.

The 19 official skills

SkillGroupPluginWhat it doesSize
xlsxDocumentsdocument-skillsReads, writes and reformats spreadsheets, including formulas and charts1,312 words
docxDocumentsdocument-skillsCreates and edits Word documents, including tracked changes and comments980 words
pptxDocumentsdocument-skillsBuilds and edits PowerPoint decks from content you supply3,129 words
pdfDocumentsdocument-skillsExtracts text and tables, merges, splits, fills forms and runs OCR1,010 words
canvas-designDesign and visualexample-skillsProduces original posters and visual art as PNG or PDF1,749 words
algorithmic-artDesign and visualexample-skillsGenerates algorithmic art in p5.js with seeded randomness2,715 words
frontend-designDesign and visualexample-skillsGuidance for designing a UI that does not look generic1,516 words
theme-factoryDesign and visualexample-skillsApplies a consistent theme across slides, docs and reports486 words
brand-guidelinesDesign and visualexample-skillsApplies a defined brand palette and typography to any artifact329 words
mcp-builderBuilding thingsexample-skillsWalks through building a production-quality MCP server1,135 words
skill-creatorBuilding thingsexample-skillsCreates, improves and measures skills, including this format5,101 words
web-artifacts-builderBuilding thingsexample-skillsBuilds multi-component HTML artifacts with modern tooling444 words
webapp-testingBuilding thingsexample-skillsDrives and tests a local web app through Playwright501 words
doc-coauthoringWriting and commsexample-skillsA structured workflow for writing documentation with you2,466 words
internal-commsWriting and commsexample-skillsWrites internal announcements, updates and memos to a house format211 words
slack-gif-creatorWriting and commsexample-skillsMakes animated GIFs sized correctly for Slack1,103 words
claude-apiReference and behaviourclaude-apiReference for the Claude API and SDK: model ids, pricing, tool use, caching14,071 words
academy-guideReference and behaviouracademy-guidePoints you at the relevant Claude Academy course for what you asked1,209 words
discernment-nudgeReference and behaviourdiscernment-nudgeAdds follow-up questions after an answer so you check it before acting1,751 words

The size column is the length of the instruction file itself. It is a rough proxy for how much the skill actually knows: claude-api at 14,071 words is a reference document, internal-comms at 211 is a short set of formats. Neither number is a quality score, but a 200 word skill and a 14,000 word skill are not the same kind of thing.

What an Agent Skill actually is

A skill is a folder with a SKILL.md inside it. The file opens with a few lines of YAML and then becomes ordinary Markdown. Claude reads the description to decide when the skill applies, then follows the body.

---
name: pdf
description: Use this skill whenever the user wants to do anything with PDF
  files. This includes reading or extracting text/tables from PDFs, combining
  or merging multiple PDFs into one, splitting PDFs apart...
---

# PDF processing
...

That is the entire format. Anthropic publishes the specification at spec/agent-skills-spec.md in the same repository.

Two consequences are worth drawing out. There is no code to run, so you can read exactly what a skill will do before you give it to an agent, which is not true of most tooling. And because the description is what triggers it, a badly written description is the usual reason a skill you installed never fires.

How to install them

The official skills install as plugins from a marketplace, not by copying files around. In Claude Code, add the marketplace once:

/plugin marketplace add anthropics/skills

Then install the bundle you want:

/plugin install document-skills@anthropic-agent-skills
/plugin install example-skills@anthropic-agent-skills

Those two cover sixteen of the nineteen. The remaining three ship as their own single-skill plugins:

/plugin install claude-api@anthropic-agent-skills
/plugin install academy-guide@anthropic-agent-skills
/plugin install discernment-nudge@anthropic-agent-skills

After installing, you use a skill by mentioning the job rather than the name. “Use the PDF skill to extract the form fields from this file” works, and so does asking for the outcome and letting the description do the matching.

Outside Claude Code

The same skills are not exclusive to the terminal. Anthropic states that these example skills are already available on paid Claude.ai plans, and that you can use the prebuilt skills or upload your own through the Claude API. So a skill you read here is portable: the file format is the same in all three places.

Which to install first

Installing all nineteen on day one is the fastest way to learn nothing about any of them. A working order that front-loads the ones that pay off immediately:

  1. document-skills, if you touch spreadsheets, decks, Word files or PDFs at all. This is the bundle that most obviously replaces manual work, and pdf and xlsx are the two most people use first.
  2. skill-creator, early rather than late. Once you have used two or three skills you will want one that does your job, and this is the skill that writes skills.
  3. claude-api, if you build anything on the API. At 14,071 words it is the largest in the set and it exists so the model stops guessing at model ids, pricing and parameters from memory.
  4. The design group, when you have a real artifact to make. These are the hardest to evaluate from a description and the easiest to judge from one output.

A caution that applies to all of them: a skill changes how the model behaves on every request where its description matches. Install a few, notice what changed, then add more. Nineteen at once and you cannot tell which one did what.

The community collections

Three repositories account for most of what people mean when they say there are hundreds of Claude Code skills. These are not published by Anthropic and are not supported by Anthropic, which does not make them bad, only different in who answers when something goes wrong.

RepositoryWhat is in itInstall
anthropics/skillsThe official nineteen above, plus the spec and a templatePlugin marketplace
coreyhaines31/marketingskillsMarketing skills: CRO, copywriting, SEO, analytics, ads, pricing, attributionClone into your skills directory
apify/awesome-skillsScraping and data-collection skills across ecommerce and social platformsClone into your skills directory

For a repository that is not a marketplace, the install is a clone into your skills directory:

cd ~/.claude/skills
git clone https://github.com/coreyhaines31/marketingskills.git

Or take a single file, which is the version to use if you care what you are running:

mkdir -p ~/.claude/skills/pricing
curl -o ~/.claude/skills/pricing/SKILL.md \
  https://raw.githubusercontent.com/coreyhaines31/marketingskills/main/skills/pricing/SKILL.md

If you want the set for one job

The official nineteen are general purpose, and the community collections are large enough that finding the handful relevant to your work is its own task. We have already done that filtering for four roles, each with the skills that map to jobs those people actually do weekly and a download link for every one:

If what you want is the agent rather than the instructions, our guide to influencer marketing AI agents covers what is worth automating and what is not.

What these are not

Three things get promised on your behalf when people write about skills, and none of them are true.

A skill is not an integration. It carries instructions, not credentials or network access. If a job needs to reach your ad account or your database, that is an MCP server, and mcp-builder exists because the two are different layers. The packaging that can carry both, plus slash commands, hooks and subagents, is a plugin: our guide to Claude Code plugins covers the official directory of 315 and how it differs from this list.

A skill is not a guarantee. It raises the floor on a task by giving the model a method instead of improvising one. It does not make the output correct, and on anything consequential you still check the work.

More skills is not better. Each one competes for the model’s attention, and a vague description fires when you did not want it. The useful collection is small and matched to what you actually do.

Frequently asked questions

How many Claude Code skills are there?

Anthropic publishes nineteen official Agent Skills, delivered as five plugins: document-skills (four), example-skills (twelve), and claude-api, academy-guide and discernment-nudge as single-skill plugins. Larger numbers you see quoted usually include community repositories, which are not published or supported by Anthropic.

How do I install Claude Code skills?

Add the marketplace once with /plugin marketplace add anthropics/skills, then install a bundle with /plugin install document-skills@anthropic-agent-skills. Community repositories that are not marketplaces are installed by cloning them into your skills directory instead, or by copying a single SKILL.md file.

Do Claude Code skills work in Claude.ai and the API?

Yes. Anthropic states the example skills are already available on paid Claude.ai plans, and that prebuilt or custom skills can be used through the Claude API. The SKILL.md format is the same in all three places, so a skill you read in the repository is portable.

What is the difference between a skill and an MCP server?

A skill is instructions, a folder with a SKILL.md that tells the model how to do something. An MCP server is a connection, giving the model access to a system or data source. A skill cannot reach your ad account or database on its own; that needs an MCP server, which is why mcp-builder exists as a skill for building one.

How do I know what a skill will do before I install it?

Read the file. A skill is Markdown with a short YAML header and no code, so the whole behaviour is visible in one document. Every skill in the table above links to its raw SKILL.md for exactly this reason, and it is the main practical advantage skills have over most tooling.

Which Claude Code skills should I install first?

Start with document-skills if you work with spreadsheets, decks or PDFs, since that is the bundle that most directly replaces manual work. Add skill-creator early, because once you have used a few you will want one for your own job. Install a handful at a time rather than all nineteen, so you can tell which skill changed what.

The official set is small enough to read in an afternoon, and that is the point of the format. Pick the three that match what you did last week, read the files, and install those. The rest will still be there.