Last updated: 2026-11-20
The short answer
Agent skills live in GitHub repositories. You find them in three places: the publisher's own repository, a skills directory that indexes many repositories, or a search on GitHub itself.
To install one, you put the skill's folder where your agent looks for skills. You can do that with a command-line installer, which is quicker and can verify the files, or by copying the folder yourself.
Before either, read the skill's SKILL.md and check whether it ships scripts. A skill with scripts runs code on your machine.
What you are looking for
A skill is a folder with a SKILL.md file at its root. The file has a short metadata block with a name and a description, followed by instructions in Markdown. The folder may also contain scripts/, references/, and assets/.
That is the whole format. It is defined as an open specification at agentskills.io, so the same skill folder can be used by any agent that supports the format, not only Claude.
Where to find skills
1. The publisher's own repository
Many skills are published by the team that makes the tool they cover. Anthropic keeps a public repository of skills at github.com/anthropics/skills. Other companies publish skills for their own products the same way.
A repository from the publisher is the most direct source. Its limit is that you have to know it exists.
2. A skills directory
A directory indexes skills from many repositories so you can search across them. A useful one shows you, for each skill, the source repository, the license, the full SKILL.md, and the list of files, so you can judge the skill before you install it.
The SourceWeft skills directory indexes public skills from GitHub repositories. For each skill it records:
- the source repository and the exact commit the skill was scanned at
- the full
SKILL.mdand file list - the license the author chose
- whether the skill ships scripts
- notes from an automated scan, such as "makes outbound network calls"
- a trust label that says whether a SourceWeft admin reviewed it
The directory does not host the skill files. It points at the repository and commit, and its installer downloads from there.
3. GitHub search
Searching GitHub for SKILL.md or for a topic plus "agent skill" finds repositories that no directory has indexed yet. You get no screening at all this way, so read everything before installing.
Check a skill before you install it
Spend two minutes on these five checks:
- Read the
SKILL.md. The instructions are what your agent will follow. If they tell the agent to do something you would not do yourself, stop. - Look at the file list. Does the skill include scripts? Scripts are code that runs on your machine when the skill is used.
- Check the source. Is the repository from the publisher you expect? Does it have a history, or is it one commit from a new account?
- Check the license. No license means you have no clear right to reuse it at work.
- Read any scan notes. A note such as "makes outbound network calls" is not a verdict, but you should know why the skill needs it. How to check an agent skill before you install it explains what each note means.
Install with a CLI
The SourceWeft CLI installs a skill from the directory and checks every file against the hashes recorded when the skill was scanned. If a file does not match, nothing is written.
Search:
npx @sourceweft/cli skills search "pdf forms"
Inspect before installing. This prints the repository, commit, license, trust label, whether the skill ships scripts, and any scan notes:
npx @sourceweft/cli skills info <name>
Install:
npx @sourceweft/cli skills install <name>
By default the skill goes to Claude Code in your home directory. Two options change that:
--agentpicks the target agent:claude-code,codex,cursor, oruniversalfor the shared.agents/skillsdirectory that many agents read. Runnpx @sourceweft/cli skills agentsfor the full list, which also covers Gemini CLI, Windsurf, GitHub Copilot, and others, with the folder each one uses.--scope projectinstalls into the current project instead of your home directory.
Before it writes anything, the CLI shows the skill's source, license, and file count, and asks you to confirm. If the skill ships scripts, the question says so.
<name> is the install name the search prints, such as @owner/skill-name. For a step-by-step walkthrough with real output, see Install an agent skill with the SourceWeft CLI.
To see, update, or remove installed skills:
npx @sourceweft/cli skills list
npx @sourceweft/cli skills update
npx @sourceweft/cli skills remove <name>
update asks before replacing anything, because a new version can bring new scripts.
Install by hand from GitHub
You can also copy the folder yourself. This works for any skill in any repository, including ones no directory lists.
- Find the skill folder in the repository. It is the folder that contains
SKILL.md. - Pin a commit. Open the commit you reviewed and download from that commit, not from the moving default branch.
- Copy the whole folder, not only
SKILL.md. Scripts and reference files are part of the skill. - Put it where your agent looks. For Claude Code, that is
~/.claude/skills/<skill-name>/for all your projects, or.claude/skills/<skill-name>/inside one project. - Keep the folder name equal to the skill's
name. The specification requires them to match. - Start a new session and ask for something the skill covers.
Copying by hand skips any hash check, and you will not be told when the skill changes upstream. Re-review the skill whenever you update it.
CLI or by hand?
| CLI | By hand | |
|---|---|---|
| Speed | One command | A few minutes |
| Verifies files | Yes, against recorded hashes | No |
| Pins a version | Yes, to the scanned commit | Only if you do it yourself |
| Updates | skills update, with confirmation | Manual |
| Works for skills not in a directory | No | Yes |
| Warns about scripts | Yes | No |
After installing
- Test it with a small task before relying on it.
- Watch what it does the first time, especially if it runs scripts.
- Remove it if you stop using it, with
skills removeor by deleting its folder. An installed skill's description is loaded in every session.
FAQ
Where can I find agent skills for Claude?
In three places: the publisher's own GitHub repository, such as anthropics/skills; a skills directory such as the SourceWeft skills directory; or GitHub search for repositories that contain a SKILL.md.
How do I install an agent skill from GitHub?
Copy the folder that contains SKILL.md into your agent's skills directory. For Claude Code that is ~/.claude/skills/<skill-name>/. Or use a CLI installer, which does the same thing and can verify the files.
Are agent skills safe to install? Skills are third-party content. A skill with no scripts is text you can read in full. A skill with scripts runs code on your machine, so read the scripts or install only from a publisher you trust.
Do skills only work with Claude? No. Agent Skills is an open format. The same folder works in any agent that supports it.
Do I need SourceWeft to use a skill from the SourceWeft directory? No. The CLI installs skills for local agents such as Claude Code, Codex, and Cursor. You can also add a skill to a SourceWeft workspace from its page.
How do I update or remove a skill?
With the CLI, run skills update or skills remove <name>. By hand, replace the folder with the new version after reviewing it, or delete the folder to remove the skill.