How we check skills
Most skills on AugmentClaude are folders of files that other people wrote and keep on their own GitHub. This page says what we check before a skill is listed, what we don't, and what an install command does on your computer, so you can decide for yourself.
Where skills come from
Added by our import
Most skills come from our import, which looks for skill repositories on GitHub. It only takes public repositories that have at least 50 stars or come from a short list of known authors. A few more sources were chosen by hand, such as Anthropic's own skills. A person doesn't read each imported skill; they get the automatic checks below.
Submitted on our site
Skills sent in through our Submit page get an automatic AI review first. Then a person on our team reviews each one and approves it before it's listed.
Pasted on our Share page
Our Share page turns a pasted SKILL.md into an install command. We keep a copy of the file on augmentclaude.com, and the command downloads that copy. It gets only an automatic AI check. No person reviews it, and it isn't listed on the site.
What we check automatically
- Each SKILL.md our import adds is checked by fixed text rules, written from what a November 2026 malware audit found. A file that matches one isn't listed. The rules look for:
- a command that downloads from a public IP address (a number instead of a site name) and runs what it gets, on the same line
- a hidden, encoded command that is decoded and run straight away
- a password for opening an archive, such as a .zip file
- install or run steps that point to an anonymous paste site, such as pastebin.com
- an instruction to ignore earlier instructions and send something to a web or email address
- your environment variables, private keys or cloud login files, such as ~/.ssh or ~/.aws, piped or uploaded to the internet
- certain invisible characters, or characters that make text show in a different order than it's stored
- When our import walks through a repository, it skips any skill whose folder sits inside a folder named test, tests, __tests__, fixture, fixtures, __fixtures__, testdata, eval, evals or test-skills. Projects usually keep test files there, not real skills.
- Our nightly import skips repositories on a block list, which includes repositories we've found sharing harmful skills.
- In November 2026 we ran the same rules over the 1,710 SKILL.md files we could download from the catalog at the time. About 1,990 skills were listed then; most of the rest had dead links. They flagged one, which was confirmed malicious and removed. The same audit found four more malicious listings that the rules missed. We removed those too.
What the install command does
For most skills on GitHub, the install command does this:
- Makes a new, empty temporary folder.
- Downloads the skill's folder from the GitHub repository it's listed from: usually the author's own, sometimes a collection that copied it. You get the version that's there now, not a copy we keep.
- Copies that folder to ~/.claude/skills/<skill-name>/.
- Deletes the temporary folder.
Some skills get a shorter command instead. It makes the folder ~/.claude/skills/<skill-name>/ and downloads only the SKILL.md file into it.
Neither of these commands runs any of the skill's files. When you use the skill later, Claude follows its SKILL.md and may run scripts that come with it.
A skill may show some other command, such as one its author gives. We can't describe those step by step. They may download and run programs, so read them before you run them.
On a skill page, the box “What this command does” under the main install command says what that one command does, or that we can't describe it.
What we don't check
- Imported skills aren't reviewed by a person, and neither are files pasted on our Share page. Skills sent through our Submit page are.
- We check only the SKILL.md file. Scripts and other files in the skill's folder aren't checked, even though the install copies them to your computer.
- We check a skill when it's added. Most installs download the skill from GitHub as it is at that moment, so the files can change after we checked them.
- Skills listed before November 2026 whose SKILL.md we couldn't download then have never been through these rules.
- Our rules look only for the patterns listed above, and only for some ways of writing them. Anything else gets through, such as a command that downloads and runs a program from an ordinary website, or a plain instruction to send your files somewhere. Passing the rules doesn't mean a skill is harmless.
- No outside company has audited or certified AugmentClaude.
- Agents, MCP servers and plugins listed here don't get these checks. What each of them can do on your computer is below.
Agents, MCP servers and plugins
These work differently from skills, and we don't run the checks above on them. Each one's page explains its own install command under “What this command does”.
Agents
Most agents are one Markdown file of instructions that Claude hands tasks to. Installing one of those runs nothing, but its header decides which tools the agent may use, and it can set up hooks or MCP servers that run code. A few agents listed here are standalone programs instead, and installing one runs code on your computer straight away. The “What this command does” box on their page warns about this.
MCP servers
An MCP server gives Claude new tools. A local one is a program on your computer that runs like any other, so it can read your files and use the internet. A remote one runs somewhere else, and what Claude sends to its tools goes to whoever runs it.
Plugins
A plugin can bundle skills, agents, hooks and MCP servers. Hooks are commands that run by themselves at set moments, such as before Claude uses a tool, with your account's access.
How to check a skill yourself
Read it.
Skills on GitHub link to their source there. Open the SKILL.md and any scripts in the folder: they're plain text. Some skills are kept on our site instead and have no GitHub folder to read.
Look for the Official badge.
It means the skill comes from the company behind the product, in that company's own GitHub, such as Anthropic's anthropics/skills.
Check the author.
Stars, how long the repository has been around, and whether you recognize the author all help.
Be wary of some instructions.
Take a closer look at a skill that tells Claude to download and run something, send data somewhere, use sudo, or skip asking you first.
Found a problem with a skill?
Email gautam.eswaran@outlook.com with the skill's page link and what's wrong, and we'll look into it. If a skill page shows an install command, the “What this command does” box under it also has a “Report this skill” link.
Keep learning
The 7 places skills live — and how to find the right one.
One command, ~60 seconds, troubleshooting included.
One-liner, git, and manual installs side by side.
From a file on your laptop to an installable link.
The hand-picked best-of list, updated as the catalog grows.
Which of the three you actually need, explained plainly.
An honest side-by-side of the notable skill directories.