SkillEvolBench: Benchmarking the Evolution from Episodic Experience to Procedural Skills
The paper introduces SkillEvolBench, a diagnostic benchmark demonstrating that current LLM agents struggle to distill episodic experiences into robust, reusable procedural skills, often performing better by directly reusing raw trajectories than by relying on distilled skill libraries.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you have a brilliant apprentice who is learning a new trade, like fixing complex engines or writing computer code. Every time they try to fix a problem, they leave behind a trail of notes, mistakes, and "aha!" moments. This is called an episodic experience.
The big question this paper asks is: Can we take those messy, one-time notes and turn them into a clean, reusable instruction manual (a "skill") that the apprentice can use forever?
The researchers built a testing ground called SkillEvolBench to find out. Here is how it works, explained simply:
The Setup: The "Learning Loop"
Think of the apprentice's workspace as having three distinct phases:
- The Trial Run (Acquisition): The apprentice tries to solve a specific problem. They might succeed, fail, or get stuck. They leave behind a "trail" of what they did.
- The Editor (Skill Author): A separate, smart editor looks at the trial run and the feedback (did it work? where did it break?). The editor's job is to write a new rule or update an old one. This is the "Skill."
- The Catch: The editor has to decide: "Is this just a fix for this specific broken engine, or is this a general rule for all engines?"
- The Final Exam (Frozen Deployment): The apprentice is given a new, harder problem. They cannot change the rules anymore; they can only use the "Skill Manual" they wrote earlier. Did the manual help them, or was it too specific to the first problem?
The Big Discovery: "The Lost in Translation" Problem
The researchers tested this with 10 different AI models (the "apprentices") across six different real-world jobs (coding, data, documents, etc.).
Here is what they found:
1. The "Raw Trail" is often better than the "Manual"
Surprisingly, when the AI was allowed to just look at its original messy notes from the first try, it often did a better job on the final exam than when it tried to use the cleaned-up manual it wrote.
- Analogy: Imagine you try to bake a cake and burn the bottom. You write a rule: "Don't put the cake in for 45 minutes." Later, you try to bake a different cake, but the rule fails because the oven was different. However, if you just looked at your original notes saying, "The bottom burned, and I smelled smoke," you might realize, "Oh, I need to check the heat," and adapt better. The "cleaned-up rule" threw away the useful context.
2. Current AI is good at "Local Patching" but bad at "Generalizing"
The AI models are great at fixing the specific problem they just faced. They can write a rule that works for that one time. But they struggle to write a rule that works for future, slightly different situations.
- Analogy: It's like a student who memorizes the answer to a specific math problem. If you ask them the exact same problem later, they get it right. But if you change the numbers slightly, they fail because they didn't learn the method, just the answer.
3. More Pages in the Manual Doesn't Help
The researchers tried forcing the AI to write bigger, more detailed manuals with extra files, scripts, and references (like adding more pages to a textbook).
- Result: This often made things worse. The manuals became cluttered with specific details that only applied to the first problem, confusing the AI when it faced a new one.
- Analogy: It's like giving a chef a cookbook that includes the exact brand of flour used for one specific cake. When they try to make a different cake, they get confused because they are looking for that specific brand, rather than understanding the general concept of baking.
The Conclusion
The paper concludes that turning experience into a reusable skill is much harder than we thought.
Current AI agents are like students who are great at taking notes but terrible at writing study guides. They can remember what happened, but they struggle to distill that memory into a durable, reusable procedure that works when the situation changes.
The key takeaway isn't that we need more memory or bigger manuals. The problem is selective abstraction: figuring out which details are important enough to keep for the future, and which details are just "noise" from that one specific moment. Until AI gets better at filtering out the noise, it will keep trying to replay old tapes instead of learning new skills.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.