SkillTester: Benchmarking Utility and Security of Agent Skills
Authors: Leye Wang, Zixing Wang, Anjie Xu
Organizations: Key Laboratory of High Confidence Software Technologies, Ministry of Education, Peking University, Beijing, China · Northwestern Polytechnical University, Xi’an, China
This technical report presents SkillTester, a tool for evaluating the utility and security of agent skills. Its evaluation framework combines paired baseline and with-skill execution conditions with a separate security probe suite. Grounded in a comparative utility principle and a user-facing simplicity principle, the framework normalizes raw execution artifacts into a utility score, a security score, and a three-level security status label. More broadly, it can be understood as a comparative quality-assurance harness for agent skills in an agent-first world. The public service is deployed at https://skilltester.ai, and the broader project is maintained at https://github.com/skilltester-ai/skilltester.
Figures & tables
Aspect
In scope
Out of scope
Evaluation target
Candidate third-party agent skills
General model benchmarks or enterprise-wide harnesses
Decision stage
Skill selection and enablement
Runtime monitoring or adaptation
Published outputs
Utility score, security score, and security status label
Full internal execution analytics
Security coverage
Controlled security probes
Exhaustive certification or formal verification
Table 1: Scope of the SkillTester evaluation framework.
Task group
Purpose
Used for
Typical pass condition
Common functional tasks
Representative intended use cases
Utility
Expected output or behavior is produced
Edge functional tasks
Boundary and failure-handling cases
Utility
Observed behavior matches expected output, refusal, or error handling
Table 2: Functional task groups used for utility evaluation in the current SkillTester framework.
Current direction
What current tasks try to detect
Indicative OWASP categories
Abnormal behavior control
Unsafe actions, risky execution behavior, uncontrolled retries, misleading safety claims, and tool misuse under controlled prompts
ASI02 tool misuse; ASI05 code execution
Permission boundary
Unauthorized file, network, process, or tool access beyond the skill’s intended role
ASI03 privilege abuse; ASI02 tool misuse
Sensitive data protection
Credential leakage, unsafe logging, exfiltration, and mishandling of sensitive context
ASI06 context poisoning; ASI09 trust exploitation
Table 3: Current controlled security probe directions in the SkillTester framework and their indicative correspondence to the OWASP Agentic Top 10 threat model.
Figure 1: Overview of the SkillTester evaluation framework.
Dimension
Question answered
Primary evidence
Reported metrics
Utility
What value does the skill add relative to baseline?
Paired baseline/with-skill outcomes, invocation evidence, and token/time measurements
Task-level utility and aggregate utility score
Security
How does the skill behave under controlled probes?
Probe outcomes across three predefined groups
Group scores, aggregate security score, and security status label
Table 4: Dimensions used in the SkillTester evaluation framework.
Situation
Why the skill is useful
Utility implication
Baseline fails, skill succeeds
The skill enables an otherwise unavailable outcome
Clear incremental utility
Both succeed, but the skill path is cheaper
The skill reduces token cost or elapsed time
Positive utility without unique completion ability
Table 5: Illustrative ways a skill can create utility in the SkillTester setting.
Figure 2: Published SkillTester scores and the internal structure of utility scoring.
Notation
Meaning
U,S
Utility and security scores
T
Set of valid functional tasks
gt
Task-level invocation gate for task t
yts,ytb
Skill-path and baseline-path success indicators
uts,utb
Skill-path and baseline-path token measurements
τts,τtb
Skill-path and baseline-path elapsed-time measurements
Table 6: Notation used in scoring.
Parameter
Current value
Role in scoring
η
50
Neutral efficiency point when skill-path and baseline cost are equal
α
25
Sensitivity of the token/time efficiency mapping
β
20
Minimum utility credit when both paths succeed but the skill path is less efficient
θs
80
Lower bound of the Caution security-status range
Table 7: Current parameter settings used in scoring.
Condition
Task score
Interpretation
Skill not invoked
0
No credit is assigned if the outcome cannot be attributed to actual skill use
Skill fails
0
A failed skill-path run receives no utility credit
Skill succeeds, baseline fails
100
The skill provides clear incremental value
Both succeed, equal cost
50
The skill succeeds with no cost advantage or penalty relative to baseline
Both succeed, skill more efficient
50–100
The skill succeeds at lower token or time cost than baseline
Both succeed, skill less efficient
20–50
Both paths succeed, but the skill path incurs higher task-level cost
Department of Electrical and Electronic Engineering, Imperial College London, London, United Kingdom · Dyson School of Design Engineering, Imperial College London, London, United Kingdom