Skills have emerged as a practical and effective approach for enhancing LLM agents at inference time through structured packages of knowledge. However, existing evaluations largely measure whether skills improve aggregated task success, leaving a more fundamental question underexplored: When do skills help, why do they work, and where do they fail? Through controlled experiments across various benchmarks, agent harnesses and LLMs, we isolate the effects of representation, outcome annotation, retrieval difficulty, and cross-framework robustness of skills. To further answer this question, we design a contrastive study that combines controlled quantitative experiments with paired trajectory analysis. We normalize 8,135 trial records from controlled experiments and retain 238 valid unique labels from 240 open-coded records. We consolidate these observations into a taxonomy of three high-level categories and twelve skill-use modes: skills work when noisy trajectories become procedural anchors that stabilize execution. Skills improve over Workflow Memory by 6.06 points in matched comparisons. Procedural anchoring accounts for 65.7% of skill cases, versus 4.5% for explicit knowledge injection, showing that skills stabilize action rather than inject missing facts. Retrieval is a separate bottleneck: as pools grow from 5 to 100, actual-use precision falls from 29.6% to 3.3%. Confusable distractors impair offline identification, yet downstream success remains stable; exact ground-truth invocation is neither sufficient nor necessary. Skills fail under brittle assumptions, incompatible contexts, or insufficient adaptation. These findings move evaluation beyond aggregate success rates and guide reliable self-evolving agents.
Figures & tables
Figure 1: Experimental pipelines. Top: skill versus procedural memory. We execute each task in a fixed Docker environment, collect successful and failed trajectories, and form a fixed-budget composition grid. The same trace pool is distilled either into Workflow Memory or into a reusable SKILL.md , which are then evaluated on matched tasks under the same protocol. Bottom: skill retrieval. Each task is paired with a candidate pool containing its ground-truth skill and k−1 real distractors (random, similar, or dissimilar). Matched pools are evaluated independently in three procedures: (A) embedding-based ranking without task execution, (B) explicit agent selection without Docker execution or verification, and (C) full-pool real execution with skill-use parsing after task verification. Outputs from (A) and (B) are not passed to (C).
Figure 2: Taxonomy label distribution across trajectory mixtures and experimental arms. Stacked bars show trajectory-level labels for Raw, Workflow Memory, and Skill across the six source-trajectory mixtures from 5s0f to 0s5f . Labels are grouped into three high-level categories; per-mode percentages are reported in Appendix Table 11 .
Agent + Model
Trajectory Mix
Terminal-Bench-2
SkillsBench
Terminal-Bench-Pro
Workflow
Skill
Workflow
Skill
Workflow
Skill
Codex + GPT-5.3-Codex Raw
0.5935
0.5083
0.5394
Codex GPT-5.3-Codex
5s0f
0.4452
0.7548
0.5250
0.7250
0.7333
0.7455
4s1f
0.4000
0.7290
0.5667
0.6167
0.7333
0.7939
3s2f
0.4194
0.7806
0.6417
0.6250
0.6970
0.7333
2s3f
0.3677
0.6839
0.6083
0.7083
0.6667
0.6667
Table 1: Task success rates for Workflow Memory and Skill injection across trajectory mixtures. Gray rows denote Raw baselines. Green, red, and unshaded cells indicate values above, below, and equal to the corresponding Raw baseline, respectively; bold marks the row-wise maximum across mixture settings. Mixture labels denote the numbers of successful (s) and failed (f) source trajectories. Terminal-Bench-Pro rates use 130 trials per condition, with infrastructure or verifier errors counted as failures.
Figure 3: Skill retrieval and execution-time skill use on SkillsBench. Left: precision for the two offline diagnostics. Right: parsed actual-use precision (solid lines) and downstream success (dashed lines) for Arm 3. Curves average over random, similar, and dissimilar pool regimes; outputs are not passed between experiments.
Figure 4: Cross-framework transfer of procedural experience. Prior-experience artifacts constructed in one agent framework are evaluated in another. Dashed lines indicate the target framework’s Raw baseline.
Mechanism
Meaning
procedural_anchor
The artifact gives a usable procedure, ordering, checklist, tool sequence, or verification plan.
knowledge_ injection
The artifact supplies concrete domain knowledge that the agent otherwise lacked.
failure_warning
The artifact warns about a pitfall that the agent avoids.
none
The artifact is not used in a meaningful way.
counterproductive
The artifact misleads the agent or makes the run worse.
Table 2: Mechanism labels used to characterize how injected prior experience affects execution.
Validation stage
Evaluation units
Result
Trajectory grounding
714 checks (238 labels × 3 trajectories)
All labels confirmed
Taxonomy aggregation
238 valid unique labels
95.8% exact; Cohen’s κ=0.952
Table 3: Human validation of the taxonomy construction pipeline. The first stage checks whether raw labels are supported by their source trajectories; the second independently maps those labels to the 12 canonical modes.
Figure 5: Effect of outcome labels during skill creation. Panels compare skills created with outcome labels visible ( normal ) or withheld ( no-hint ) across trajectory mixtures and benchmarks. Dashed lines indicate the corresponding Raw baselines. Terminal-Bench-Pro entries use 130 trials per condition; missing or infrastructure-error trials count as failures.
Pool / metric
Skill-pool size k
5
10
20
50
100
Random
Arm 1 P
97.7
95.5
95.5
92.0
84.1
Arm 2 P
78.1
77.9
82.1
76.5
69.8
Arm 3 P
25.9
23.2
19.5
8.6
4.4
Arm 3 Succ.
31.8
36.8
40.1
36.3
41.9
Similar
Arm 1 P
70.5
63.6
60.2
56.8
53.4
Table 4: Effect of pool composition and size on SkillsBench. Entries report percentages for the indicated retrieval arm, pool composition, and pool size. Arms 2 and 3 are arithmetic means over the reported agent–model pairings. Full recall and F1 values are given in Appendix Table 15 .
Appendix figures & tables12 assets
Supplementary material from the paper’s appendix.
Appendix
Arm
Injected prior experience
Purpose
Raw
No injected prior trajectory or skill
Baseline behavior of the agent on the task.
Workflow memory
Cleaned prior workflows are appended as procedural memory
Tests whether direct trajectory-like procedural memory improves execution.
Skill
The same prior workflows are distilled into a standardized reusable skill
Tests whether compact skill representation improves over direct workflow memory.
Appendix
Table 5: Experimental arms in the contrastive trajectory analysis.
Stores the terminal/tool-use trajectory and the agent’s reasoning-visible interaction record.
Task instruction
Defines the task objective and, for workflow-memory arms, may include injected workflow content.
Skill artifact
Stores the injected skill used in the skill arm.
Task-side files
Used only as contextual artifacts when present; the main taxonomy labels are based on execution trajectories and verifier outcomes.
Appendix
Table 6: Input artifacts used by the taxonomy pipeline.
Dimension
Count
Terminal-Bench 2.0 trials
3,254
Terminal-Bench-Pro trials
2,993
SkillsBench trials
1,888
Raw-arm trials
1,883
Workflow-memory trials
2,658
Skill-arm trials
3,594
Appendix
Table 7: Coverage statistics after manifest construction and artifact linking.
Split
Count
SkillsBench triples
144
Terminal-Bench 2.0 triples
186
Terminal-Bench-Pro triples
198
Triples per mixture setting
88
Total triples
528
Appendix
Table 8: Paired triple sample used for contrastive taxonomy labeling.
Arm
Success / total
Success rate
Raw
312 / 528
59.1%
Workflow memory
295 / 528
55.9%
Skill
327 / 528
61.9%
Appendix
Table 9: Oracle-status success rates across the three execution arms.
Comparison
Mean paired delta
95% bootstrap CI
WM vs Raw
−0.0322
[−0.0814,+0.0208]
Skill vs Raw
+0.0284
[−0.0227,+0.0795]
Skill vs WM
+0.0606
[+0.0076,+0.1136]
Appendix
Table 10: Paired success-rate deltas between execution arms.
SC
Mode
Raw
WF
Skill
SC1
skill_guided_success
10.4%
0.4%
61.6%
SC1
workflow_guided_success
0.0%
54.5%
0.0%
SC1
autonomous_clean_success
48.7%
0.8%
0.2%
SC2
environment_infrastructure_failure
5.3%
1.7%
0.2%
SC2
output_format_schema_mismatch
7.4%
3.8%
3.2%
SC2
background_service_lifecycle_failure
2.7%
2.5%
0.8%
Appendix
Table 11: Contrastive skill-use taxonomy over 528 paired triples. SC abbreviates Skill-use Category , the top-level taxonomy label assigned to a trajectory; each SC groups the fine-grained modes listed in the table. Percentages are computed within each arm over the same paired-triple sample. SC1 denotes successful procedural anchoring, SC2 execution-layer and verification failures, and SC3 invocation, applicability, and boundary failures.
Condition
Source
Success / total
Success rate
Raw
None
65 / 130
50.0%
Short plan
Task instruction
62 / 130
47.7%
Test-first template
Workflow
77 / 130
59.2%
Workflow Memory
Workflow
81 / 130
62.3%
Skill
Workflow
103 / 130
79.2 %
Appendix
Table 12: Lightweight compact procedural baselines on selected Terminal-Bench-2 tasks. Entries report downstream success for Raw, short-plan, test-first, Workflow Memory, and Skill conditions over 26 tasks with five trials per task.
Absolute metrics on the matched 83-task intersection
Representation
Success
Input
Output
Total
Δ succ. vs Raw
Cost profile
Raw trajectories
64.1%
541.5K
14.2K
555.7K
–
Full prior traces provide broad evidence but carry the largest context load.
Workflow Memory
64.8%
417.9K
8.3K
426.2K
+0.7 pp
Most token-efficient representation after cleaning trajectory noise.
Skill
69.6%
511.7K
9.8K
521.5K
+5.5 pp
Highest success rate, with lower token use than Raw but higher token use than Workflow Memory.
Pairwise trade-offs
Comparison
Δ success
Δ input
Δ output
Δ total
Direction
Interpretation
Appendix
Table 13: Matched success and token-cost comparison. Entries are computed on the 83-task intersection with equal task weighting. Token counts are per-task averages reported in thousands (K); “pp” denotes percentage points.
Pool
k
Top-1
Top-3
Top-5
P
P
R
F1
P
R
F1
Random
5
97.7
33.0
98.9
49.4
–
–
–
10
95.5
32.6
97.7
48.9
19.5
97.7
32.6
20
95.5
32.2
96.6
48.3
19.5
97.7
32.6
50
92.0
32.2
96.6
48.3
19.5
97.7
32.6
100
84.1
30.7
92.0
46.0
19.1
95.5
31.8
Appendix
Table 14: Complete Arm 1 embedding-retrieval results on SkillsBench. Entries report ranking metrics from Qwen3-Embedding-0.6B using task–skill-description similarity. Top-5 is omitted for k=5 because it covers the full candidate pool.
Agent / Model
Pool
k
Arm 2: Agent Selection
Arm 3: Real Execution
P
R
F1
P
R
F1
Succ.
Gemini CLI Gemini-3.1-Pro-Preview
Random
5
74.4
75.0
74.7
18.6
69.4
29.3
39.2
Random
10
72.7
72.7
72.7
7.1
66.4
12.9
38.1
Random
20
80.1
81.8
81.0
3.6
66.0
6.8
39.2
Random
50
81.2
84.1
82.6
1.4
65.8
2.8
37.6
Random
100
77.4
83.0
80.1
0.7
66.0
1.4
39.0
Appendix
Table 15: Complete Arm 2 and Arm 3 retrieval results on SkillsBench. Rows correspond to agent–model, distractor regime, and pool size. Arm 2 reports explicit-selection precision, recall, and F1; Arm 3 reports parsed actual-use precision, recall, F1, and downstream success. Dashes indicate excluded entries.
Agent + Model
Benchmark
Creator
5s0f
4s1f
3s2f
2s3f
1s4f
0s5f
Codex GPT-5.3-Codex
TB2
normal
0.7548
0.7290
0.7806
0.6839
0.7097
0.5161
no-hint
0.7677
0.7355
0.5871
0.4968
0.5548
0.3871
SB
normal
0.7250
0.6167
0.6250
0.7083
0.6167
0.4500
no-hint
0.6667
0.6417
0.5583
0.5000
0.5083
0.3500
TB-Pro
normal
0.7455
0.7939
0.7333
0.6667
0.5818
0.4303
no-hint
0.8364
0.6606
0.5758
0.5152
0.4848
0.3758
Appendix
Table 16: Complete numerical results for the outcome-annotation ablation. Entries report downstream success for skills constructed under the indicated trajectory mixture. normal exposes source-trajectory outcomes during construction; no-hint withholds them. Terminal-Bench-Pro entries use 130 trials per condition, with missing or infrastructure-error trials counted as failures.
Agent skills are the de facto mechanism for extending LLM agents with reusable guidance. A skill can shape the agent's task execution, including planning, tool use, problem-solving, and validation. Prior work reported mixed results of agent skills: some skills improve task success rates, while others have no effect, increase token use and execution time, and even reduce success rates. This paper presents a comprehensive analysis of skill-induced agent failures by attributing task failures and cost regressions to specific loaded skills. We introduce a differential analysis framework that attributes a failure or regression to a skill by comparing a target skill-guided run against a no-skill or semantically matched skill reference run that solves the same task, or solves it more cheaply. We instantiate this framework on SkillsBench and SWE-Skills-Bench, yielding 307 skill-induced failures, including 125 functional failures and 182 efficiency regressions. We also build SkillTriage, a taxonomy-guided attribution tool that normalizes paired cases, extracts differential evidence, and produces triage reports. Our major findings include: (1) Skill induced functional failures are rarely caused by obviously irrelevant skills; instead, seemingly relevant skills often make the agent incorrectly implement or omit task-required implementation elements. (2) Skill-induced efficiency regressions are not explained by prompt length alone. (3) The largest sources within Excessive Procedure are excessive verification and heavy implementation pipelines, contributing 67 and 30 cases, respectively. This shows that skills often turn validation checklists and construction recipes into mandatory work. Based on our findings, we propose research topics and tooling improvements for safer and more cost-aware skill reuse.
Gen Dong, Yanjie Gao, Liqun Li +3
Huazhong University of Science and Technology · Microsoft Research · Microsoft +1
Agent skills, which are reusable, domain-specific knowledge artifacts, have become a popular mechanism for extending LLM-based agents, yet formally benchmarking skill usage performance remains scarce. Existing skill benchmarking efforts focus on overly idealized conditions, where LLMs are directly provided with hand-crafted, narrowly-tailored task-specific skills for each task, whereas in many realistic settings, the LLM agent may have to search for and select relevant skills on its own, and even the closest matching skills may not be well-tailored for the task. In this paper, we conduct the first comprehensive study of skill utility under progressively challenging realistic settings, where agents must retrieve skills from a large collection of 34k real-world skills and may not have access to any hand-curated skills. Our findings reveal that the benefits of skills are fragile: performance gains degrade consistently as settings become more realistic, with pass rates approaching no-skill baselines in the most challenging scenarios. To narrow this gap, we study skill refinement strategies, including query-specific and query-agnostic approaches, and we show that query-specific refinement substantially recovers lost performance when the initial skills are of reasonable relevance and quality. We further demonstrate the generality of retrieval and refinement on Terminal-Bench 2.0, where they improve the pass rate of Claude Opus 4.6 from 57.7% to 65.5%. Our results, consistent across multiple models, highlight both the promise and the current limitations of skills for LLM-based agents. Our code is available at https://github.com/UCSB-NLP-Chang/Skill-Usage.
Yujian Liu, Jiabao Ji, Li An +3
UC Santa Barbara · MIT CSAIL · MIT-IBM Watson AI Lab
Large language model (LLM) agents increasingly rely on skills, structured documents that specify when to act, which procedure to follow, and which tools are allowed. Existing evaluations mostly judge the quality of a skill or its contribution to task success, leaving unexamined whether an agent can recognize a relevant skill and apply it on its own. We introduce Skill-Use, a benchmark that evaluates skill use under progressive disclosure, where an agent sees only a skill's name and short description and must retrieve the full procedure before following it. Skill-Use separates three facets of skill use. Trigger measures whether the agent invokes the relevant skill, Compliance measures how faithfully it follows the prescribed procedure, and Boundary measures whether it avoids forbidden operations. A Skill-Use (SU) score combines the three and credits execution only after the skill is triggered. Skill-Use pairs 79 real skills with 177 executable tasks across nine domains, each grounded in real files, run in an isolated Docker sandbox, and scored by a trajectory-based rubric. Evaluating eight LLMs under two agent harnesses, we find that reliable skill use remains out of reach, as the strongest configuration reaches an SU of only 0.613. Triggering and procedural compliance fail as independent bottlenecks, and both scores and model rankings shift with the harness, so skill use behaves as a capability conditioned on the harness rather than a fixed property of the model.
Jinyi Han, Yuanjian Xu, Ying Liao +6
1East China Normal University · 2Hong Kong University of Science and Technology · 3Fudan University +1