LLM-generated skills move data-science accuracy 1.2 points — same as filler text
Notes on Do LLM-Generated Skills Make Better AI Data Scientists? A Component Ablation Across Data-Science Workflows (arXiv:2607.07504) — Wei-Jung Huang · July 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 benchmarksThe team built one reusable skill file per stage of a data-science agent's workflow — data preparation, data extraction, statistical analysis, and reporting — generating each with Gemini 2.5 Pro and shipping it unedited, mirroring how a low-curation skill pipeline actually gets used. Each skill split into four parts: routing triggers, a core procedure, worked examples, and reference notes. Rather than testing skills as a single on/off switch, they ran a component ablation: five conditions from no-skill up to the full four-part file, plus a token-matched control of irrelevant office-supply text padded to the same length, and a variant instructing the model to prioritize task instructions over skill guidance. Nine model configurations across OpenAI, Google, and Anthropic — spanning compact, frontier, and explicit-reasoning tiers — ran three times each over 56 deterministically verified tasks, yielding 7,560 runs in the main ablation and 10,584 runs total with the supplemental controls.
Nothing beat the no-skill baseline. Pass rates across all five conditions spanned only 1.2 percentage points, and every comparison against the task-only prompt came back with p ≥ 0.396, including on a mixed-effects model with per-task random intercepts. The token-matched filler content scored statistically the same as the real skill (66.9% vs. 67.5%), meaning models showed no visible benefit from the skill's actual content beyond paying a token cost for it. Break it down by stage and three different things are going wrong. Extraction and reporting already sit near ceiling (88.9% and 97.6% baseline) — no headroom for a skill to lift. Data preparation got worse with a skill attached, 57.1% down to 50.8%, because generic cleaning heuristics collided with task-specific instructions. Statistical analysis never moved off the floor (29.4%) no matter which skill condition ran, which points to a reasoning gap that added prompt text can't close.
Key numbers
| Spread across all skill conditions | 1.2 pp |
| Weakest p-value across conditions | p ≥ 0.396 |
| Main-ablation runs | 7,560 |
| Input-token overhead, Full skill | ~4.5× |
| Human-curated skill gain, prior work (contrast) | 16.2 pp |
Skills related to this research
Related notes
- Forced to search a 34k-skill library instead of being handed the right one, agents' pass rate falls from 55.4% to 38.4% -- a hair above the 35.4% no-skill floor →
- Diagnose, don't rewrite: three revision rounds take a skill from 36% to 62% success →
- Compiling a skill per task beats a static library by up to 13 Pass@1 points →
- Best skill-generation pipeline clears just 14% of code-repo tasks, 25% of document tasks →
- Same skill, +22 points for Claude Sonnet, +5.5 for Nemotron Nano →
- Cut Skill Bodies 39%, Task Success Rises 2.8% →
- 216,938 skills, and only 114,565 come with a paper trail →
- Coding agents violate their own skill's embedded logic in up to 70% of test cases →
- Code review, testing, and security auditing claim 35% of task assignments; requirements analysis gets 2% →
References
- Wei-Jung Huang, "Do LLM-Generated Skills Make Better AI Data Scientists? A Component Ablation Across Data-Science Workflows," arXiv:2607.07504 (July 2026).
- SkillsBench (cited in this paper as prior work): human-curated skills produced a 16.2 percentage-point improvement over no-skill baselines, while LLM-generated skills showed no aggregate benefit.