[CVPR 2024] SkillCraft: Can LLM Agents Learn to Use Tools Skillfully?

SkillCraft: Can LLM Agents Learn to Use Tools Skillfully?

Summary
Problem
Method
Results
Takeaways
Abstract

The paper introduces SkillCraft, a benchmark containing 126 long-horizon tasks designed to evaluate if LLM agents can learn and reuse high-level tool compositions ("Skills"). It evaluates state-of-the-art models using Skill Mode, a modular protocol that allows agents to consolidate atomic tool sequences into executable code-based skills, achieving up to 80% reduction in token usage.

TL;DR

The research community has long treated LLM tool-use as a "single-shot" invocation problem. SkillCraft shifts the paradigm toward Procedural Abstraction. It introduces a benchmark and a "Skill Mode" protocol that allows agents to write their own higher-level macro-tools. By caching these tool-chains, top-tier models like GPT-5.2 and Claude-4.5 reduce their token footprint by a staggering 80% while increasing their success on complex, repetitive tasks.

The Motivation: Moving from "Atomic" to "Composite"

In the real world, experts don't just use tools; they build workflows. If you are a developer, you don't just "Search," "Extract," and "Summarize" for every single repository manually—you write a script.

Current LLM agents suffer from "The Flat-Execution Tax":

  1. Redundant State Passing: Manually passing JSON results from Tool A to Tool B via the LLM context.
  2. Context Saturation: Long-horizon tasks fill the context window with verbose API responses, causing the agent to lose the "big picture."

SkillCraft's insight is simple: Intelligence is the efficiency of skill acquisition. If an agent sees a pattern (e.g., fetching GitLab commits for 5 different repos), it should create a process_repo skill and call it repeatedly.

Methodology: The SkillCraft Protocol

The authors expose a lean interface via the Model Context Protocol (MCP) consisting of four primitives: save_skill, get_skill, list_skills, and execute_skill.

The "Skill Mode" Lifecycle:

  1. Exploration: The agent solves a subtask using atomic tools.
  2. Composition: The agent recognizes the sequence and wraps it in a Python script (Skill).
  3. Verification: A Coding Verifier checks for syntax, runtime errors, and "Silent Failures" (e.g., the skill returning empty/null data).
  4. Reuse: For the next 4 subtasks, the agent simply calls execute_skill(params), bypassing the need for multi-step reasoning.

SkillCraft Pipeline Overview Figure 1: The SkillCraft Pipeline—from atomic exploration to verified skill storage and cross-task reuse.

Experiments & Results

The researchers benchmarked several SOTA models, including Claude-4.5-Sonnet, GPT-5.2, and DeepSeek-V3.2.

Key Quantitative Triumphs:

  • Token Efficiency: GPT-5.2 reduced token consumption from 1.23M to 0.26M (-79%) in Skill Mode.
  • Success Amplification: On "Hard" tasks, DeepSeek-V3.2-EXP's success rate soared from 42% to 71% because the skill abstraction kept the context clean and focused.
  • Cross-Model Generalization: In a fascinating "Silicon Skill Sharing" experiment, skills authored by Claude-4.5 were executed by weaker models (like Minimax or GLM) with a 100% success rate.

Experimental Results Table Figure 2: Performance comparison—Skill Mode consistently yields lower costs and fewer tool calls across all models.

Deep Insight: The Hierarchical Paradox

The paper uncovers a vital counter-intuitive finding: Deeper isn't always better. While humans use hierarchical skills (skills calling other skills), SkillCraft found that nested LLM skills suffer from rapid error propagation. If a low-level "fetch" skill returns a slightly malformed JSON, it causes a TypeError three levels up, crashing the entire plan.

  • Flat Skills: 90% Success (GPT-5.2)
  • Hierarchical Skills: 79% Success (GPT-5.2)

This suggests that for current LLMs, shallow, robust, and well-tested skill libraries are superior to complex "tree-like" abstractions.

Critical Analysis & Future Outlook

Takeaway

This work proves that "Skill Creation" is the next frontier for agentic efficiency. Instead of providing 10,000 APIs to an agent, we should provide 100 base APIs and allow it to build its own "Standard Library."

Limitations

  1. Trust and Security: Executing agent-generated Python scripts (even in a sandbox) remains a security concern for production.
  2. Dependency Management: As the Skill Library grows, agents will face "Dependency Hell" similar to modern software development.

Future Work

The next step is likely Collective Skill Learning, where a fleet of agents contributes to a global, version-controlled skill repository, evolving a shared "digital culture" of tool use.


Senior Editor's Note: SkillCraft provides a much-needed "stress test" for the structural intelligence of agents. It moves the conversation beyond "can it follow instructions" to "can it optimize its own existence."

Find Similar Papers

Try Our Examples

  • Analyze recent papers on 'Test-Time Tool Evolution' and 'LLM Skill Discovery' that move beyond static API documentation to dynamic capability acquisition.
  • What is the origin of the 'Model Context Protocol (MCP)' in agentic frameworks, and how does SkillCraft's implementation differ from standard MCP tool calling in terms of state persistence?
  • Explore research regarding 'Error Propagation in Hierarchical Planning' for LLM agents to find potential solutions for the failures observed in SkillCraft's Iteration Mode.
Contents
[CVPR 2024] SkillCraft: Can LLM Agents Learn to Use Tools Skillfully?
1. TL;DR
2. The Motivation: Moving from "Atomic" to "Composite"
3. Methodology: The SkillCraft Protocol
3.1. The "Skill Mode" Lifecycle:
4. Experiments & Results
4.1. Key Quantitative Triumphs:
5. Deep Insight: The Hierarchical Paradox
6. Critical Analysis & Future Outlook
6.1. Takeaway
6.2. Limitations
6.3. Future Work