How to Install Claude Skills from GitHub (2026 Guide)

Installing Claude Skills from GitHub takes five minutes once you know the folder structure. You download a repository, move it to Claude’s Skills directory (~/Library/Application Support/Claude/Skills/ on macOS, %APPDATA%\Claude\Skills\ on Windows, ~/.config/claude/skills/ on Linux), restart the app, and toggle the skill on in Settings. The catch: you verify quality yourself—no centralized review means checking the code for security issues and testing compatibility with your Claude version.

GitHub hosts community-built skills that solve problems the official Marketplace does not cover. Company-specific API integrations, experimental automation workflows, and niche data parsing tools rarely pass Anthropic’s approval process. Installing from source gets you these tools immediately.

Three Requirements: Claude Pro, Desktop App 2.4+, File Navigation

Skills do not work on Claude’s free tier as of March 2026. You need a Pro or Team subscription. The desktop app (version 2.4 or later on macOS/Windows) or web interface at claude.ai must have Skills enabled in account settings—check Settings → Skills to confirm the toggle exists.

You will download files and place them in a hidden system folder. No coding required, but you need to open Terminal or Command Prompt for dependency installation on some skills. If you have never used cd to navigate directories, budget 20 minutes to learn basic commands.

GitHub Repository Anatomy: skill.json, Entry Point, README

A working Claude Skill repository contains skill.json in its root directory—this manifest declares the skill’s name, version, required permissions, and entry point file. The entry point is either main.py (Python) or index.js (JavaScript), the two languages Claude supports as of mid-2026. The README.md explains functionality, lists dependencies, and shows usage examples.

Quality repositories include requirements.txt (Python) or package.json (JavaScript) listing external libraries. A tests/ folder signals the developer wrote validation checks. An examples/ folder with sample inputs clarifies what the skill expects.

Repositories without skill.json are not installable—Claude recognizes skills only by that manifest. Loose Python scripts with no packaging structure will not load.

Step 1: Check Stars, Commits, Issues, and Code Before Downloading

Star count and fork count give rough popularity signals. A repository with 12 stars in a narrow category (e.g., “Notion API sync”) may be more useful than a 200-star general tool if it solves your exact problem. Check the commit history—click “Commits” near the top—to see if the developer maintains it. A skill untouched since January 2026 may not work with Claude’s current API.

Read the Issues tab. Open issues titled “skill fails to load” or “permission errors” are red flags. Look for developer responses—a repo with 15 open issues and zero replies is abandoned. Closed issues with solutions show active support.

Scan the README for “Tested with Claude version” notes. Skills built for Claude 1.x often break on 2.x due to API changes. If the README omits compatibility information, assume it works only if the last commit is recent—within the past three months.

Scroll through main.py or index.js. You do not need to audit every line. Look for hardcoded API keys (a security mistake), os.system() calls executing shell commands without validation, or network requests to unfamiliar domains. Well-written skills use environment variables for secrets and include comments explaining functions.

Step 2: Download ZIP, Extract, Rename Folder to Match skill.json

Click the green “Code” button on the repository page, then “Download ZIP”. This downloads the entire repository as a compressed folder. On Windows, right-click the ZIP and choose “Extract All”. On macOS, double-click it.

You get a folder named something like email-summarizer-main (GitHub appends the branch name). Rename it to match the skill’s actual name from skill.json—open that file in a text editor and find the "name" field. If it says "name": "email_summarizer", rename the folder to email_summarizer. Underscores and lowercase matter; Claude’s skill loader is case-sensitive on Linux and macOS.

Step 3: Run pip install -r requirements.txt or npm install (If Needed)

If the skill includes requirements.txt, you need Python 3.9 or later. Open Terminal (macOS/Linux) or Command Prompt (Windows), navigate to the skill folder using cd, and run:

pip install -r requirements.txt

For JavaScript skills with package.json, you need Node.js 18 or later. Run:

npm install

This downloads libraries into a node_modules or site-packages subfolder. Skills without these files have no external dependencies—skip this step.

The most common error: “pip not found” or “npm not found”. That means Python or Node.js is not installed. Download from python.org or nodejs.org, install, restart your terminal, try again.

Step 4: Copy Skill Folder to ~/Library/Application Support/Claude/Skills/ (macOS)

Claude reads skills from a specific folder:

• macOS: ~/Library/Application Support/Claude/Skills/
• Windows: %APPDATA%\Claude\Skills\
• Linux: ~/.config/claude/skills/

If the Skills folder does not exist, create it manually. Copy your renamed skill folder (the one containing skill.json) into this directory. The structure should look like:

Skills/email_summarizer/skill.json
Skills/email_summarizer/main.py
Skills/email_summarizer/README.md

Do not nest it deeper—Skills/email_summarizer/email_summarizer/skill.json will not load.

Step 5: Quit Claude (Cmd+Q on macOS), Relaunch, Toggle Skill in Settings

Quit Claude completely. On macOS, press Cmd+Q. On Windows, right-click the system tray icon and choose Exit. Relaunch the app. Open Settings → Skills. If installation worked, your skill appears with a toggle switch. Turn it on.

If it does not appear, check Claude’s log file. On macOS, open Console.app and filter for “Claude”. On Windows, logs live in %APPDATA%\Claude\logs\. Look for lines mentioning your skill’s name—common errors include “missing required field in skill.json” (malformed manifest) or “module not found” (dependencies did not install).

When a Skill Stops Working After a Claude Update

Anthropic changes the Skills API every few months as of 2026. Developers do not always keep pace. If a previously working skill suddenly fails, check the GitHub repository for a newer version—the developer may have pushed a compatibility fix.

If the repo has not updated in three months and the skill is broken, check the Issues tab for reports from other users. Sometimes another user posts a working fork (a modified copy). The original README often links to active forks if the maintainer abandoned the project.

Disable the skill in Claude’s settings without deleting files. That keeps it installed but inactive, useful if you want to wait for a fix without losing your setup.

Edit main.py or index.js to Change Prompts, Settings, Logging

Every file in the skill folder is editable. Open main.py or index.js in any text editor (VS Code, Sublime, Notepad) and change the code. Common modifications: adjusting prompt templates the skill uses, changing default settings in skill.json, adding logging statements to debug behavior.

After editing, restart Claude for changes to take effect. The app does not hot-reload skills—it reads them once at launch.

Save a backup copy of original files before editing. Syntax errors can break the skill. If your changes cause Claude to crash on startup, delete the skill folder, restore the backup, restart.

Search “claude skill” site:github.com in Google, Filter by Past Year

GitHub’s search is mediocre for this. Search "claude skill" site:github.com in Google—it surfaces repositories with those terms in the README. Filter results by date (past year) to avoid outdated projects.

Three repositories aggregate curated lists as of September 2026: awesome-claude-skills, claude-community-skills (includes compatibility tags), and anthropic-unofficial-skills (focuses on business automation). These are not official Anthropic projects—they are community-maintained indexes. Star counts and last-update dates vary; check each repository’s commit history to confirm it is actively maintained.

Reddit’s r/ClaudeAI subreddit has a monthly “Share Your Skills” thread where developers post new releases. Discord servers for AI automation (like the “LLM Builders” community) have channels dedicated to Claude Skills with install help.

Marketplace: One-Click, Vetted, Slow Approval vs. GitHub: Manual, Unvetted, Immediate

The official Skills Marketplace vets every skill for security and reliability. Installation is one-click. Updates happen automatically. But approval takes weeks, and Anthropic rejects skills that duplicate existing functionality or target narrow use cases. As of September 2026, the Marketplace approval process is not publicly documented with specific timelines.

GitHub skills install in five minutes but require manual updates and your own quality judgment. For experimental workflows or company-specific integrations, GitHub is often the only option. For general-purpose tools (calendar sync, email drafting), check the Marketplace first—if it exists there, the official version is stabler.

Regulated Industries, Terminal Aversion, Business-Critical Workflows: Use Marketplace Only

If you work in healthcare, finance, or legal sectors, your IT policy may prohibit running unvetted code that interacts with company data. Check with your security team before installing any GitHub skill on a work machine.

If you are uncomfortable opening a terminal or do not know how to navigate hidden folders on your operating system, stick to the Marketplace. The manual install process is not complex, but it assumes you can follow file path instructions without screenshots.

If you need guaranteed uptime for a business-critical workflow, do not depend on a solo developer’s GitHub repo. Community skills have no SLA, no support contract, and can vanish if the maintainer deletes their account.

Frequently asked questions

What are Claude Skills and why would I install them from GitHub?

Claude Skills are add-ons that teach Claude new capabilities—automating email responses, parsing CSV files, integrating with project management APIs. GitHub hosts community-created skills that solve niche problems or experimental features not in Anthropic’s official Marketplace. Installing from GitHub gets you specialized tools immediately, though you handle quality checks yourself. As of 2026, GitHub remains the primary source for business-specific automation skills that target narrow use cases.

Do I need coding experience to install Claude Skills from GitHub?

No programming required, but you need comfort with file systems. The process involves downloading a ZIP, moving folders to ~/Library/Application Support/Claude/Skills/ (macOS) or %APPDATA%\Claude\Skills\ (Windows), and occasionally running pip install -r requirements.txt to install dependencies. If you have ever manually installed a browser extension from a file or moved documents into a hidden system folder, you have the necessary skills. Reading a README and following step-by-step instructions is the main requirement.

What’s the difference between the Claude Skills Marketplace and GitHub repositories?

The Marketplace offers one-click installs, automatic updates, and Anthropic’s security review—every skill is vetted before publication. GitHub repositories are community-maintained, require manual installation, and receive no official oversight. Marketplace skills are stabler; GitHub skills are more experimental and specialized. As of September 2026, the Marketplace and GitHub each host hundreds of skills, but GitHub includes many narrow business workflows that would not pass Anthropic’s approval process.

How do I find reliable Claude Skills on GitHub?

Check four indicators: recent commits within the past three months show active maintenance, closed issues with developer responses indicate support, a detailed README with version compatibility notes signals professionalism, and test files plus example usage demonstrate higher quality. Scan the code for hardcoded passwords or unexplained network requests. Community-curated lists like awesome-claude-skills filter for reliability, though you should still verify the last commit date on any repository before installing.

Can I modify GitHub Claude Skills after installing them?

Yes, every file is editable. Open the skill’s Python or JavaScript file in any text editor to adjust prompts, change default settings in skill.json, or add functionality. Changes take effect after restarting Claude—the app does not reload skills while running. Save backup copies before editing, since syntax errors can prevent the skill from loading. This is useful for tweaking behavior to match your workflow or fixing compatibility issues the original developer has not addressed.

Photo by REINER SCT on Pexels