> Quick Answer: Clone the repo into `~/.claude/skills/SKILL_NAME/` (personal) or `.claude/skills/SKILL_NAME/` (project). Confirm a valid `SKILL.md` exists at the folder root, restart Claude Code, then run `/skills` to verify load. Audit the code first — GitHub skills aren't security-scanned.
GitHub is the largest source of community-built SKILL.md skills. Thousands of developers have published skills for Claude Code, OpenClaw, and other AI coding agents in public repositories. The challenge is finding good ones and installing them safely.
This guide walks through the entire process: where to search, how to evaluate a skill before installing, and the exact commands to get it running.
Where to find Claude skills on GitHub
The best starting points are:
Search GitHub directly for `SKILL.md` files. Use the query `filename:SKILL.md` in GitHub's search bar, then filter by recently updated. You'll find individual skills, skill collections, and project-specific skills that teams have published alongside their code.
Check the awesome-skill-md topic tag. Many skill authors tag their repositories, making them discoverable through GitHub's topic pages.
Browse curated marketplaces like Agensi where skills have been reviewed and security-scanned before listing. If a skill on Agensi links to its GitHub source, you can clone it directly.
How to evaluate a skill before installing
Not every skill on GitHub is safe or well-made. Before installing, check these things:
Read the SKILL.md file. Open it and look at what the skill actually does. Check for any `scripts/` folder and read those files too. Be wary of skills that make network requests, access environment variables, or run shell commands that aren't clearly related to the skill's stated purpose.
Check the repository's stars, forks, and recent activity. A skill with 50 stars and recent commits is more trustworthy than one published once and abandoned.
Look at the frontmatter. A well-written skill has a clear `name`, a specific `description` with trigger phrases, and appropriate `context` settings. Vague descriptions like "does stuff with code" are a red flag.
Installing from GitHub
Once you've found a skill you trust, installation takes three commands:
```bash
# Clone the repository
git clone https://github.com/author/skill-name.git
# Copy the skill folder to your skills directory
cp -r skill-name ~/.claude/skills/skill-name
# For OpenClaw
cp -r skill-name ~/.openclaw/skills/skill-name
# For Codex CLI
cp -r skill-name ~/.codex/skills/skill-name
```
If the repository contains multiple skills in subdirectories, copy just the one you want:
```bash
cp -r repo-name/skills/code-reviewer ~/.claude/skills/code-reviewer
```
Start a new Claude Code session and the skill is active immediately.
Installing from a GitHub URL without cloning
If you just want one skill and don't need the whole repository, you can download it directly:
```bash
# Download and extract a specific folder using git sparse checkout
git clone --no-checkout https://github.com/author/repo.git
cd repo
git sparse-checkout set skills/skill-name
git checkout
cp -r skills/skill-name ~/.claude/skills/
```
Or use `curl` to download a single SKILL.md file:
```bash
mkdir -p ~/.claude/skills/my-skill
curl -o ~/.claude/skills/my-skill/SKILL.md \
https://raw.githubusercontent.com/author/repo/main/skills/my-skill/SKILL.md
```
Keeping skills updated
GitHub skills don't auto-update. To get the latest version:
```bash
cd ~/path-to-cloned-repo
git pull
cp -r skill-name ~/.claude/skills/skill-name
```
If you installed many skills from different repos, consider writing a simple shell script that pulls updates for all of them.
Troubleshooting
If Claude Code doesn't recognize your skill after installing, check these common issues:
The SKILL.md file must be directly inside the skill folder, not nested deeper. The path should be `~/.claude/skills/skill-name/SKILL.md`, not `~/.claude/skills/skill-name/subfolder/SKILL.md`.
The frontmatter must be valid YAML between `---` markers. Even a small formatting error can prevent Claude from loading the skill.
The `description` field must match what you're asking Claude to do. If the description says "use for code review" but you're asking for "review my code," the skill should trigger. If it says "use for Java code review" and you're working in Python, it won't.
Start a fresh Claude Code session after installing. Skills are loaded at session startup.
A safer alternative
If evaluating GitHub skills feels like too much work, marketplaces like Agensi run automated security scans on every submission. You get the same SKILL.md skills from the community but with an extra layer of review. Most Agensi skills also link to their GitHub source if you want to inspect the code yourself.
---
*Browse security-scanned SKILL.md skills for Claude Code, OpenClaw, and other AI agents on Agensi.*
For security-scanned alternatives to GitHub, browse the Agensi skill marketplace where every skill passes an 8-point security review.
