How to Install Skills in Claude Code: Every Method

A skill is a set of instructions packaged as a SKILL.md file that an AI agent reads to learn a new workflow.

Quick Answer: The fastest way to install is the one-liner curl command: mkdir -p ~/.claude/skills && curl -sL https://www.agensi.io/api/install/<slug> | tar xz -C ~/.claude/skills/. This creates the directory, fetches the skill, and unpacks it. You can also download the ZIP from the skill's page on agensi.io and unzip into ~/.claude/skills/SKILL_NAME/ (personal) or .claude/skills/SKILL_NAME/ (project-scoped). Restart Claude Code, then run /skills to confirm it loaded.

Once the directory is in place, the Claude Code skills marketplace lists every skill Claude Code can load, so you can install one and verify the setup right away.

Claude Code becomes a lot more useful once you start adding skills to it. Skills are packaged instructions that teach Claude Code, OpenClaw, and other AI agents how to handle specific tasks, from writing commit messages to reviewing code to generating documentation. The good news is that installing them takes less than a minute.

There are several ways to add skills to Claude Code. This guide walks through each method with step-by-step instructions so you can pick whichever fits your workflow.

What's the fastest way to install a skill?

Use the one-liner curl install command. From any agensi.io skill page, copy the slug and run:

mkdir -p ~/.claude/skills && curl -sL https://www.agensi.io/api/install/<slug> | tar xz -C ~/.claude/skills/

The command creates ~/.claude/skills/ if it doesn't exist, downloads the archive over HTTPS, and unpacks it in place. Restart Claude Code and run /skills to confirm.

On Windows PowerShell:

New-Item -ItemType Directory -Force -Path "$HOME\.claude\skills" | Out-Null
irm https://www.agensi.io/api/install/<slug> -OutFile skill.tar.gz; tar -xzf skill.tar.gz -C "$HOME\.claude\skills"; del skill.tar.gz

Free skills install directly. Paid skills require purchase - use the download button on the skill page after buying.

What do I need before installing skills?

Make sure Claude Code is installed and working. Open your terminal and run:

claude --version

If you get a version number back, you're good. If not, install Claude Code first by following the instructions at claude.ai/install.

Skills are stored in two places:

• Personal skills go in ~/.claude/skills/ and are available across all your projects
• Project skills go in .claude/skills/ inside a specific repo and are shared with anyone who clones it

Most of the time, you'll install to the personal directory unless you're setting up skills for a team.

How do I install skills using the plugin browser?

Claude Code has a built-in plugin system that lets you browse, install, and manage skills without leaving your terminal. This is the fastest method if the skill you want is available as a plugin.

Step 1. Start a Claude Code session in any project:

claude

Step 2. Type /plugin and press Enter. This opens the plugin browser.

Step 3. Navigate to the Discover tab. You'll see a list of available plugins from the default Anthropic marketplace.

Step 4. Find the plugin you want and press Enter to install it. Claude will ask you to choose a scope:

• User installs it for all your projects (~/.claude/skills/)
• Project installs it for the current repo only (.claude/skills/)

Step 5. That's it. The skill is now active. You can invoke it with /skill-name or let Claude load it automatically when it's relevant.

Adding community marketplaces

The default marketplace only has Anthropic's official plugins. To access community skills, add a third-party marketplace:

/plugin marketplace add author/repository

For example, to add a popular community skills collection:

/plugin marketplace add alirezarezvani/claude-skills

After adding a marketplace, its plugins show up in the Discover tab alongside the official ones.

How do I install skills from GitHub?

If a skill isn't available as a plugin, or if you prefer to manage files yourself, you can install skills by copying them into the right directory. This works for skills downloaded as zip files, cloned from GitHub, or created by hand.

Installing from a zip file

Step 1. Download the skill zip file. On Agensi, click the download button on any skill page.

Step 2. Unzip it into your skills directory:

# Personal install (all projects)
unzip code-reviewer.zip -d ~/.claude/skills/

# Project install (current repo only)
unzip code-reviewer.zip -d .claude/skills/

Step 3. Verify the folder structure looks right:

ls ~/.claude/skills/code-reviewer/

You should see at least a SKILL.md file. Some skills also include scripts/, references/, or assets/ folders.

Step 4. Start a new Claude Code session. Claude will automatically detect the new skill.

Installing from GitHub

Step 1. Clone the repository:

git clone https://github.com/author/skill-name.git

Step 2. Copy the skill folder (not the whole repo) to your skills directory:

cp -r skill-name ~/.claude/skills/skill-name

If the repo contains multiple skills in subdirectories, copy just the one you want:

cp -r repo-name/skills/code-reviewer ~/.claude/skills/code-reviewer

Step 3. Start a new session and the skill will be available.

Verifying an install

After installing any skill, you can check that Claude recognizes it. Start a session and type:

/skill-name

If the skill loads, you'll see Claude acknowledge it and follow the skill's instructions. If nothing happens, double check that the SKILL.md file is in the right location and that the folder is directly inside ~/.claude/skills/ (not nested an extra level deep).

How do I install skills from Agensi?

Agensi is a marketplace for curated, security-reviewed SKILL.md skills. Every skill goes through an automated 8-point security scan before it goes live, so you know what you're installing has been inspected.

Step 1. Browse skills at agensi.io/skills. Filter by category, price, or popularity.

Step 2. Click on a skill to see its detail page. Check the description, tags, and security scan results.

Step 3. Click Download (for free skills) or Buy (for paid skills). You'll get a zip file.

Step 4. Unzip into your Claude Code skills directory:

unzip skill-name.zip -d ~/.claude/skills/

Step 5. Start a new Claude Code session. Done.

Agensi skills work with Claude Code out of the box, but most are also compatible with Codex CLI, Cursor, Gemini CLI, and other agents that support the SKILL.md format. Check the compatibility info on each skill's page.

How do I manage my installed skills?

Over time you'll accumulate skills. Here are a few useful things to know:

List all installed skills:

ls ~/.claude/skills/

Remove a skill: Just delete its folder.

rm -rf ~/.claude/skills/skill-name

Update a skill: Replace the folder with the new version. If you bought it on Agensi, download the latest version from your dashboard. For GitHub skills, pull the latest changes.

Disable a skill temporarily: Rename the folder to something Claude won't recognize, like adding an underscore prefix:

mv ~/.claude/skills/code-reviewer ~/.claude/skills/_code-reviewer

Rename it back to re-enable.

How do I create my own skill?

You don't need to download anything. You can write a SKILL.md from scratch.

mkdir -p ~/.claude/skills/my-custom-skill/

Create the SKILL.md file with your editor:

---
name: my-custom-skill
description: Enforces our team's React component conventions
---

# React Component Standards

When generating React components:

- Use functional components with TypeScript
- Put styles in a co-located `.module.css` file
- Export components as named exports, not default
- Include a basic unit test file alongside every component
- Use our custom `useApi` hook for data fetching, never raw fetch

That's a complete skill. The frontmatter (name and description) tells Claude what the skill is for. The body contains the instructions Claude follows when the skill is triggered.

For more on writing effective skills, see How to Write a SKILL.md Description That Actually Triggers.

How do I add project-level skills for my team?

Instead of putting skills in your personal ~/.claude/skills/ directory, you can add them to a specific project:

mkdir -p .claude/skills/
cp -r ~/some-skill/ .claude/skills/

Commit this to your repo:

git add .claude/skills/
git commit -m "Add code review skill for team"

Now everyone who clones the project gets the skill automatically. This is how teams standardize AI-assisted workflows. Your frontend team can share a component generation skill. Your backend team can share an API design skill. No individual setup required.

Personal vs project skills

You can have both. Claude Code loads personal skills first, then project skills. If two skills cover the same task, both are available.

Cloning a skill straight from a repo

git clone https://github.com/user/skill-repo.git ~/.claude/skills/repo-name

If SKILL.md is not at the root of the cloned folder, move it up one level:

mv ~/.claude/skills/repo-name/src/SKILL.md ~/.claude/skills/repo-name/

The risk with GitHub skills is that they're unvetted. Check the SKILL.md content before adding it. Look for anything that asks Claude to run shell commands you don't recognize, access credentials, or make network requests.

Do the same paths work on other agents?

The process is the same everywhere, only the path differs:

Skills built on the SKILL.md standard work across all of these agents without modification.

Which skills should I install first?

If you're just getting started, here are a few skills that most developers find useful right away:

• git-commit-writer writes conventional commit messages by analyzing your staged changes
• code-reviewer reviews your code for bugs, security issues, and best practices
• pr-description-writer generates clear pull request descriptions from your branch diff
• env-doctor diagnoses why your project won't start

Browse more on the Agensi marketplace or check out the complete guide to SKILL.md if you want to understand how skills work under the hood.

Keep reading

• Claude Code Plan Mode: What It Is and How to Use It
• Claude Code Channels: Control Your Agent from Telegram and Discord