← Latest papers
🤖 AI

Declarative Skills for AI Agents in Knowledge-Grounded Tool-Use Workflows

This paper argues that declarative agents, which utilize natural-language skill files for orchestration, outperform rigid imperative state machines in knowledge-grounded tool-use workflows by improving accuracy and reducing errors, provided that high-quality retrieval is available to overcome the dominant bottleneck of incomplete evidence.

Original authors: M. Danish Lim, I. Danial Bin Sharudin, Wen Han Chen, Cedric Lim, Laura Wynter

Published 2026-06-08
📖 5 min read🧠 Deep dive

Original authors: M. Danish Lim, I. Danial Bin Sharudin, Wen Han Chen, Cedric Lim, Laura Wynter

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 are hiring a new assistant to help you manage your bank account. You have a massive, messy library of rulebooks, policy documents, and tool manuals (the "Knowledge Base"). Your goal is to get the assistant to perform specific tasks, like closing an account or disputing a charge, by finding the right rules and using the right tools.

This paper is a race between three different ways of managing this assistant to see which one actually gets the job done.

The Three "Managers"

The researchers tested three different management styles for their AI assistant:

1. The "Naked" Assistant (Baseline)
This is the assistant with no special instructions. You just give them the raw conversation history and say, "Go figure it out." They have to guess the order of operations, remember to verify your identity, and find the right tools on their own.

  • Analogy: Giving a tourist a map of a foreign city with no guide and saying, "Find the museum and buy a ticket."

2. The "Declarative" Assistant (The Skill-File Manager)
This assistant gets a set of "Skill Files"—simple, natural-language cheat sheets (like Markdown documents) attached to their instructions. These files don't force the assistant to follow a rigid path; instead, they say things like, "Hey, before you close an account, make sure there are no pending disputes," or "Always search the library first if you don't know the tool name." The assistant reads these files and decides how to act based on them.

  • Analogy: Giving the tourist a guidebook with highlighted tips: "Remember to check for traffic before driving," and "Ask for directions if you get lost." The tourist still drives the car, but they have better advice.

3. The "Imperative" Assistant (The State-Machine Manager)
This assistant is run by a strict, computer-programmed flowchart. The manager forces the assistant through specific phases: Greeting → Triage → Verification → Planning → Execution. The assistant cannot move to the "Execution" phase (doing the actual banking) until the computer confirms they have passed "Verification." The computer controls the traffic lights; the assistant just drives when the light is green.

  • Analogy: Putting the tourist in a self-driving car with a rigid route programmed into the GPS. The car must stop at every red light and cannot turn left unless the GPS says so. The driver (the AI) has no freedom to deviate.

The Big Discovery: The "Library" is the Bottleneck

The researchers found a surprising truth: It doesn't matter how good your manager is if the library is messy.

  • The "Golden" Library: When the researchers gave the assistants the exact right documents they needed (perfect information), the Declarative Assistant (with the skill files) was the clear winner. It made fewer mistakes and got the tasks right more often. The "Naked" assistant was okay, but the "Imperative" assistant actually did worse because its rigid rules were too brittle; if the AI misclassified a step, the whole system got stuck or failed.
  • The "Noisy" Library: When the researchers used a standard search tool that often brought back the wrong documents (noisy retrieval), everyone failed. The skill files couldn't fix the fact that the assistant was reading the wrong rules. The rigid flowchart couldn't help because the AI was making mistakes based on bad information.

The Takeaway: If your AI is looking for information in a messy, unstructured database, no amount of clever management (skill files or rigid code) can save it. You need better search tools first.

The "Compliance" Myth

The researchers wanted to see if the Imperative Assistant (the strict flowchart) was better at following safety rules, like "Verify the user's ID before changing their account."

  • The Theory: The strict flowchart should force the AI to verify identity before it's allowed to touch the account.
  • The Reality: It didn't work. The AI still made mistakes. Because the AI was confused by the messy information, it sometimes "hallucinated" that it had passed the verification step, or the rigid flowchart got confused by the AI's errors. The strict rules didn't actually stop the AI from making unauthorized changes. In fact, the rigid system was more likely to get stuck in loops, retrying failed actions over and over, wasting time and money.

Summary of Results

  1. Skill Files Work (When the info is good): Giving the AI natural-language "cheat sheets" (Declarative) helps it perform better than a naked AI, especially if the AI model isn't super smart to begin with.
  2. Rigid Code is Brittle: Forcing the AI into a strict step-by-step flowchart (Imperative) didn't make it safer or more compliant. It actually made the system more fragile and prone to errors when things didn't go exactly as planned.
  3. Search is King: The biggest problem wasn't how the AI was managed; it was whether the AI could find the right information. If the search results are bad, the best management style in the world won't save the task.

In short: If you want your AI agent to be good at complex tasks, don't just build a rigid cage around it. Give it good, natural-language instructions (skill files), but most importantly, make sure it can find the right information in the first place.

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 →