Last updated: 2026-11-21
The short answer
A Claude skill, also called an agent skill, is a folder with a SKILL.md file that says how to do a kind of task. Put the folder where Claude Code looks for skills, and Claude can read it when it is relevant and follow it.
You can find skills in three places: the publisher's own GitHub repository, a skills directory that indexes many repositories, or a GitHub search. You can install one with a command or by copying the folder yourself. Either way, check first whether it ships scripts, because scripts run on your machine.
What a skill looks like
A skill needs only a SKILL.md. It starts with a short metadata block holding a name and a description, followed by instructions in Markdown. After installing one, this is what we saw at the top of its SKILL.md:
---
name: frontend-design
description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. …
license: Complete terms in LICENSE.txt
---
The folder may also hold scripts/, references/ and assets/. The format is an open specification at agentskills.io, so the same folder works in other agents that support it, not only Claude.
Skills vs MCP servers
In short: a skill is written instructions for Claude, and an MCP server is a service Claude calls. One is a folder, the other a connection. See MCP servers vs agent skills; to set up both, see Install skills and MCP servers in Claude Code.
Where to find skills
- The publisher's repository. Many skills come from the team behind the tool. Anthropic keeps public skills at
github.com/anthropics/skills. This is the most direct source, but you must know it exists. - A skills directory. A directory indexes many repositories so you can search at once. The SourceWeft skills directory indexes public skills from GitHub and records, for each, the source repository and the commit it was scanned at, the full
SKILL.mdand file list, the author's license, whether it ships scripts, notes from an automated scan, and whether a SourceWeft admin reviewed it. It does not host the files; it points to the repository and commit, and the installer downloads from there. - GitHub search. Searching for
SKILL.mdor a topic plus "agent skill" finds repositories no directory has indexed. There is no screening, so read everything first.
What to check before installing
At minimum: the content of SKILL.md (Claude will follow it), whether the file list includes scripts (code that runs on your machine), and the license and source. How to check an agent skill before you install it explains each scan note.
Method 1: install with a command
Search, inspect, install (all run by us with CLI 0.3.0):
npx @sourceweft/cli skills search "frontend design" --limit 5
npx @sourceweft/cli skills info @anthropics/frontend-design-skills
npx @sourceweft/cli skills install @anthropics/frontend-design-skills --scope project
info prints the source, version, license, trust label and file count; install prints them again and asks before writing. In a non-interactive shell it does not decide for you: it stops with Error: Confirmation required. Re-run with --yes to proceed without asking. and writes nothing.
- By default it installs for Claude Code into
~/.claude/skills/;--scope projectuses.claude/skills/in the current project. - For other tools use
--agent.npx @sourceweft/cli skills agentslists the supported tools and their folders, including Codex, Cursor, Gemini CLI, Windsurf and GitHub Copilot.
The CLI checks each file against the hashes recorded when the skill was scanned. That shows you installed what was scanned; it does not show the content is harmless, which is what reading the skill is for. For a step-by-step walkthrough, see Install an agent skill with the SourceWeft CLI.
To manage installed skills:
npx @sourceweft/cli skills list
npx @sourceweft/cli skills doctor
npx @sourceweft/cli skills update --dry-run
Method 2: copy the folder by hand
If a skill is in no directory, you can copy the whole folder containing SKILL.md to ~/.claude/skills/<skill-name>/ (all projects) or .claude/skills/<skill-name>/ (one project) and start a new session. Copying by hand skips the hash check, and you are not told when the skill changes upstream. The full steps (pin a commit, keep the folder name equal to name, and so on) are in Where to find agent skills and how to install one.
Use the command for speed, file checks and managing many skills; copy by hand only when a skill is in no directory. Either way, look before you install.
FAQ
Are Claude skills and agent skills the same thing?
They are the same format: a folder with a SKILL.md. "Claude skills" is the common search phrase; "agent skills" is the name of the format, which other tools that support it can use too.
Do Claude skills cost money? Whether a skill is free depends on its author's license and how it is distributed, so read the license field. Searching, inspecting and installing with our CLI needs no login or account.
Which folder do skills go in?
For Claude Code, ~/.claude/skills/ (all projects) or .claude/skills/ (one project).
Do many installed skills interfere with each other?
We did not test this, so we do not draw a conclusion. Install only what you use and check with skills list.
How do I remove one?
npx @sourceweft/cli skills remove <name> --yes, using the name skills update --dry-run prints (for example gh-anthropics-skills-frontend-design), not the install name; add --scope project or --scope user to pick which copy. For a skill installed by hand, delete the folder.