The Regression Tax: Decomposing Why Skills Help and Hurt LLM Agents
A structured summary of the Sentient Labs paper by Darshan Tank and Baran Nama (arXiv 2607.22520), based on a detailed Chinese forum write-up.
Key points
- Setup: 5,832 paired experiments on two office-automation benchmarks (OfficeQA-Pro, SpreadsheetBench) across three model-framework stacks (OpenCode+MiniMax-M2.7, Codex+GPT-5.4-mini, Claude Code+Sonnet 4.6), each task run with and without a skill library, compared per-item.
- Core finding: 553 gains vs. 324 regressions — skills fixed 553 previously failing tasks while breaking 324 tasks the agent previously solved, offsetting 59% of the gains. None of the 18 experimental conditions had zero regressions.
- Rankings can invert: On Claude Code+Sonnet 4.6 / OfficeQA-Pro, ranking libraries by gain (12/11/10) vs. net effect gain−regression (+5/+7/+8) completely reverses the ordering. Average pass rate hides which library is genuinely safer.
- 90%+ of OfficeQA-Pro failures are grounding errors (wrong table, year, or definition read)
- SpreadsheetBench failures concentrate in verification
- Residual (always-failing) tasks also stem from grounding errors that no procedural skill corrects
- Report paired gain/regression counts, not just net pass rates.
- Evaluate skills in three conditions: no library, description-only, description+body — to detect osmosis.
- Target skills at grounding and verification, not method.
- Fix evaluator validation gaps — grader blind spots create false negatives that poison skill selection.
Three regression mechanisms
1. Skill-Description Osmosis: Skill names and descriptions live in the system prompt even when never invoked. In one case (UID0096, correct answer 0.377), the agent passed without skills, but failed identically with all three libraries — no skill was called; the words "revised" and "customs" in descriptions alone skewed its interpretation. This defeats retrieval-based safety methods (ASSAY, GRASP, RSEA) that only evaluate skills when invoked. 2. Grounding Displacement: An invoked skill's procedure overrides the agent's correct reading of the input. 59 of 81 (72.8%) OfficeQA-Pro regressions fit this pattern — the dominant failure mode. 3. Verification Displacement: Skill procedures suppress output checks the agent would otherwise perform. Rare on OfficeQA-Pro but decisive on SpreadsheetBench.
Where failures actually live
The agent pipeline is input → grounding → method → verification → output. Existing skill libraries overwhelmingly target the method stage, but:
Evaluator blind spots
Of 663 formula-related SpreadsheetBench failures, 226 (34%) had fully correct formulas — the value-based grader simply could not evaluate structured-reference formulas. Re-computing with a real Excel engine raised pass rates by 11–49 percentage points per library (e.g., GPT-5.4-mini from 67% to 79%).
Statistical caveats
Only 5 of 18 conditions reached p<.05; only 3 survived Bonferroni correction — all Claude Code+Sonnet 4.6 on SpreadsheetBench (+43 to +47 items, p<.001). Most "improvements" elsewhere are indistinguishable from noise.
Engineering takeaways
---
Paper: The Regression Tax: Decomposing Why Skills Help and Hurt LLM Agents Authors: Darshan Tank, Baran Nama (Sentient Labs) arXiv: 2607.22520 | Code: not yet released