What 8,135 agent trials say about writing skills as runbooks
- Source
- x.com
- Date
Most AI agent skills are written like tutorials. The data says they work better as runbooks. A new study analyzed 8,135 agent trials to understand when skills actually help. The main finding: skills do not mainly fill knowledge gaps. They stabilize execution. Procedural anchoring accounted for 65.7% of successful skill cases. Explicit knowledge injection accounted for just 4.5%. That changes how you should build a skill library. > Distill successful trajectories into step-by-step procedures > Label failed runs before using them for skill generation > Route by domain before retrieving from large catalogs > Use strict triggers when skills look semantically similar One result shows why this matters. When success and failure labels were visible during skill distillation, an agent reached 74.6% success. Remove those labels, and it dropped to 40%. The retrieval results were even stranger. As the catalog grew from 5 to 100 skills, retrieval precision collapsed. Task success barely moved. Agents often picked the wrong skill and still extracted enough useful procedure to finish the task. So the important question is not simply: “Did the agent retrieve the correct skill?”

So the important question is not simply: “Did the agent retrieve the correct skill?” It is: “Did the retrieved skill give the agent the right procedure at the right moment?” Full breakdown of what 8,100+ trials reveal about how to design, distill, and retrieve agent skills: https://t.co/dokcBZJXdS
Context
When turning past runs into reusable instructions, preserving which attempts succeeded can change the result substantially. In a controlled skills study, researchers created skills from the same mixture of three successful and two failed runs. For Gemini CLI with Gemini-3.1-Pro-Preview on Terminal-Bench-2, task success reached 74.62% when the creator saw the outcome labels, versus 40% when those labels were removed.
The comparison isolates information used while writing the skill: the underlying runs stayed the same. It supports keeping success and failure annotations when converting execution histories into procedures, so failed attempts are distinguishable from useful steps. The percentages describe that particular agent, and mixture of source runs.
- AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
- agent skill — A reusable instruction file that teaches an agent how to do one job well — the procedure, the tools, and what counts as done.
- benchmark — A standard public test set for comparing AI models — the shared scoreboards behind every "model X beats model Y" claim.
articleAn Empirical Study of Agent Skills' Downstream UtilityYu Cheng, Dehai Zhao, Zhongxin Liu, Qing Huang, Zhenchang Xing, Xiaoxue Ren
videoBuilding Great Agent Skills: The Missing ManualAI Engineer
videoFrom 36% to 100%: How Self-Improving Agents Write Their Own Skills — Rafal Wilinski, RunlayerAI Engineer
Checking sign-in…
Loading comments…



