← Latest papers
💬 NLP

How Well Do Agentic Skills Work in the Wild: Benchmarking LLM Skill Usage in Realistic Settings

This paper presents the first comprehensive benchmark of LLM agent skills in realistic settings, revealing that performance gains from skills are fragile and degrade significantly when agents must autonomously retrieve from large collections, though query-specific refinement strategies can substantially recover this lost performance.

Original authors: Yujian Liu, Jiabao Ji, Li An, Tommi Jaakkola, Yang Zhang, Shiyu Chang

Published 2026-04-07
📖 5 min read🧠 Deep dive

Original authors: Yujian Liu, Jiabao Ji, Li An, Tommi Jaakkola, Yang Zhang, Shiyu Chang

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, super-smart assistant (the AI) who knows a lot about the world but needs help with very specific, tricky jobs. To help them, you give them a "toolbox" of pre-written instructions called Skills. These skills are like cheat sheets, recipes, or step-by-step guides for things like "how to fix a leaky pipe" or "how to write code for a specific website."

This paper asks a simple but crucial question: Does this toolbox actually work when the real world gets messy?

Here is the breakdown of what the researchers found, using some everyday analogies.

1. The "Perfect World" vs. The "Real World"

The Old Way (The Idealized Lab):
Imagine you are taking a driving test. In the old studies, the instructor handed you a map that had the exact route drawn in bright red ink, with every turn labeled. The instructor also said, "You must use this map."

  • Result: The driver (the AI) passed easily.
  • The Problem: This isn't how real life works. In the real world, no one hands you a pre-drawn map. You have to find the map yourself, and you might have to choose between a map for "City Driving" and a map for "Off-Roading" when you're actually driving on a muddy trail.

The New Study (The Real World):
The researchers built a massive library of 34,000 real-world skills (like a giant, messy garage full of tools). They then gave the AI a task and said, "Go find the right tools yourself."

  • The Result: The AI's performance crashed. When the AI had to search for its own tools, it got confused, picked the wrong ones, or ignored the good ones. In the hardest scenarios, the AI did almost as poorly as if it had no tools at all.

2. The Three Big Hurdles

The paper identifies three specific reasons why the AI struggled, which we can think of like this:

  • Hurdle 1: The "Too Many Options" Problem (Selection)
    Imagine you are in a hardware store with 10,000 hammers. You need to hang a picture. The AI often picks the wrong hammer (a giant sledgehammer) or doesn't pick any hammer at all because it's overwhelmed. Even when the right tool was right in front of it, the AI often forgot to grab it.
  • Hurdle 2: The "Bad Search" Problem (Retrieval)
    Imagine you ask the librarian for a book on "cooking pasta," but the librarian hands you a book on "how to build a boat" because the keywords were slightly off. The AI's search engine wasn't perfect; it often missed the right skills or grabbed irrelevant ones.
  • Hurdle 3: The "Rough Draft" Problem (Adaptation)
    Imagine you find a recipe for "Spaghetti Carbonara," but your task is to make "Pasta with Pesto." The recipe is close, but not quite right. The AI struggled to tweak the recipe. It tried to follow the Carbonara instructions for the Pesto dish and failed. It couldn't "translate" the general skill to the specific need.

3. The Solution: The "Smart Editor" (Refinement)

The researchers realized that just dumping a pile of tools on the AI wasn't enough. They needed a way to fix the tools before the AI used them. They tested two strategies:

  • Strategy A: The "Generic Polish" (Query-Agnostic)
    Imagine a professional editor who goes through the library and fixes typos and improves the grammar of every book, without knowing what specific book you are going to read later.

    • Result: It helped a little bit (cleaner text), but it didn't solve the main problem because the books were still about the wrong topics.
  • Strategy B: The "Custom Tailor" (Query-Specific)
    Imagine a tailor who looks at your specific outfit (the task) and then goes to the closet to find the right fabric. They take a piece of a "Winter Coat" pattern and a piece of a "Summer Shirt" pattern, cut them up, and sew them together to make the perfect jacket for your specific day.

    • Result: This worked amazingly well! When the AI was allowed to look at the task first, then search for skills, and finally "stitch together" the best parts of those skills, its performance jumped back up. It recovered most of the lost ground.

4. The Catch

There is one big limit to this "Smart Editor."
If the library doesn't have the right ingredients at all, the tailor can't make a suit out of thin air.

  • If the AI searches for a "Pasta" recipe and the library only has "Boat Building" manuals, no amount of editing will help. The AI needs some relevant starting material to work with.

The Bottom Line

  • Skills are powerful, but fragile. They work great if you hand the AI the perfect, pre-selected guide.
  • In the real world, they often fail because the AI gets lost in the noise or picks the wrong guide.
  • The Fix: We need AI that doesn't just find skills, but adapts them. If the AI can look at the messy, imperfect tools it finds and say, "Okay, I'll take this part from Tool A and that part from Tool B to solve my specific problem," then the system works again.

In short: Giving an AI a toolbox is great, but giving it a toolbox and a smart mechanic who knows how to modify the tools for the specific job is what makes the car actually drive.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →