What Claude Skills actually are (and why GitHub matters)
A Claude Skill is just a folder. Inside it, you'll find a file called SKILL.md — a plain text file with instructions that tell Claude how to do something specific, like format a spreadsheet a certain way or follow a brand's writing style. Sometimes the folder also has a scripts/ subfolder with small helper scripts, or reference files Claude can pull from. When the task matches what's in the Skill, Claude loads it and uses those instructions.
Here's the part that trips people up: there's no app store for Skills. Most of the ones worth using live in public GitHub repositories, shared by other builders. That means "installing" a Skill isn't a one-click action — it's more like downloading a recipe card and handing it to Claude yourself. You'll be copying files, not clicking "add to library." It's simple once you've done it, but it's manual. Set that expectation now and the rest of this walkthrough will make a lot more sense.
What you need before you start
You don't need to know how to code to do this. Here's the actual checklist:
- A Claude.ai account — Skills currently work on Pro, Team, and Enterprise plans, or through Claude Code. The free tier doesn't support custom Skills yet, so check your plan before you start downloading anything.
- A GitHub account — not strictly required. You can view and download files from public repos without logging in. But having an account makes navigating GitHub easier, and you'll need one eventually if you start saving or forking Skills.
- A way to view files — a code editor like VS Code is nice, but a basic file browser works fine too. You're mostly just opening text files and uploading folders, not writing code.
Anatomy of a Skill folder: what you're actually downloading
Before you install anything, it helps to know what's inside the folder you're grabbing. A typical Skill repo looks like this:
SKILL.md— the core file. It has a name, a short description, and the actual instructions Claude reads to understand what the Skill does and when to use it.scripts/(optional) — small helper scripts the Skill might run, like a Python file that processes data a specific way.- Reference files (optional) — templates, examples, or extra context the Skill points to when it needs more detail.
Here's why this matters: SKILL.md is just text. Nothing hidden, nothing compiled. Before you hand a Skill to Claude, open that file and actually read it. You're trusting these instructions to shape how Claude behaves — so take the two minutes to see exactly what you're giving it, the same way you'd skim a recipe before cooking it for guests.
Step 1: Find and vet the skill repo
Let's use a real example: Anthropic's own anthropics/skills repository on GitHub. Open it up and you'll see a list of folders, each one a separate Skill — things like pdf or pptx for working with specific file types. Click into one, and start with the README if there is one. It should tell you in plain language what the Skill does and why it exists.
Then open SKILL.md itself. A trustworthy one reads like this: a clear name, a one-sentence description of when Claude should use it, and a numbered list of instructions you could follow yourself by hand. A vague one looks like three sentences of marketing copy with no real steps — that's a sign the author didn't test it, or worse, copied it from somewhere without checking.
Watch for red flags in any scripts/ folder too: calls to external APIs, requests to paste in API keys, or code that reaches out to a URL you don't recognize. A Skill that just formats text or reads local files is low-risk. One that phones home is worth a second look before you trust it.
Step 2: Download the skill files to your computer
[Screenshot: GitHub repo page with the green "Code" button highlighted]
If the repo is just one Skill, click the green Code button, then Download ZIP. GitHub hands you the whole repo as a compressed file — unzip it, and you'll have the Skill folder with SKILL.md inside.
If the repo bundles multiple Skills (like anthropics/skills does), downloading the whole thing means digging through folders you don't need. In that case, use git clone in your terminal to pull the repo, then just copy the one subfolder you want — say, pdf/ — somewhere else on your computer. You can delete the rest.
[Screenshot: terminal showing a git clone command, followed by a file browser with the single skill folder isolated]
Either way, the end goal is the same: one folder, on your machine, containing SKILL.md and whatever else belongs to that Skill.
Step 3: Install it into Claude.ai (web)
In Claude.ai, go to Settings, then look for Capabilities (Anthropic has moved this around before, so if you don't see it right away, check under your profile menu or a "Skills" tab directly). You're looking for an Upload Skill or Add Skill button.
[Screenshot: Claude.ai Settings page with Capabilities/Skills section circled]
Here's where it gets a little fiddly. Depending on when you're reading this, the upload step may want a zipped folder, not a raw folder — so you might need to re-zip just that one Skill folder you isolated in Step 2, not the whole repo. Select it, confirm, and Claude will parse the SKILL.md inside.
[Screenshot: Upload dialog with a zipped skill file selected]
A few honest caveats: Skills are still rolling out gradually, so if you're on a Pro plan and don't see the option at all yet, that's likely why — not something you're doing wrong. There are also size limits on uploads, so a Skill with a lot of reference files or large scripts may get rejected; if that happens, check whether the repo's README mentions trimming it down. And occasionally the UI changes labels between when I'm writing this and when you're reading it. If a button name doesn't match exactly, look for anything that says "Skill" or "Capability" — the concept stays the same even when Anthropic reshuffles the menu.
Step 3b: Installing into Claude Code or Claude Desktop instead
If you're using Claude Code, skip the ZIP dance entirely. Drop the Skill folder straight into ~/.claude/skills/ (on Mac/Linux) or the equivalent path on Windows. No upload button, no parsing delay — just a folder in the right place.
Restart Claude Code (or Claude Desktop) so it rescans that directory. Then run /skills or check the capabilities list in settings — your Skill's name should show up, pulled straight from SKILL.md.
This path is worth it even if you're not a developer by trade: editing a Skill means opening a text file and saving it, then restarting. Compare that to re-zipping and re-uploading every time you tweak a line. If you plan to customize a Skill at all, do it here first.
Step 4: Confirm the skill is actually working
Don't assume it loaded — test it immediately. Open a new chat and give Claude a prompt that should obviously trigger the Skill. If it's a meeting notes formatter, paste in a messy block of notes and ask Claude to format them. A working Skill responds using the exact structure defined in SKILL.md — specific headers, a particular order, maybe a summary line it wouldn't add on its own.
If Claude ignores the structure, answers generically, or says it doesn't have that capability, the Skill didn't load — check the file path or re-upload. This matters because failures here are silent. Claude won't throw an error. It'll just quietly answer like the Skill doesn't exist, and you won't notice until you're relying on it mid-task.
Free skill to practice with: Meeting Notes Formatter
To actually try this, grab the Meeting Notes Formatter skill — free, open, no signup. It takes raw, messy meeting notes and turns them into a consistent format: attendees, decisions made, action items with owners, and open questions. Nothing fancy, but it saves the ten minutes you'd spend manually restructuring notes after every call.
Inside SKILL.md, you'll find a short description plus five numbered steps Claude follows — the kind you could do by hand if you had to. No scripts folder, no external calls, so it's low-risk to install and inspect.
One easy customization: open the file and change the "Action Items" section to include a due-date column. Save, reload, test again. That's the whole editing loop — no code required.
Troubleshooting: common install errors and fixes
Most install failures come down to one of these five things:
- Missing SKILL.md at the root. Claude needs that file directly inside the folder, not buried in a subfolder. Check the ZIP's top level before uploading.
- Extra nested folder in the ZIP. If you zip the parent directory instead of the Skill folder itself, you end up with
folder/folder/SKILL.md— Claude won't find it. Re-zip from inside the Skill folder. - No Skills access yet. If the upload option isn't there at all, your account likely hasn't gotten the rollout. Nothing to fix — just wait or check Claude Code instead.
- Conflicting skill names. Two Skills with overlapping triggers can confuse Claude about which one to use. Disable one and test again.
- File size rejected. Trim reference files or large scripts, then re-upload.
Updating, disabling, and removing a skill
Claude doesn't watch the GitHub repo for you — if the maintainer pushes an update, you won't see it until you manually re-download and re-upload the new version (or re-copy the folder, if you're using Claude Code). There's no sync button.
To disable a Skill temporarily, toggle it off in the capabilities list — the files stay installed, Claude just stops using them. To remove it fully, delete it from that same list, or delete the folder from ~/.claude/skills/ if you installed it locally.
The security trade-off nobody mentions
Installing a Skill means letting Claude follow instructions you didn't write. That's a real trust decision, even though it's less scary than it sounds. Most Skills are just text — a SKILL.md file telling Claude how to behave. That's not arbitrary code execution. The risk goes up only if the Skill includes a scripts folder that actually runs something on your machine.
My rule: only install a Skill if you've read every file in it, or it comes from a source you already trust. A five-step markdown file takes two minutes to read. If you can't be bothered to read it, you probably shouldn't be running it.
Try this today
Download the Meeting Notes Formatter skill from this post, install it with the web method, and paste in a messy set of notes from your last call. Five minutes, start to finish — no terminal required.
Once that works, go find one more Skill on GitHub that solves something you actually deal with — PDF cleanup, commit message formatting, whatever's eating your time this week. Read the SKILL.md first. If it's short and makes sense, install it the same way.