Home / Guide

How to install Claude Code skills (three ways)

This guide shows three ways to install the 140 skills in 16 plugins in this repository: through the Claude Code plugin marketplace, by cloning the repository and running install.py, and with the npx skills command for other agents. It ends with troubleshooting and a list of what the installer does not do.

What a skill is

A skill is a folder with a file named SKILL.md. The file starts with YAML front matter that has a name and a description, followed by instructions in Markdown. The folder can also hold scripts and reference files. Claude Code reads the description to decide when a skill is relevant and loads the rest only when it is used. The same layout is the Agent Skills format, which other agents also read.

Claude Code finds skills in three places:

The folder name must be the same as the name in the front matter.

Route 1: the plugin marketplace

This is the route I recommend. In Claude Code, add this repository as a marketplace:

/plugin marketplace add basitalisandhu/claude-skills

Then install a plugin from it. The marketplace is named claude-skills, so the plugin name is followed by @claude-skills:

/plugin install aws-security@claude-skills

Replace aws-security with any plugin from the plugin list. Run /plugin to open the plugin manager and see what is installed. To refresh the catalog and pick up new versions, run:

/plugin marketplace update claude-skills

This route also loads plugin-level hooks, commands, agents and MCP servers when a plugin ships them, and it keeps ${CLAUDE_PLUGIN_ROOT} script paths working.

Route 2: clone and run install.py

Clone the repository and run the installer. It needs Python 3.10 or newer and nothing else.

git clone https://github.com/basitalisandhu/claude-skills
cd claude-skills
python3 install.py --user

--user copies every skill into ~/.claude/skills/. These flags change what it does:

CommandWhat it does
python3 install.py --projectCopies into ./.claude/skills/ of the directory you run it from
python3 install.py --listLists plugins and skills, with the name each installs as
python3 install.py --user --only <plugin>One plugin; repeat --only for more
python3 install.py --user --skill <plugin>/<skill>One skill; repeat for more
python3 install.py --user --dry-runShows what would happen and writes nothing
python3 install.py --user --forceAlso overwrites skill folders the script did not write
python3 install.py --user --prefixInstalls every skill as <plugin>-<skill>
python3 install.py --user --uninstallRemoves exactly the files the script wrote

To update, run git pull in the clone and run the same command again. The copy route installs skills only. Hooks, commands, agents and MCP servers need route 1.

Route 3: npx skills add

Other agents that read the Agent Skills format can install from this repository with the skills command line tool:

npx skills add basitalisandhu/claude-skills

On 2026-10-04 the tool found every skill in this repository. I have not tested it with every agent it supports, so check the result in the agent you use.

Skills refer to each other across plugins

Some skills point at a skill that lives in a different plugin, for example "hand this to other-skill". If you install only one plugin, that name does not exist on your machine. Install the sibling plugin as well, or give install.py several plugins: python3 install.py --user --only plugin-a --only plugin-b. The file reports/quality.md in the repository lists every cross-plugin pointer.

Troubleshooting

A skill does not show up

Check these in order:

Two skills have the same name

If two plugins ever ship a skill with the same name, the first in plugin name order installs under the plain name and the second as <plugin>-<skill> (or <plugin>-<skill>-2 if that name is taken too, so no skill ever overwrites another), and the script says so. To avoid any clash, pass --prefix and every skill installs as <plugin>-<skill>. Today every skill name here is unique, and scripts/validate.py fails the build if that changes.

If a skill folder already exists and install.py did not write it, the script skips it. Pass --force to overwrite it.

Uninstall

For the marketplace route, run /plugin uninstall <plugin>@claude-skills and, to drop the catalog, /plugin marketplace remove claude-skills. For the copy route, run python3 install.py --user --uninstall (or --project --uninstall). The script writes .claude-skills-manifest.json in the target folder and removes only the files listed there, so skills you wrote yourself stay.

What this does not do

Report a problem with a skill in the issues of its source repository, which each skill page links. Problems with the installer go to this repository's issues.