Automating SKILL.md Generation for Computer-Using Agents via Interaction Trajectory Mining
This paper presents a diagnostic study demonstrating that while interaction trajectory mining can generate readable and high-purity skill libraries for computer-using agents, the current approach fails to translate these insights into reliable cross-domain policy improvements due to limitations in boundary detection, segment representation, and offline reward modeling.
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 robot assistant that can use a computer just like a human: clicking, typing, scrolling, and copying. To make this robot smarter, we often give it a "cheat sheet" called SKILL.md. Think of this cheat sheet as a recipe book. Instead of telling the robot "click here, then type there," the book says, "Here is how to 'Send an Email' or 'Save a File'." These are pre-packaged skills that make the robot's job easier to understand and fix.
Usually, humans have to write these recipe books by hand. But what if we could teach the robot to write its own recipe book just by watching how people use computers? That is exactly what this paper tries to do.
The Experiment: Teaching a Robot to Write Its Own Cookbook
The researchers built a three-step machine to turn raw computer usage data into a recipe book:
- Cutting the Video: Imagine watching a long video of someone working. The machine tries to find the "scene changes." If the person suddenly stops typing and starts scrolling, the machine cuts the video there, thinking, "Okay, that was one task; now they are starting a new one."
- Grouping the Scenes: The machine takes all these little video clips and tries to group similar ones together. If 50 clips all involve "copying and pasting," it puts them in a bucket labeled "Data Transfer." It then creates a digital "fingerprint" for each bucket so the robot can recognize them later.
- Training the Robot: Finally, they teach the robot a new policy (a set of rules) using these buckets. The goal is to see if the robot can look at a new task and say, "First, I need to do the 'Search' skill, then the 'Copy' skill," and actually do it better than before.
The Results: A Mixed Bag
The results were a bit like finding a treasure map that leads to a beautiful island, but the boat you built to get there doesn't sail very well.
The Good News: The Map is Readable
On the specific dataset they used to build the map (called "IW"), the machine did a great job of organizing the data. Five out of eight of its "buckets" were very pure. For example, one bucket was almost entirely made of "Document Editing" actions, and another was purely "Sending Messages."
- Analogy: It's like if you asked a robot to sort a pile of mixed laundry, and it successfully put all the socks in one basket and all the shirts in another. The sorting was clear and easy for humans to read.
The Bad News: The Boat Doesn't Sail
Here is the tricky part: Just because the robot sorted the laundry well doesn't mean it knows how to wear the clothes.
- The Transfer Problem: When they tried to use these sorted skills on new tasks (different websites or different types of work), the robot didn't get any better. In fact, it sometimes got slightly worse.
- The "Frequency" Surprise: The researchers tested the robot against a very simple, silly baseline: a "Frequency Prior." This is just a rule that says, "Whatever skill was used the most often before, do that again." Surprisingly, this dumb rule beat the robot's complex, learned skills.
- Analogy: Imagine you are trying to learn a new language. You study a complex grammar book (the robot's skills), but you keep making mistakes. Meanwhile, your friend just repeats the most common word they heard yesterday ("Hello"), and they actually communicate better than you do in this specific test.
Why Did It Fail?
The paper suggests a few reasons why the robot's "recipe book" didn't help it cook better:
- Missing the Order: The machine grouped actions based on what they were (clicks, types), but it forgot the order. It knew "click" and "paste" were in the same bucket, but it didn't remember that you must click before you paste. It's like having a bag of ingredients for a cake but forgetting the order in which to mix them.
- Wrong Cuts: The machine sometimes cut the "video" in the wrong places. It might think a long pause in typing was a new skill, when it was just the same skill continuing.
- The Reward System: The system used to train the robot (called GRPO) wasn't good enough at giving feedback. It was like a coach who gives vague praise instead of specific corrections.
The Bottom Line
This paper is a diagnostic study, meaning it's more about finding out why something didn't work perfectly than claiming a huge victory.
- What worked: We can automatically mine computer usage data to create a readable, organized list of skills that humans can understand.
- What didn't work: Turning that list into a robot that can actually use those skills to solve new problems is much harder. The current method didn't beat a simple "guess the most common action" strategy.
The authors conclude that while we have a good way to see the structure of how people work, we haven't yet figured out how to turn that structure into a reliable, transferable skill set for robots. The "recipe book" exists, but the robot still needs more practice before it can cook a meal on its own.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.