BuyAgentSkills

How to check an agent skill before you install it (a 10-minute safety review)

Short answer: A skill is a folder of instructions and sometimes scripts that your AI coding tool will follow. Read it the way you would read a stranger's shell script before running it. Six checks, about ten minutes, no special tools.

Written by the Buy Agent Skills team. Updated 9 November 2026.

Why bother

Skills are easy to publish and easy to copy. That is why there are so many good free ones. It also means nobody has necessarily checked the one you found. A skill can tell your agent what to read, what to run and where to send things. If you installed it without reading it, you accepted all of that.

The six checks

1. Open the folder and list what is in it.

You should see a SKILL.md and maybe references/ or scripts/. Surprises are worth a pause: binaries, minified files, or archives you cannot read.

2. Read SKILL.md top to bottom.

Look at the description (when will the agent use this?) and the steps. Ask: does every instruction match what the skill says it does? Be careful with lines that say to ignore other instructions, hide output, or act without asking.

3. Read every script.

In scripts/, search for these and understand each hit:

curl  wget  fetch  http  ssh  scp  nc
rm -rf  sudo  chmod  eval  exec  base64
.env  id_rsa  token  secret  password  API_KEY

A network call is not automatically bad. A skill that fetches a font may need one. A skill that sends your project files somewhere does not.

4. Check what it can touch.

Does it write outside the project folder? Read your home directory? Change your shell config or git settings? A skill should need only what its job needs.

5. Check the license.

Find a LICENSE file. If there is none, you have no stated right to use or share it. If there is one, check that it allows your use (including commercial use) and keep the notice with the files. Do not strip it.

6. Test it somewhere safe first.

Install into a scratch project with no secrets and no important files. Run it once. Check what files changed (git status and git diff make this easy) before you use it for real work.

A quick example

Say a skill promises to "clean up my repo". In check 3 you find rm -rf in a script with a path built from user input. That is not proof of malice, but it is a good reason to read the script closely or choose another skill.

What this does not cover

This review catches the obvious problems. It does not prove a skill is perfect or that it will work in every setup. Tools change, so repeat the review when a skill updates.

If you would rather not do this yourself

That is what a tested pack is for. For each pack, Buy Agent Skills checks licenses, reads the scripts, install-tests from a clean folder and publishes what was and was not tested, with dates. See How we test. If a free skill fits and you have reviewed it, use it. Our buy or build guide helps you decide.

FAQ

Are free skills unsafe? No. Many are excellent. The point is to read before you run, whoever wrote it.

Do I need to read a long SKILL.md line by line? Yes for scripts and instructions about files, network and secrets. You can skim background text.

Does a paid pack remove the need to read? Ask what the seller checked, and still skim the files. Reading is cheap.

Can an agent do the review for me? It can help you spot patterns, but you make the call. Do not let the skill under review judge itself.

Related: What are agent skills? | Buy or build | Browse packs