VCE-Skill: Enhancing Skill Self-Evolution with Version-Change Experience
The paper proposes VCE-Skill, a novel framework that enhances agent skill self-evolution by adaptively fusing task-specific execution trajectories with distilled, structured experience from public skill version histories, resulting in significant performance improvements and stronger cross-model transfer capabilities.
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
In the rapidly evolving world of artificial intelligence, researchers are teaching computer programs to act more like human assistants. These programs, often called agents, do not just answer questions; they perform tasks by using tools, following instructions, and managing files. To make these agents reliable, developers give them "skills." Think of a skill as a portable toolbox containing a set of instructions, scripts, and resources that the agent can pick up and use whenever it faces a specific type of problem. However, just as a human learns from mistakes, these tools are rarely perfect when first created. As the world changes and new challenges arise, the instructions inside these toolboxes need to be updated, patched, and improved. The central question for scientists is how to automate this improvement process so that the agents can teach themselves to become better over time.
For some time, the standard approach to this self-improvement has been to let the agent try a task, watch where it fails, and then rewrite the instructions based on that specific failure. This method relies entirely on the evidence gathered during the current attempt. While this works, it has a blind spot: it only sees the mistakes that happen right now. It misses the broader lessons that other developers have learned over years of maintaining similar tools. A team of researchers from the Chinese Academy of Sciences and the Beijing University of Post and Telecommunications realized that this narrow focus was leaving a vast library of knowledge untapped. They set out to see if the history of changes made to public software tools could teach an agent something that its own immediate experience could not.
The researchers began by comparing two different sources of information. The first source was the agent's own recent attempts at a task, which provided a detailed but narrow view of what went wrong. The second source was the public history of changes made to similar tools by human developers over time. When they analyzed these two sources side by side, they discovered a clear and useful difference. The agent's own attempts mostly focused on fixing immediate, specific errors in how it called tools or read instructions. In contrast, the public history contained a much wider variety of improvements, including changes to how data was organized, how scripts were structured, and how the tool handled unexpected situations. The public records offered a broader perspective, while the agent's own records offered a grounded, task-specific reality. The two sources did not repeat each other; instead, they filled in each other's gaps.
To put this insight to work, the team developed a new system called VCE-Skill. This system acts as a bridge between the agent's current experience and the collective wisdom of the past. The process happens in two main stages. First, the system takes the raw, messy history of changes from public repositories and cleans them up. It strips away the specific details that only apply to one project and distills them into general, reusable lessons. For example, if many developers have added a check to ensure a file exists before trying to open it, the system learns this as a general rule rather than a single fix. These distilled lessons are stored in a structured library of experience.
In the second stage, the agent attempts a task and generates its own ideas for improvement based on what happened. The system then looks at its library of distilled lessons and selects the ones that are most relevant to the current problem. It does not simply copy the old lessons or ignore the agent's own ideas. Instead, it carefully blends the two. If the agent is struggling with a common issue that the public history has solved many times before, the system leans heavily on that external wisdom. If the agent is facing a unique, strange error that has never been seen before, the system trusts the agent's own observation more. This balance is not fixed; the system constantly adjusts how much it trusts the external library versus the agent's own experience, depending on whether the changes are actually making the agent perform better.
The results of this approach were tested across five different types of tasks, ranging from answering complex questions and managing spreadsheets to controlling robots in virtual environments. The researchers used four different large language models to act as the agents. In every case, adding this external experience to the agent's self-improvement loop led to better performance. The agents scored higher on average, with improvements ranging from about three to five points across the various tests. More importantly, the skills that were improved using this method proved to be more robust. When the researchers took a skill that had been evolved with this new method and tested it on a different computer model than the one it was trained on, it performed significantly better than skills that had only learned from their own immediate mistakes. This suggests that by incorporating the broader lessons from public history, the agents learned more general principles that could be applied in new situations, rather than just memorizing how to fix a specific error.
The study does not claim that the old way of learning from mistakes is useless. The agent's own experience remains essential for understanding the specific details of the task at hand. The new method simply adds a layer of context that the agent could not find on its own. By treating the history of public software changes as a valuable source of prior knowledge, the researchers have shown that agents can learn to evolve more effectively. They have demonstrated that the path to a smarter, more reliable agent is not just about watching what happens in the moment, but also about understanding the long story of how similar tools have been improved over time. This approach offers a practical way to make artificial intelligence more adaptable, ensuring that the tools it uses are not just functional for today, but robust enough for the future.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.