Audit agent skills before they touch your system.
Should you install this skill? See the safety and utility evidence for every skill before you trust it.
See SkillAudit in action.
A 17-second walkthrough, from picking a skill to reading its safety and utility verdict.
One execution pass. Four independent verdicts.
The same paired run produces utility, efficiency, cost, and safety. We never blend them into a single number, because a skill that helps can still be the one that leaks your keys.
Does it stay in its sandbox?
A static scan plus a live containerized run record every file write and outbound packet. Each finding is weighted by existence and exploitability confidence.
Does it help?
Mean pass-rate gain over matched with / without pairs.
Is it faster?
Relative wall-clock time saved versus the no-skill baseline.
Is it cheaper?
Relative effective input tokens saved on the same runs.
Most skills help a little. A few help a lot.
Pass-rate gain across 226 skills with a valid paired run. The long tail on the right is where the genuinely capability-adding skills live.
Every skill, plotted by what matters.
One dot per audited skill: utility gain against safety score, sized by findings. Many look helpful, but 41 triggered a confirmed exploit. The most dangerous sit in the lower right: they help the agent and are not safe to run.
What skills add, domain by domain.
Resolution rate across nine professional-domain groups (O*NET occupation taxonomy), per model and harness. The pale fill is the lift skills add over the no-skill baseline. That lift is the whole point: skills make agents materially more capable, which is exactly why an unvetted one is worth worrying about. Hover an axis to inspect a domain; click any agent to compare, up to four at a time.
Leaderboard.
Sorted by utility by default. High utility does not mean safe to install. Click a column to re-sort.
| Skill ▲▼ | Utility ▲▼ | Safety ▲▼ | Verdict ▲▼ |
|---|
Riskiest skills you should know about.
93 confirmed exploits across 41 skillsHow a skill gets scored.
Every skill runs the same five-step pipeline. One execution pass, four axes, full evidence trail.
Profile
Static scan of SKILL.md, scripts, and dependencies. Each finding gets an existence confidence.
static_scan.jsonGenerate
Capability-targeted scenarios with binary judge items, calibrated to baseline difficulty.
scenarios/U*.yamlExecute
Containerized paired runs, with and without the skill. The sandbox records file diff and network in real time.
fs.diff · net.logJudge
An LLM judge scores each item. The security judge composes existence by exploitability against the trace.
judges/*.jsonReport
One report, four scores, every judge item and finding rationale kept for reproduction.
skill_report.jsonCite and reproduce.
BibTeX
@misc{skillaudit2026,
title = {SkillAudit: From Fixed-Suite Benchmarking to
Skill-Centered Assessment},
author = {SkillAudit Contributors},
year = {2026},
eprint = {2606.22613},
archivePrefix = {arXiv},
primaryClass = {cs.AI},
note = {https://skillaudit.github.io/}
}
Read on arXiv ↗
Reproduce
Every skill_report.json with judge items, finding rationale, paired numbers and severity weighting, bundled for all 227 evaluated skills.
Download benchmark.json