Source-linked AI summary

Demystifying Agent Skills: Why They Work-Until They Don't

Zhiyuan Jiang, Fangrui Huang, Hanwen Xing, Xander Wu, Yipeng Gao, Rui Cao, Mengdi Wang, Shilong Liu, Yijiang Li

arXiv:2608.14036v1cs.AI

TL;DR

Existing evaluations often ask whether skills improve task success, but reveal little about why they change agent behavior. This paper combines controlled experiments with paired trajectory analysis to study skill use. It finds that skills chiefly work as procedural anchors rather than factual-knowledge injections.

  • Problem

    Existing evaluations focus on aggregate task success, leaving limited evidence about how skills change agent behavior and why they help some tasks but harm others.

    Source: §1 · p. 1
  • Method

    The study compares matched executions with and without skill access and analyzes trajectory differences across the skill-use pipeline.

    Source: §1 · p. 2, §4 · p. 7
  • Results

    65.7% of skill cases involve procedural anchoring, versus 4.5% for explicit knowledge injection.

    Source: §1 · p. 2
  • Takeaways & Limitations

    The findings suggest understanding skill use as a lifecycle problem involving representation, retrieval, and leverage of procedural knowledge, rather than a single memory-injection mechanism.

    Source: §6 · p. 11

    The evaluation covers terminal- and tool-using benchmarks and limited agent–model configurations, so findings may not generalize to other scaffolds, model families, or versions.

    Source: §7 · p. 11

Abstract

from arXiv · show

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: \emph{\textbf{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.

1 Introduction

The paper moves skill evaluation beyond aggregate task success to explain when skills help, how they change agent behavior, and where they fail. It finds that skills mainly stabilize procedural execution, while reliable benefits depend on retrieval and context-appropriate application.

Motivation

  • Repeated agent failures often come from rediscovering procedural details, while aggregate-success evaluations reveal little about what skills stabilize or why they help one task and harm another.As a result, skill design has often relied on heuristic iteration, prompt tuning, or trial and error rather than a principled account of skill value.Source: §1 · pp. 1–2

Approach

  • The study uses matched executions with and without skill access, tracing divergences across representation, transfer, retrieval, and invocation to attribute effects to concrete mechanisms.Its four questions compare skills with direct procedural memory, test outcome annotations and cross-framework transfer, and examine pool size and confusability.Source: §1 · p. 2

Results

  • 65.7% of skill cases reflect procedural anchoring, versus 4.5% explicit factual-knowledge injection; skills stabilize setup, tool-use, implementation, and verification routines.Workflow memory preserves useful procedural evidence but can also retain irrelevant exploration, failed branches, and process noise that increase timeout and drift.Source: §1 · pp. 2–3

Retrieval and failure modes

  • Hard negative distractors impair explicit skill selection, but retrieval correctness does not map one-to-one to success: correct skills may fail, while related nonground-truth skills can still help.Failures also arise when guidance is retrieved for the wrong procedural context, invoked superficially, or insufficient for execution bottlenecks.Source: §1 · p. 3

Lifecycle of skill use

  • Skills work when distilled guidance is reusable and applied in compatible contexts; they fail when it is noisy, over-specific, mismatched, or followed without adaptation.This lifecycle view frames reliable self-improvement as generating, retrieving, and applying procedural abstractions—not merely accumulating memories.Source: §1 · p. 3

Contributions

  • The trajectory analysis normalizes 8,135 trial records and consolidates 238 valid unique labels from 240 sampled trajectories into three categories and twelve skill-use modes.The analysis shifts evaluation from aggregate success rates toward mechanisms by which skills change agent behavior.Source: §1 · p. 3

2 Related Works

Agent-memory research has moved from reusing past experiences to explicit procedural skills, while benchmark evaluations still leave execution-level reasons for skill success and failure underexplored.

2.1 Memory Reuse in LLM Agents

2.2 Benchmarks for Evaluating Agent Behavior

  • General tool- and computer-use and software or terminal benchmarks test multi-step interaction; Terminal-Bench (Merrill et al., 2026) offers realistic command-line tasks with isolated environments and test-based verification.Source: §2.2 · p. 4
  • SkillsBench (Li et al., 2026) and SWE-Skills-Bench (Han et al., 2026) measure skill utility but mainly report final success; this work links outcomes to retrieval, interpretation, and procedural fit.Source: §2.2 · p. 4

3 Study Design

The study treats skill use as a controlled transformation of prior agent experience into procedural knowledge, combining controlled experiments with trajectory analysis to examine when skills help, how they work, and where they fail.

3.1 Research Questions

  • The study’s four questions examine how procedural representation, outcome signals, cross-framework transfer, and skill-pool retrieval affect skill use.RQ1 compares workflow memories with distilled skills; RQ2 isolates success/failure annotations; RQ3 tests transfer across frameworks; and RQ4 studies retrieval and downstream use as pools grow or become more confusable.Source: §3.1 · pp. 4–5

3.2 Experimental Setup

  • Experiments use complementary agent–model pairings and Terminal-Bench and SkillsBench, with RQ4 interpreted only within its own pairings.RQ1–RQ2 use Codex + GPT-5.3-Codex and Gemini CLI + Gemini-3.1-Pro-Preview; RQ3 transfers artifacts from the primary Codex setting to Gemini CLI; RQ4 uses Gemini CLI + Gemini-3.1-Pro-Preview and Codex + GPT-5.4. Downstream studies use five unique trials per task unless otherwise noted.Source: §3.2 · pp. 5–6

3.3 Experimental Design

  • The RQ1–RQ2 design compares Raw, Workflow Memory, and Skill conditions using the same source trajectories and target tasks.A fixed-budget grid varies the mix of successful and failed trajectories; standard and no-hint Skill variants test the role of visible outcome annotations while retaining the same trajectories and execution protocol.Source: §3.3 · p. 6
  • RQ3 constructs skills and workflow memories in Codex, then evaluates their transfer in Gemini CLI against a target-framework Raw baseline.The source experience is fixed while the target framework changes, including prompting style, tool-use interface, and execution behavior.Source: §3.3 · p. 6
  • RQ4 independently measures retrieval and execution by comparing offline skill identification with full-pool execution outcomes across controlled candidate pools.The three arms are embedding retrieval, explicit agent selection without task execution, and real execution with the full pool; offline selections are not passed to execution. Pools contain ground-truth skills and distractors, range from 5 to 100, and use random, semantically similar, or dissimilar distractors.Source: §3.3 · pp. 6–7

4 Skill-Use Mechanisms: A Contrastive Taxonomy

The section builds a human-checked, 12-mode taxonomy from contrastive trajectories to explain how skills alter behavior beyond aggregate success. Paired comparisons show more skill-arm trajectories in successful procedural anchoring, alongside execution-layer and invocation or boundary failures.

4 Skill-Use Mechanisms: A Contrastive Taxonomy

  • The analysis normalized 8,135 trial records, including 7,837 with transcripts, and open-coded 240 sampled trajectories into 238 valid unique labels for a 12-mode taxonomy.Both LLM-assisted taxonomy-construction stages received an independent human check.Source: §4 · p. 7
  • 95.8% exact agreement and Cohen’s κ = 0.952 between human and LLM assignments supported the stability of the 12-mode taxonomy.Human validation included checking three supporting trajectories for each of 238 labels, totaling 714 trajectory–label checks, then independently mapping all labels to canonical modes; Table 3 summarizes the validation stages.Source: §4 · p. 7, Table 3 · p. 7
  • The study compared raw execution, workflow-memory injection, and skill injection in 528 paired triples across three benchmarks, yielding 1,584 arm-level mode assignments.The triples covered SkillsBench (144), Terminal-Bench 2.0 (186), and Terminal-Bench-Pro (198); an LLM judge labeled each arm and recorded pairwise behavioral changes.Source: §4 · p. 7
  • The 12 fine-grained modes roll up into SC1 successful procedural anchoring, SC2 execution and verification failures, and SC3 invocation, applicability, and boundary failures.SC3 includes guidance that is misused, over-applied, ignored, or constrained by external limits.Source: §4 · pp. 7–8
  • 326/528 skill-arm assignments were SC1 versus 294/528 for workflow memory; SC2 failures were 124/528 for skills versus 197/528 raw and 176/528 workflow memory, while SC3 failures were 78/528 for skills versus 19/528 raw.SC1 captures successful procedural anchoring, SC2 execution-layer and verification failures, and SC3 invocation or boundary failures.Source: §4 · p. 8

5 Findings

Skills improve on workflow memory mainly by stabilizing procedures and reducing execution failures, not by supplying missing facts. Their benefits are limited by brittle applicability and retrieval difficulty, especially with confusable skill pools.

5.1 Skills work as procedural anchors, not merely external knowledge

  • +6.06 percentage points: skills improve over workflow memory in matched comparisons, with a 95% bootstrap confidence interval of [+0.76, +11.36].Skill-augmented runs achieved 61.9% oracle-status success, compared with 59.1% for raw execution and 55.9% for workflow memory; both skill and workflow memory draw on the same source trajectories.Source: §5.1 · p. 8
  • 65.7% of skill mechanisms were procedural_anchor, versus 4.5% explicit knowledge_injection, indicating that skills stabilize action rather than supply missing facts.On 26 selected Terminal-Bench-2 tasks, instruction-derived short plans reached 47.7% success and workflow-derived test-first templates 59.2%, below Workflow Memory (62.3%) and Skill injection (79.2%); skills also distill traces into cleaner procedures than workflow memory.Source: §5.1 · pp. 8–9

5.2 Skills improve execution robustness but fall short on tasks requiring reformulation or verification

  • 23.5% of skill-arm labels were SC2, versus 37.3% for raw and 33.3% for workflow arms, while setup and service failures also fell with skills.Environment_infrastructure_failure declined from 5.3% in raw execution to 1.7% with workflow memory and 0.2% with skills; algorithmic_logic_error and static_verification_without_runtime remained substantial across arms.Source: §5.2 · p. 9

5.3 Skills introduce invocation and applicability failures

  • 10.0% of skill-arm cases involved skill_guidance_misapplied_or_ignored, versus 0.8% for raw execution and 0.4% for workflow memory.Workflow memory instead had timeout_budget_exhaustion in 10.6% of cases, versus 1.7% for raw execution and 4.4% for skills; skill utility depends on distillation, compatible transfer or retrieval, invocation, and adaptation.Source: §5.3 · p. 9

5.4 Outcome annotations guide skill construction

  • 0.7462 versus 0.4000: for Gemini on Terminal-Bench-2 at 3s2f, normal skill creation outperformed creation without outcome hints once failed trajectories were included.Withholding outcome labels had little effect when source pools contained only successful trajectories; the same stronger-normal-creation pattern held across completed Gemini Terminal-Bench-2 and SkillsBench ratios.Source: §5.4 · p. 10

5.5 Retrieval exposes the gap between skill availability and skill use

  • 29.6% to 3.3%: average actual-use precision fell as pools grew from 5 to 100, while downstream success changed only from 36.4% to 39.3%.Arm 3 recall remained 54.3–73.6% at k = 100, so agents often inspected or invoked candidates without restricting use to the annotated ground-truth skill; exact ground-truth invocation was neither sufficient nor strictly necessary for success.Source: §5.5 · p. 10
  • 70.5% to 53.4%: Arm 1 top-1 precision on similar pools fell with pool growth, while random and dissimilar pools retained higher precision.At k = 100, random-pool precision was 84.1% and dissimilar-pool precision was 93.2%; offline identification diagnostics are independent of execution, and similar distractors were their dominant stressor.Source: §5.5 · p. 10

6 Conclusion

The paper examines when skills help, why they work, and where they fail, finding that they are most effective as procedural anchors but can fail through incorrect retrieval, context mismatch, rigid use, or insufficient reformulation and validation. It frames reliable skill use as a lifecycle problem involving how agents represent, retrieve, and leverage procedural knowledge.

6 Conclusion

  • Skills are most effective as procedural anchors, but can fail when retrieved incorrectly, used in the wrong context, followed too rigidly, or applied without deeper reformulation and runtime validation.The study uses controlled experiments and contrastive trajectory analysis to move beyond aggregate success rates.Source: §6 · p. 11
  • Skill use is a lifecycle problem: self-evolving agents need to improve how they represent, retrieve, and leverage procedural knowledge, not merely generate more skills.The authors offer their analysis as a foundation for more principled evaluation and design of future skill-based agent systems.Source: §6 · p. 11

7 Limitations

The evaluation covers a limited range of benchmarks and agent–model configurations, while the mechanism taxonomy draws on a small sample of normalized records.

7 Limitations

  • The evaluation omits long-horizon web interaction and open-ended collaboration, and its limited agent–model configurations may not generalize to other scaffolds, model families, or versions.The study focuses on terminal- and tool-using benchmarks emphasizing multi-step execution, debugging, and verification.Source: §7 · p. 11
  • The mechanism taxonomy comes from stratified open-coding of approximately 3% of normalized records, so rare behavioral modes may be underrepresented.Source: §7 · p. 11

A Implementation Details

The experiments use controlled comparisons to isolate representation, outcome annotation, cross-framework transfer, and retrieval difficulty. Within each experiment, conditions share the same tasks, benchmark interface, agent framework, model, execution harness, and trial budget unless stated otherwise.

A Implementation Details

  • Conditions within each experiment share tasks, benchmark interface, agent framework, model, execution harness, and trial budget unless otherwise stated.The comparisons isolate representation, outcome annotation, cross-framework transfer, and retrieval difficulty.Source: A Implementation Details · p. 15

A.1 Model–Framework Pairings and Benchmarks

The evaluation pairs agent frameworks and models with benchmark tasks to study skill use in realistic deployments and controlled retrieval settings.

A.1 Model–Framework Pairings and Benchmarks

  • RQ1–RQ3 use Codex + GPT-5.3-Codex and Gemini CLI + Gemini-3.1-Pro-Preview, while RQ4 uses Gemini CLI + Gemini-3.1-Pro-Preview and Codex + GPT-5.4.Because GPT-5.3-Codex was unavailable for RQ4, its results are interpreted only through within-pairing comparisons across three independent experiments, not direct numerical comparisons with RQ1–RQ3.Source: §A.1 · p. 15
  • RQ1–RQ3 draw controlled subsets from Terminal-Bench Pro (200 public tasks from 400 across 8 domains), Terminal-Bench 2.0 (89 tasks), and SkillsBench (86 tasks across 11 domains).RQ4 uses SkillsBench for its native task–skill annotations; the benchmarks involve multi-step execution and tool use, making many failures procedural rather than purely factual.Source: §A.1 · p. 15
  • Execution experiments use n = 5 unique trials per task and parallelism of 20 unless noted; retrieval-isolation arms use one query per task–pool setting.Skills are placed in the execution environment as reusable procedural resources rather than fully inlined into initial context; RQ4 retrieval and distractor similarity scores use Qwen3-Embedding-0.6B (Zhang et al., 2025).Source: §A.1 · p. 15

A.2 Dive into Skill-Use Mechanisms: Trajectory Labeling and Comparative Analysis

The section builds a trajectory-level, paired analysis to identify how prior-experience artifacts change agent execution and failure modes. It induces a taxonomy from observed trajectories, then applies it to matched raw, workflow-memory, and skill runs.

Trajectory Source and Experimental Context; Manifest Construction and Trial Normalization

  • The normalized manifest contains 8,135 trial records from three benchmark sources, while labeling retains only selected artifacts needed to analyze trajectory success and failure.The corpus covers Terminal-Bench 2.0, SkillsBench, and Terminal-Bench-Pro under a fixed harness and agent-model configuration; workflow and skill arms use six prior-experience compositions.Source: §A.2 · pp. 15–16

Manifest Construction and Trial Normalization

  • Because some skill-arm token fields are incomplete, taxonomy analysis relies primarily on trajectory content, verifier outcomes, and paired mode changes.Token and duration metadata support secondary analyses of context cost, output length, and execution time when present.Source: §A.2 · p. 16

Open Coding of Individual Trajectories

  • Open coding derives candidate modes from sampled execution failures rather than imposing a generic taxonomy, with an open-ended primary-mode field enabling vocabulary to emerge from the data.Sampling is stratified by benchmark, setting, arm, and outcome; the target is 240 trials.Source: §A.2 · pp. 16–17

Open Coding of Individual Trajectories; Canonical Taxonomy Induction

  • 238 of 240 open-coded records were retained as valid unique labels, and taxonomy induction yielded 12 mixed success/failure modes.The modes distinguish success attributable to skill guidance, workflow guidance, or autonomous agent behavior as well as failure patterns.Source: §A.2 · p. 17

Paired Contrastive Trajectory Labeling

  • Matched triples compare raw, workflow-memory, and skill trajectories for the same task to identify failure modes fixed or introduced by each treatment.The paired design contains 528 triples; the judge assigns modes and compares each arm pair, including the skill-versus-workflow comparison.Source: §A.2 · p. 18

A.3 Paired-Trajectory Example … A.8 Lightweight Compact Procedural Baselines

The sections compare skills with direct workflow memory, then describe controlled tests of outcome annotations, framework transfer, skill retrieval, and compact procedural baselines. Paired analysis highlights the distinction between distilling useful procedures and preserving noisy process, while the retrieval design separates offline identification from execution-time use.

A.3 Paired-Trajectory Example

  • The paired analysis identifies Skill versus Workflow Memory—not Skill versus Raw—as the most robust aggregate difference in the taxonomy sample.The paired-trial example illustrates the contrast: Raw bypasses an external-service check, Workflow Memory misses the latency threshold, and Skill passes all 11 tests by starting a dependent request when its prerequisite resolves.Source: Table 10 · p. 20, §A.3 · p. 20
  • The paired taxonomy covers 528 triples, but its v1 labels are applied to the full set with LLM assistance rather than exhaustive human coding.It uses one representative trajectory per arm and triple, and reports token cost only on the matched same-task intersection with complete metadata.Source: §A.3 · p. 20

A.4 RQ1: Representation of Prior Experience

  • RQ1 holds the underlying trajectory pool constant while comparing Raw, cleaned Workflow Memory, and standardized Skill representations under matched execution conditions.The same tasks, model, scaffold, benchmark interface, and trial budget are kept fixed within each agent–model pairing; successful and failed trajectories are recomposed under a fixed experience budget.Source: §A.4 · pp. 20–21

A.5 RQ2: Outcome Annotation and No-Hint Ablation

  • RQ2 compares standard and no-hint Skills to isolate whether explicit success/failure annotations add value beyond the same trajectories and skill format.The no-hint variant removes outcome annotations during skill construction while keeping the task pool, workflow content, experience budget, and execution protocol unchanged.Source: §A.5 · p. 21

A.6 RQ3: Cross-Framework Transfer

  • RQ3 tests portability by evaluating Codex-derived Workflow Memory and Skills with Gemini, holding source experience and target tasks fixed while changing the agent framework.It compares both transferred artifacts with Gemini’s Raw baseline; the framework shift changes prompting style, tool interface, and execution loop.Source: §A.6 · p. 21

A.7 RQ4: Skill Retrieval and Downstream Execution

  • RQ4 varies candidate-pool size from 5 to 100 and compares random, embedding-near, and embedding-far distractors across its retrieval and execution experiments.Ground-truth skills come from SkillsBench annotations; the execution arm parses inspected or invoked skills and measures precision, recall, F1, and task success.Source: §A.7 · p. 22
  • RQ4 separates offline retrieval, deliberate agent selection, and execution-time skill use, which are independent tests rather than sequential stages.Correct offline selection does not guarantee success, and selecting a non-ground-truth skill is not always fatal because related skills may still offer useful procedural guidance.Source: §A.7 · p. 22

A.8 Lightweight Compact Procedural Baselines

  • The compact-baseline study compares short-plan and test-first procedural text with Raw, Workflow Memory, and Skill on 26 Terminal-Bench-2 tasks across five trials each.Table 12 covers these downstream-success conditions; Table 13 reports matched success and token-cost comparisons on an equally weighted 83-task intersection, with token counts in thousands. Table 11 describes taxonomy categories over 528 paired triples.Source: §A.8 · pp. 22–23, Table 12 · p. 23, Table 13 · p. 23

A.9 Matched Token-Cost Analysis · B Prompts

On a matched set of 83 tasks, Skill achieved the strongest execution performance while Workflow Memory used tokens most efficiently. Skill improved over Raw while reducing token use, but required more context than Workflow Memory.

A.9 Matched Token-Cost Analysis

  • The analysis compared Raw, Workflow Memory, and Skill on 83 tasks with usable token metadata for all three representations.Success and token use were averaged within each task and representation, then across tasks, keeping the task mix fixed and preventing tasks with more completed trials from receiving extra weight.Source: §A.9 · p. 23
  • Workflow Memory was the most token-efficient representation, reducing both input and output tokens relative to Raw trajectories.The analysis characterizes Workflow Memory as more token-efficient and Skill as more effective.Source: §A.9 · pp. 23–24
  • Skill was not uniformly cheaper than Workflow Memory, trading additional context for stronger execution performance.The comparison presents an effectiveness–efficiency trade-off between the representations.Source: §A.9 · pp. 23–24
  • Skill achieved the highest success rate, improving over Raw while also reducing token usage.It traded additional context relative to Workflow Memory for stronger execution performance.Source: §A.9 · p. 24

B.1 skill-creator.md (Experiment 1) · B.2 skill-creator-no-hint.md (Experiment 2) · B.3 Prompts for Trajectory Labeling and Comparative Analysis

The appendices specify how trace-based skills are generated and how controlled-study trajectories are labeled, consolidated into modes, and compared to identify skill and workflow mechanisms.

B.1 skill-creator.md (Experiment 1)

  • The Experiment 1 skill creator extracts repeatable steps, tools, cross-trace patterns, and failure modes, then produces one reusable skill generalized beyond the observed task.It directs the generator to select the most reliable approach and use placeholders rather than task-specific paths or data.Source: §B.1 · p. 24
  • The Experiment 1 template structures skills around applicability, preconditions, ordered actions, failure handling, and verification.It asks for concrete, actionable steps and fixes followed by rerun verification.Source: §B.1 · p. 24

B.2 skill-creator-no-hint.md (Experiment 2)

  • The no-hint creator infers failure signals and mitigations only from observable trace evidence and avoids assuming whether a run succeeded or failed.It retains the reusable, single-skill format and requires generalizable, actionable guidance.Source: §B.2 · pp. 24–25

B.3 Prompts for Trajectory Labeling and Comparative Analysis

  • Trajectory labels explain success or failure using concrete trajectory evidence, distinguish raw, workflow, and skill conditions, and judge skill effects only where applicable.The prompt requires evidence spans and separates missing knowledge from misuse, capability limits, and environmental causes.Source: §B.3 · p. 25
  • For each batch, produce a small set of canonical, specific procedural modes and assign every input id exactly one mode, covering failures, skill/workflow effects, and successful execution patterns.Aim for 8–14 modes per batch, preferring fewer, clearer modes over many narrow ones.Source: §B.3 · p. 26
  • A consolidation prompt merges overlapping batch modes into a unified 9–14-mode taxonomy and maps every source mode to a canonical category.Each unified mode records the batch-level modes folded into it.Source: §B.3 · p. 26
  • Trajectory comparisons record per-arm modes and evidence, classify changes against baselines, and assign skill or workflow mechanisms with confidence.The schema distinguishes knowledge injection, procedural anchoring, failure warnings, no effect, and counterproductive effects.Source: §B.3 · p. 27
Loading 2608.14036v1…