How to Add Skills to Claude
The four real ways to add skills to Claude — download from Agensi, clone from GitHub, connect the MCP server, or write your own.
Quick Answer: To add a skill to Claude, drop a
SKILL.mdfile (with optional supporting files) into~/.claude/skills/SKILL_NAME/. Claude Code, Claude Desktop, and the Claude API all read from this directory. The fastest source: download a ready-made skill ZIP from agensi.io, unzip it, and restart Claude. Verify with/skills.
Adding skills is the single highest-leverage thing you can do with Claude. A well-written SKILL.md turns a one-paragraph prompt into a permanent capability. This guide covers all three Claude surfaces — Code, Desktop, and API — and the four real ways to source skills.
Where Claude looks for skills
All Claude products read from the same location:
~/.claude/skills/
├── code-reviewer/
│ └── SKILL.md
├── git-commit-writer/
│ └── SKILL.md
└── README.md (optional)
For project-scoped skills committed to a repo, use .claude/skills/ instead.
Method 1: Download from Agensi
Go to agensi.io/skills, pick a skill, click Download, then:
unzip code-reviewer.zip -d ~/.claude/skills/
Every Agensi skill goes through an 8-point automated security scan before listing.
Method 2: Clone from GitHub
git clone https://github.com/author/skill-name.git ~/.claude/skills/skill-name
GitHub skills are not vetted — read the SKILL.md and any scripts before installing.
Method 3: Connect the Agensi MCP server (Pro subscribers)
Agensi Pro subscribers skip manual installation entirely. Connect the MCP server at mcp.agensi.io/mcp and Claude pulls SKILL.md content on demand for every skill in your library.
Method 4: Write your own
mkdir -p ~/.claude/skills/my-skill
cat > ~/.claude/skills/my-skill/SKILL.md <<'EOF'
---
name: my-skill
description: One-sentence description of what this does and when to use it.
---
# My Skill
Instructions for Claude here.
EOF
Comparison: where each method shines
| Method | Best for | Vetted | Cost |
|---|---|---|---|
| Agensi download | Curated quality | Yes (8-point scan) | Free or one-time |
| Agensi MCP | Zero-config across projects | Yes | Pro subscription |
| GitHub clone | Bleeding-edge / experimental | No | Free |
| Write your own | Team-specific workflows | N/A | Free |
Verify the install
Inside Claude Code, run /skills. The list shows every loaded skill with name and description. Press t to sort by token cost.
Common mistakes
- Putting
SKILL.mddirectly in~/.claude/skills/instead of inside a named folder - Tabs in the YAML frontmatter (must be spaces)
- Forgetting to restart Claude Code after dropping in a new skill folder
- Identical
descriptionfields across two skills — Claude can't tell them apart
What's next
- How to install skills in Claude Code — full installation methods
- SKILL.md format reference — every frontmatter field
- Where are Claude skills stored? — paths across OS and surfaces
Frequently Asked Questions
Find the right skill for your workflow
Browse our marketplace of AI agent skills, ready to install in seconds.
Browse SkillsRelated Articles
OpenClaw Skills Directory Path
Where OpenClaw stores skills, how to share them with Claude Code, and how to verify a skill loaded.
How to Import Skills into Claude: Complete Guide
Every way to import skills into Claude Code. Download from marketplaces, clone from GitHub, use the plugin browser, or create from scratch.
4 min read
Claude Code Plugins vs Skills — What's the Difference? (2026)
Claude Code now has a plugin system AND a skills system. Here's what plugins are, how they differ from skills, and why the distinction matters for your workflow.
7 min read