A Claude Code skill is just a folder with a SKILL.md file inside. Installing one means putting that folder where Claude Code looks for skills. Here is exactly where that is on Windows, and how to do it in a minute.
Where Claude Code looks for skills
- Personal skills (available in every project):
~/.claude/skills/<skill-name>/SKILL.md. On Windows~is your user folder, so the path isC:\Users\<you>\.claude\skills\<skill-name>\SKILL.md. - Project skills (shared with your team through git):
.claude/skills/<skill-name>/SKILL.mdinside the project.
The folder name matters: if the skill's SKILL.md has no name field, the folder name becomes the skill name.
Install a skill from GitHub (PowerShell)
Open PowerShell and run:
New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null
git clone --depth 1 https://github.com/OWNER/REPO.git "$HOME\.claude\skills\my-skill"
Replace OWNER/REPO and my-skill. Every skill page on SkillNest shows the exact command for that skill.
When the skill is inside a bigger repository
Many repositories hold several skills in sub-folders. Clone the repository somewhere temporary and copy only the folder you need:
git clone --depth 1 https://github.com/anthropics/skills.git "$env:TEMP\anthropic-skills"
Copy-Item -Recurse "$env:TEMP\anthropic-skills\skills\pdf" "$HOME\.claude\skills\pdf"
Install a skill from a zip file
Expand-Archive .\my-skill.zip -DestinationPath "$env:TEMP\my-skill"
Copy-Item -Recurse "$env:TEMP\my-skill\*" "$HOME\.claude\skills\"
Then check the result: the file must end up at .claude\skills\<name>\SKILL.md — not one folder deeper.
macOS and Linux
mkdir -p ~/.claude/skills
git clone --depth 1 https://github.com/OWNER/REPO.git ~/.claude/skills/my-skill
Check that it works
You do not need to restart. Claude Code watches the skills folders and picks up added or edited skills during the session. The one exception: if the skills folder itself did not exist when the session started, run /reload-skills.
Then either describe the task the skill is for — Claude loads skills automatically when they are relevant — or call it directly with /skill-name.
Troubleshooting
- The skill never triggers. Open
SKILL.md: the opening---must be the very first line, otherwise the frontmatter (and itsdescription) is not read. - “requires bash … Git Bash was not found”. Some skills run shell commands with
shell: bash. On Windows these need Git Bash, which comes with Git for Windows. - Wrong folder depth.
skills\my-skill\my-skill\SKILL.mdwill not load — move the inner folder up one level. - Two skills with the same name. Personal skills take precedence over project skills.
Always read a skill's files before installing it — it is code and instructions you are giving your agent. Browse options by topic in the best skills guides.