Asset 20 8 2
Does AI recommend your business? Run the free check →

Join 15,000 business owners, marketers and entrepreneurs. The Sunday newsletter you'll be annoyed only arrives once a week.

Article

Claude Skills on GitHub (2026): A Plain Tour of Anthropic's Skills Repository

Anthropic's Claude skills live on GitHub in the anthropics/skills repository at github.com/anthropics/skills. It still had 19 skill folders on 16 November 2026, the same count it held when I checked on 30 October 2026, alongside a spec folder and a starter template. You don't have to download anything to use most of them: the README says the example skills are already available to paid plans in Claude.ai, and Claude Code users can install them as plugins with two commands.

If you came to Claude for job hunting rather than skills, start with Claude Prompts for Job Applications and Cover Letters.

Open github.com/anthropics/skills and the root shows seven items: a .claude-plugin folder, .gitignore, README.md, THIRD_PARTY_NOTICES.md, and the skills, spec and template folders. Below them, GitHub displays the README. Every skill is just a folder with a SKILL.md file inside. Here's what's in it, which parts matter to a business owner, and how to get a skill from GitHub into Claude without touching anything you don't understand.

What's in the anthropics/skills repository

GitHub's own one-line description is "Public repository for Agent Skills". The latest commit, on 14 November 2026, was titled "Update docx, pptx, xlsx, and pdf skills", so the document skills are still being worked on. Three of the root items are the folders you'll use. skills holds the skills themselves. spec holds the Agent Skills specification, the open format these files follow. template holds a starter skill you can copy. The README groups the skills into Creative and Design, Development and Technical, Enterprise and Communication, and Document Skills.

Folder or skillWhat it holdsLicence note
skills/docx, pptx, xlsxThe Word, PowerPoint and Excel skills that power Claude's document featuresOpen source (Apache 2.0), per the README
skills/pdfExtracting, merging, splitting, filling forms and OCR for PDFsFrontmatter says "Complete terms in LICENSE.txt"; that file is the Apache License 2.0
skills/internal-comms, doc-coauthoringTeam updates, newsletters, proposals and specsRead the LICENSE.txt in the folder
skills/brand-guidelines, theme-factory, canvas-designBranding, themes and static visualsRead the LICENSE.txt in the folder
skills/skill-creatorBuilds and tests new skills, about 33 KB of instructionsRead the LICENSE.txt in the folder
skills/mcp-builder, webapp-testing, claude-apiDeveloper tools for servers, web app tests and the Claude APIRead the LICENSE.txt in the folder
specThe Agent Skills specificationCovers the format, not a single skill
templateA minimal starter skillCopy it as your starting point

The full list of 19, rechecked on 16 November 2026, is academy-guide, algorithmic-art, brand-guidelines, canvas-design, claude-api, discernment-nudge, doc-coauthoring, docx, frontend-design, internal-comms, mcp-builder, pdf, pptx, skill-creator, slack-gif-creator, theme-factory, web-artifacts-builder, webapp-testing and xlsx.

Licences: what you can and can't reuse

The README says many skills in the repository are open source under Apache 2.0, and that the four document skills, docx, pdf, pptx and xlsx, are open source under Apache 2.0 as well. If an older guide tells you those four are off limits, it's out of date. Anthropic shares them as a reference for complex skills that are used in a production AI app, which makes them the best examples in the repository to learn from.

Here's how to confirm a licence yourself, using pdf. Open skills/pdf/SKILL.md and look at the frontmatter at the top: the licence line reads "license: Complete terms in LICENSE.txt". Open LICENSE.txt in the same folder and you'll see the Apache License 2.0. Do that for any skill you plan to reuse in something you sell, because the licence lives with each folder, not in the README. If you're bundling code from the repository into a product, read THIRD_PARTY_NOTICES.md in the root as well.

The README also carries a disclaimer: the skills are for demonstration and educational purposes only, and the behaviour you get from Claude may differ from what's in the repository. Treat the GitHub versions as worked examples, and test anything before you rely on it for client work.

Three ways to get a skill into Claude

The README gives a route for each place you might use Claude. Anthropic's help article on using skills in Claude fills in the menus, and the paths below were checked against it on 16 November 2026.

  1. Claude.ai and the desktop app. The example skills are already available to paid plans. You manage them in Customize > Skills, so most people never need GitHub at all. To use a skill from the repository, or your own edited copy, download the skill folder and ZIP it, then go to Customize > Skills, click the "+" button, choose Create skill, then Upload a skill. If Skills doesn't appear, the help article says code execution must be switched on in Settings > Capabilities, because skills run in the code execution environment.
  2. Claude Code. Register the repository as a plugin marketplace with /plugin marketplace add anthropics/skills. Then select Browse and install plugins, select anthropic-agent-skills, choose document-skills or example-skills, and select Install now. The direct install commands below do the same thing in one line each. After that, you use a skill just by mentioning it; the README's own example asks Claude Code to "Use the PDF skill to extract the form fields from" a PDF, with the file's path at the end. My pick for most business owners is document-skills, since Word, PowerPoint, Excel and PDF files are where the everyday work sits.
  3. The Claude API. Developers can call Anthropic's pre-built skills (pptx, xlsx, docx and pdf) or upload custom skills through the Skills API. The README sends developers to the Skills API quickstart in Anthropic's docs for both.

Copy these commands

/plugin marketplace add anthropics/skills
/plugin install document-skills@anthropic-agent-skills
/plugin install example-skills@anthropic-agent-skills

Plugins are how Claude Code packages skills for sharing, and the same idea now reaches the chat app too; my guide to Claude plugins explains how they bundle skills with connectors. Some repository skills, such as doc-coauthoring and skill-creator, are written to start fresh helper agents when they run in Claude Code, which is where Claude Code subagents come in.

Which folders to open first

If you're not a developer, open a SKILL.md file directly on GitHub and read it like a recipe. Start with the frontmatter at the top: the name, the description that tells Claude when to use it, and the licence line. Then read the body. internal-comms is a good first read because it's short: it lists the message types it handles, then tells Claude to load a different guideline file from its examples folder for each one. Next, open the template folder to see the bare minimum a skill needs. Leave the long developer skills for later, or for never.

Work with me

Want AI doing the heavy lifting in your marketing?

I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.

The one skill in the repository that's about making skills, rather than documents or designs, is skill-creator. Its SKILL.md runs to about 33 KB and covers test prompts, evaluations and tuning a skill's description so Claude uses it at the right time.

Check a skill before you enable it

Skills can run code, so Anthropic's help article says to install skills only from trusted sources, and to review anything from a less-trusted source before enabling it, including a skill a colleague shares. A skill from a fork or a third-party repository carries its own terms and its own risks, even when it looks identical to Anthropic's. Before enabling one:

  1. Check whose repository it came from. anthropics/skills is Anthropic's; a copy elsewhere isn't.
  2. Read every file in the folder, not just SKILL.md. The Help Center says to pay attention to code dependencies and bundled resources like images or scripts.
  3. Look for any instruction to connect to an untrusted network source, or for network calls that don't match what the skill says it does.
  4. Read the folder's LICENSE.txt if you plan to reuse or adapt the skill.
  5. Open the folder's History on GitHub to see when it last changed and what the commit says. On 14 November 2026, for example, docx, pptx, xlsx and pdf were updated together in one commit, so a copy you downloaded before that is already behind.
  6. Test it on work that doesn't involve client data first.

For the background on the company behind anthropics/skills, my longer write-up is my explainer on anthropic.

My take on the repository

I'd browse the repository for ideas and patterns, then install anything you want through the directory inside Claude, where it's one click. Skip cloning or downloading the repository unless you use Claude Code; for everyone else, GitHub is a reading room, not a shop. If you're curious about the spec folder and why the same skill format works beyond Claude, my explainer on Agent Skills covers the open standard.

If your team wants to make sense of Anthropic's skills and decide which ones are safe and useful to adopt, that's the kind of AI enablement I help with. I run AI training and workshops for teams, and help businesses with AI enablement and workflow automation, so the busywork runs itself and people get time back. Most of that work is with SaaS marketing teams and small businesses. Here's how we can work together.

For skills from outside Anthropic's repository, and how to judge them, see Claude Skills Marketplace (2026): Where to Find Skills and Which Ones to Trust.

Frequently asked questions

Is the anthropics/skills repository official?

Yes. It's Anthropic's own repository, at github.com/anthropics/skills, and GitHub describes it as "Public repository for Agent Skills". Copies under other accounts are forks or third-party repositories and carry their own terms.

Where is the spec for Agent Skills?

In the repository's spec folder, which holds the Agent Skills specification. The README also points to agentskills.io for the open standard itself.

How do I install the GitHub Claude skills in Claude Code?

Run /plugin marketplace add anthropics/skills, then install document-skills or example-skills, for example with /plugin install document-skills@anthropic-agent-skills.

Are the Claude skills on GitHub open source?

Yes. The README says many skills are open source under Apache 2.0, and the docx, pdf, pptx and xlsx skills are Apache 2.0 too as of 16 November 2026. Check the LICENSE.txt in each folder before reusing one.

Are skills from other GitHub repositories safe?

Only if you've checked them. Anthropic says to use skills you made or got from Anthropic, and to read every bundled file, including scripts, before enabling one from anywhere else.

Published and maintained by the Lilach Bullock team, covering marketing, AI and business growth.
Your buyers are asking AI who to use. Does it say you?

See for free whether ChatGPT, Claude, Perplexity, Gemini and Google name you, and get the plan to become the answer.

Check my AI visibility →
Sundays only

Get the Sunday newsletter.

One email a week. AI experiments, marketing tactics, and the workflows Lilach is building right now in her own business.

Subscribe free

Let’s get your marketing running on AI.

Book a free 30-minute call

We figure out what you need, where AI fits in, and what working together would look like.

Book the call →

Or take the 30-second calculator

You’ll see the hours and the money quietly leaking out of your week, and the three workflows worth building first.

Take the calculator →

Or grab the free AI resource library

Prompt packs, templates, checklists, and swipe files. The exact tools I build for paying clients. Yours, free.

Get the library →
Keep reading

More from the blog.