A skill is just markdown — but markdown that instructs your agent, and that can ship helper scripts the agent may run. Treat a SKILL.md like any third-party code: useful, and worth a 60-second read before you trust it.
A skill folder holds a SKILL.md (instructions) and, optionally, scripts/ and references/. Two things to be aware of:
This isn't unique to skills — it's the same trust model as any package, extension, or snippet you add to a project. The point is simply to look before you install.
scripts/. Short, readable, scoped to the task is good. Obfuscated or network-heavy is a flag.allowed-tools frontmatter field — a skill that restricts itself is a good sign.Run a new skill in a project where a mistake is cheap (a scratch repo, a branch, a container) before using it on anything important. Most agents ask before running commands — keep that confirmation on while you're getting to know a skill. Review the diff a skill-driven change produces, just as you would a pull request.
We don't execute or modify skills — we index them and link the original source so you can verify exactly what you're installing. The Pro Quality Score factors in signals like documentation completeness and attribution, which correlate with well-maintained, trustworthy skills. But the final check is always yours: read it, then install it. See the install guide for the safe two-step on each agent.