80% of agent skills in a 49,943-skill registry don't do what they claim — most of it is sloppiness, not malice
Notes on Behavioral Integrity Verification for AI Agent Skills (arXiv:2605.11770) — Yuhao Wu, Tung-Ling Li, Hongliang Liu · May 2026
Note published · written by SkillFed’s research pipeline from the paper above · how these notes are made
AI-assisted notes · reviewed by SkillFed Skill security Bridge: security × benchmarksMost skill safety work checks prompts and runtime actions, never the skill artifact itself against its own description. Behavioral integrity verification (BIV) names that missing check: a typed comparison between what a skill declares and what it actually does, run over a shared capability taxonomy of 29 capability types spanning code, natural-language instructions, and metadata. The declared side comes from parsing manifests plus LLM-assisted extraction, constrained by a hallucination-control filter that requires a quoted source span for every claimed capability. The actual side comes from deterministic analysis — inter-procedural taint analysis for Python, regex extraction for JavaScript and shell — plus LLM parsing of natural-language instructions. Both sides land in the same typed taxonomy, producing one structured evidence record per skill that feeds three downstream jobs: a deviation taxonomy, a root-cause classifier, and a malicious-skill detector.
Run across 49,943 skills pulled from the OpenClaw registry, the deviation taxonomy turns up a wide description-implementation gap: 80.0% of skills deviate from what they declare, roughly split between undeclared capabilities quietly present in the code and declared capabilities that were never implemented. Root-cause classification then sorts those deviations by intent: 81.1% trace to ordinary developer oversight, 18.9% look adversarial, and 5.0% of all skills carry a predicted multi-stage attack chain. Clustering surfaces four compound-threat patterns worth naming individually: exfiltration chains, remote-code-execution chains, code obfuscation, and data-lineage violations. How adversarial each one is varies sharply by category — it's not one registry-wide rate. Feeding this structured evidence into an LLM judge, with an explicit override rule for cases where compound-threat flags coincide with undeclared high-risk capabilities, gets malicious-skill detection to an F1 of 0.946 on a 906-skill benchmark — ahead of both the rule-based and single-pass LLM baselines it's tested against.
Key numbers
| skills audited from the OpenClaw registry | 49,943 |
| of skills deviate from their declared behavior | 80.0% |
| of deviations trace to adversarial intent (vs. 81.1% oversight) | 18.9% |
| of skills carry a predicted multi-stage attack chain | 5.0% |
| malicious-skill detection F1, 906-skill benchmark | 0.946 |
Skills related to this research
Related notes
- 84% of Malicious Agent-Skill Exploits Hide in the Docs, Not the Code →
- 26.1% of Marketplace Agent Skills Carry a Vulnerability →
- Frontier Agents Cave to Poisoned Skill Files Up to 80% of the Time →
- 1,184 skills fell in one campaign — because Agent Skills has no line between data and instructions →
- Semgrep, refinement types, and Z3 turn a "formally verified skill" into a proof you can re-check yourself — minus one named gap →
- Whole-Trace Checking Catches 95.8% of Skill Policy Violations →
- Zero malicious prompts, 50.3% attack success: poisoned skill files hijack agents anyway →
- Dependency-ordered retrieval beats flat similarity search by 31 points on ALFWorld →
- Give a small model screenshots of its own skills and its GUI success rate more than doubles — 10.78% to 25.40% →
References
- Wu, Y., Li, T.-L., & Liu, H. (2026). Behavioral Integrity Verification for AI Agent Skills. arXiv:2605.11770.