The Router Within: Eliciting Native Skill Routing from a Frozen LLM

Ruishuo Chen, Xun Wang, Yu Chen, Zhuoran Li, Longbo Huang

Tsinghua University

Published September 14, 2026 · on the feed September 16, 2026 · ▲ 7 · arXiv 2609.15982

Agents No code arXiv ↗Hugging Face ↗

The abstract

Skills extend an LLM agent beyond its parametric knowledge, and the gain they promise rests on picking the right one. Deployed harnesses route by preloading every skill's metadata into the context, which disperses the agent's attention and caps the library size. Retrieval pipelines move the selection out of the context, but also out of the agent's capability. We show that the frozen agent LLM already carries the routing signal in its own forward passes, and that two linear maps suffice to read it out with no skill text in the context. Gavel (Glance And Verdict from a frozen LLM) reads it in two steps. A glance projects the task's and each skill's mid-layer states through the two maps, the only parameters trained, and scores the full library against compact per-skill banks that one forward pass builds at installation. A verdict then resumes the shortlisted skills' forward passes and reads the model's own likelihood and yes/no judgment, fused with the glance as a product of experts. Trained once, Gavel transfers zero-shot to three public benchmarks and SkillTraj, our new benchmark of 372 simulated agent trajectories. On Qwen3-32B it outperforms progressive disclosure and retrieve-and-rerank pipelines that add 1.2B to 16B external parameters, by up to 13.4 points on written tasks and up to 21.9 when the need for a skill arises mid-rollout. Routing accuracy improves as the backbone does, and in a bash-agent harness the same 32B triggers the correct skill on Skill-Use more often than far larger frontier models running in Codex.

The Brief

2:45

A short podcast summary of the paper. Written and voiced by AI.

Transcript

The Router Within. Eliciting Native Skill Routing from a Frozen LLM. By Ruishuo Chen and four others, from Tsinghua University. Published on the fourteenth of September. No code repository is linked to it.

Skills extend an LLM agent beyond its parametric knowledge, and the gain they promise depends on choosing the right one. Deployed harnesses route by preloading every skill's metadata into the context. That disperses the agent's attention, and it caps how large the library can grow, since every new skill takes up room. Retrieval pipelines move the selection out of the context. But in doing so they also move it out of the agent's own capability, handing the choice to an external system.

The authors show that a frozen agent LLM already carries the routing signal in its own forward passes, and that two linear maps are enough to read it out, with no skill text in the context at all. Their method is Gavel, short for Glance And Verdict from a frozen LLM, and as the name says, it works in two steps.

The glance projects mid-layer states for the task and for each skill through the two maps, which are the only parameters trained. It scores the full library against compact per-skill banks, each built by a single forward pass when the skill is installed. That gives a shortlist cheaply. Because each bank is built once at installation, adding a skill costs one forward pass, and scoring it later needs no skill text in the context.

The verdict then resumes the forward passes of the shortlisted skills and reads the model's own likelihood and its own yes or no judgment. Those readings are fused with the glance as a product of experts, so the final choice has to satisfy both.

Trained once, Gavel transfers zero-shot to three public benchmarks and to SkillTraj, a new benchmark of three hundred and seventy-two simulated agent trajectories. On Qwen3-32B it outperforms progressive disclosure. It also outperforms retrieve-and-rerank pipelines that add between one point two billion and sixteen billion external parameters. The margin reaches thirteen point four points on written tasks, and twenty-one point nine when the need for a skill arises in the middle of a rollout.

Routing accuracy improves as the backbone improves. And in a bash-agent harness, the same thirty-two billion parameter model triggers the correct skill on Skill-Use more often than far larger frontier models running in Codex.

Two contrasts frame the result. Against preloading metadata, Gavel keeps the context clear. Against retrieval, it keeps the decision inside the agent's own forward passes, rather than delegating it to billions of external parameters. The claim underneath is that the model already knows which skill it needs, before any skill text is shown to it. Reading that knowledge out with two small maps keeps routing inside the agent, adds almost nothing in parameters, and lets the library grow without crowding the context.

Paper Quest · 7 chapters · about 40 min

Play this paper

Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.

Chapter 1 🧩 · The problem

Every quest starts with a wall. Here it is a skill library that is too big for the agent's context.

You run an LLM agent with a growing library of skills: packaged instructions and scripts it loads when a task calls for one. A well-chosen skill helps; an ill-suited one leaves the agent worse off than none.

The road ahead

  1. 1 · The problem ~6 min An LLM agent must pick the right skill from a growing library, and both ways of choosing today cost it something.
  2. 2 · What came before ~3 min
  3. 3 · The key idea ~9 min The frozen agent model already knows which skill fits; a cheap glance and a careful verdict read that out from its own internal states.
  4. 4 · Choose your own research ~3 min
  5. 5 · Build the method ~8 min Gavel stores skill banks at install time, glances at the whole library through two maps, then gives a shortlist a full verdict and fuses the scores.
  6. 6 · The experiment ~6 min You’ll guess: When the need for a skill arises mid-rollout, by up to how many points did Gavel beat the strongest rival, pipeline or progressive disclosure?
  7. 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Join free to play the whole quest ›

Free, with Google or an email address. Your stars and progress are kept.

KipQuest: the day’s AI research, as podcasts and quests. All papers Android app Privacy Contact Episodes are written and voiced by AI from each paper. Summaries can contain mistakes: the paper is the source.