HavenSkills

Official Anthropic Skills for Claude

Explore the six skills maintained in Anthropic’s official examples repository — and what they are a good reference for.

Skills
6 skills
Full write-ups
6

How to choose

Choose by output type for office work, or use skill-creator to develop an instruction set for your own workflow.

Filter

All skills in this category

frontend-design

Create a distinct interface and implement its layout, type and visual styling.

by anthropics Skill guide
npx skills add anthropics/skills --skill frontend-design
Author
anthropics
Repo
GitHub
Write-up
Read →

skill-creator

Write a skill, design eval cases and refine activation based on results.

by anthropics Skill guide
npx skills add anthropics/skills --skill skill-creator
Author
anthropics
Repo
GitHub
Write-up
Read →

pptx

Build and edit PowerPoint presentations with editable slide objects.

by anthropics Skill guide
npx skills add anthropics/skills --skill pptx
Author
anthropics
Repo
GitHub
Write-up
Read →

pdf

Extract, combine, reorder and fill PDF files.

by anthropics Skill guide
npx skills add anthropics/skills --skill pdf
Author
anthropics
Repo
GitHub
Write-up
Read →

docx

Create and edit Word documents with review markup.

by anthropics Skill guide
npx skills add anthropics/skills --skill docx
Author
anthropics
Repo
GitHub
Write-up
Read →

webapp-testing

Exercise browser flows and report visible behavior on a running application.

by anthropics Skill guide
npx skills add anthropics/skills --skill webapp-testing
Author
anthropics
Repo
GitHub
Write-up
Read →

What the official Anthropic skills are

This page is the short list of what Anthropic itself ships in anthropics/skills. That matters for one practical reason: these are the skills whose behaviour the model was trained around, so they tend to be the ones that work without much prompting. Everything else on this site — community skills, third-party packages — is judged against them.

There are six here, and they answer two different questions.

By output type

  • frontend-design — a distinct interface, plus the layout, type and visual styling that carries it. The useful part is the opinion: it picks a direction instead of producing a neutral grid.
  • pptx, pdf, docx — the three file formats. Decks with editable slide objects, PDF extraction and form filling, Word documents with review markup. The format pages on this site go deeper on each.

By capability

  • skill-creator — write a skill, design eval cases, then refine activation based on results. This is how you turn a workflow you keep repeating into something the agent does without being re-taught.
  • webapp-testing — exercise browser flows against a running application and report visible behaviour. It is the official counterpart to the community browser CLIs.

Where these skills break in practice

  • Expecting a finished page from frontend-design. It gives a direction and the styles to express it; it does not load fonts or wire up your app.
  • Skipping the eval stage in skill-creator. A skill without eval cases gets “improved” in whatever direction the last conversation went.
  • Testing on a dead server. webapp-testing needs the app running. Pointed at a stopped process it reports connection errors as findings.
  • Assuming the file skills beat community ones. For common formats the official skills are the safest baseline; for specific workflows a specialised skill can be sharper. Compare on your own sample file.
  • Installing all six. Each installs separately. Formats you never deliver just add surface area.

The check that catches most of it

  1. Try the skill on one real file or page before trusting it on ten. The official skills are general; your edge cases are not.
  2. For skill-creator, check that the eval cases fail before the skill exists. An eval that passes with no instructions is measuring nothing.
  3. For frontend-design, ask what the typographic direction is. If the answer is a list of fonts with no argument, the direction was skipped.
  4. For webapp-testing, start the app yourself first and confirm the URL responds before the run.

Which page to read next

Agent workflow covers skill-creator, webapp-testing, claude-api and mcp-builder in depth — the four skills about building and running agents rather than producing files. Design and UI covers frontend-design alongside the community design skills.

What makes these different from the rest of the directory

Most skills in this directory are one person's way of doing one job. These six are different: they come from the repository Anthropic publishes as examples, which means they are also the format every other skill copies — a folder, a SKILL.md, a name and a description the model reads before it decides to activate. That makes them a good starting point even if you never install them: reading how frontend-design describes itself teaches you what a usable description looks like. The trade-off is scope. Each one does a broad, general job rather than a narrow one you can drop into an existing workflow, and none of them knows anything about your project. Treat them as reference implementations you can adapt, not as finished tools. If you only ever install one, make it skill-creator: it is the skill for writing the next skill.

How to check the result

Open the skill's SKILL.md and read the description line first: it is the text the model matches against your request, and a vague one is why a skill never activates. Then run it on a sample file you already know the answer for — a two-page PDF, a six-slide deck, a small component you have reviewed before. Compare the output with what you would have accepted from a person. frontend-design is the one to watch: it names a typeface and a palette but does not install them, so a page can follow its advice and still render in the browser's default font. Load the font yourself and look again before you judge it.

Frequently asked questions

How do I install one of these Anthropic skills?

Use the command beside the skill, then reload the agent and confirm it can see the skill in your project. The folder must end at SKILL.md: ~/.claude/skills/name/SKILL.md, where name is the skill's own folder. An extra folder on top of that path is the most common reason a skill never appears.

Are these the official skills, or a copy?

The six skills on this page come from Anthropic’s public anthropics/skills repository. The same repository includes additional examples. Check the repository history for current behavior and maintenance.

Which one should I read first?

Start with the format you deliver most often, such as docx, xlsx or pdf. For web pages, try frontend-design. For authoring your own skill, use skill-creator to draft a SKILL.md, design evaluation cases and refine when the skill activates.

Do these skills work outside Claude Code?

Other agents that support SKILL.md can load these instructions. Activation, available tools and results depend on the client. Check the client’s documentation for supported behavior.

How is this different from the community skills?

Provenance. These come from Anthropic; the rest come from individuals and companies. Judge both on the same sample of your own work.

Why does webapp-testing report errors instead of pages?

The application was not running. Start it, confirm the URL, then run the skill.