skillfed

534 of 3,984 public skills carried a critical security flaw — SkillTester grades against that baseline

Notes on SkillTester: Benchmarking Utility and Security of Agent Skills (arXiv:2603.28815) — Leye Wang, Zixing Wang, Anjie Xu · March 2026

Note published · written by SkillFed’s research pipeline from the paper above · how these notes are made

AI-assisted notes · reviewed by SkillFed Agentic benchmarks Bridge: benchmarks × security

SkillTester is a comparative test harness for agent skills — the packaged, SKILL.md-based capabilities now shipped across Claude Code, OpenAI Codex, GitHub Copilot, and OpenClaw. Its core rule, what the paper calls the comparative utility principle, is simple to state and strict to enforce: every task runs twice, once with the skill disabled and once enabled, on the same model and environment, and a skill only earns credit if it's actually invoked. That gate stops a model's own baseline competence from getting credited to the skill. Utility tasks split into common functional cases — the skill's stated use — and edge cases covering failure handling; each has to resolve in both conditions with a documented pass criterion before it's admitted to the benchmark. Security gets scored separately, through a controlled security probe suite rather than paired execution, organized into three groups — abnormal behavior control, permission boundary, sensitive data protection — built on one premise: a skill's SKILL.md claims and safety badges are unverified assertions until tested against actual code and behavior.

Scoring collapses to three numbers. A task gets 0 if the skill isn't invoked or fails, 100 if the skill succeeds where the baseline fails — a clean win — and if both succeed, the score is set by relative token and time cost: log-scaled around a neutral point of 50, with a floor of 20 so a successful-but-slower run never gets crushed toward zero. Security groups are each scored as a plain pass-rate percentage, averaged unweighted into one number, then bucketed into a status label — Pass requires a perfect 100, Caution covers 80 up to 100, Risky is anything under 80. None of this exists in a vacuum: the paper cites a February 2026 Snyk audit of 3,984 public skills pulled from ClawHub and skills.sh that found 534 carrying at least one critical security issue, 1,467 with a flaw of any severity, and 76 confirmed-malicious payloads. Popularity and self-reported badges, in other words, aren't a substitute for behavioral testing.

Key numbers

Public skills audited (Snyk, Feb 2026)3,984
Skills with ≥1 critical security issue534
Skills with a security flaw of any severity1,467
Confirmed malicious payloads found76
Floor score for a successful-but-slower skill run20/100

Skills related to this research

axiom-analyze-test-failures This skill equips AI coding assistants with specialized knowledge for troubleshooting flaky tests in Swift and Apple OS environments. It helps identify whether failures stem from timing issues, resource contention, environment misconfigurations, or code defects—critical for maintaining reliable CI pipelines. Perfect for developers wrestling with tests that pass locally but fail in continuous integration.★ 1,095 Swift Testing Master Swift Testing, the modern framework for Swift unit tests in Xcode 16+. Learn to write tests with @Test and @Suite, use #expect and #require for assertions, organize tests with traits, handle async patterns, and migrate from XCTest. This skill covers test attachments, exit testing, known issues, and version-gated APIs to help you build reliable test suites.★ 932 qa-test-planner QA Test Planner helps QA engineers create structured test plans, detailed manual test cases, and regression test suites with built-in templates and workflows. It includes Figma MCP integration to validate UI implementations against designs, plus bug report generation and test coverage analysis to ensure comprehensive quality assurance.★ 187 test-fixing test-fixing identifies all failing tests, groups them by error type and root cause, then fixes them in priority order. It handles infrastructure issues first (imports, dependencies), then API changes, then logic bugs. After each fix group passes, it moves to the next until the full suite succeeds.★ 657

Related notes

References

  1. Wang, Wang & Xu, "SkillTester: Benchmarking Utility and Security of Agent Skills," arXiv:2603.28815 (2026)
  2. Snyk, "ToxicSkills: Agent Skills Supply Chain Compromise Study" (2026)
  3. OWASP Foundation, "OWASP Top 10 for Agentic Applications for 2026"
  4. Claude Docs, "Agent Skills" (docs.claude.com)
  5. Lopopolo, "Harness engineering: leveraging Codex in an agent-first world," OpenAI