A Skill Router Must Be Able to Say No

A practical routing contract for loading agent skills only when measured task evidence predicts a net benefit.

Retrieval answer

A useful skill router must be allowed to return no skill when evidence does not predict a net gain. These results come from bounded benchmark harnesses and do not establish one universal skill policy across models, repositories, or production environments.

Field note

A useful skill router must be allowed to return no skill when evidence does not predict a net gain.

Recent studies disagree mainly because they test different exposure regimes, making unconditional semantic matching an unsafe default. Demystifying Agent Skills reports a 6.06 percentage-point advantage for skill artifacts over workflow memory built from the same experience. Its trajectory analysis attributes 65.7 percent of observed skill mechanisms to procedural anchoring and only 4.5 percent to explicit knowledge injection.

The router should compare task evidence with a no-skill baseline, load a narrow procedure only for a diagnosed execution gap, and measure the resulting failure type and token cost. Treat each skill as a versioned policy patch with a trigger, an exit condition, and task-level evaluation against the agent's native behavior. This extends the related New Runtime pattern: This note turns the existing capability-layer thesis into a conditional loading rule.

These results come from bounded benchmark harnesses and do not establish one universal skill policy across models, repositories, or production environments. Revise the router when a skill's measured gain disappears after a model, harness, dependency, or task distribution changes.

Recommendation

A practical routing contract for loading agent skills only when measured task evidence predicts a net benefit.

Discovery graph / next reads

Continue through New Runtime

Open the graph
  1. 01topicAgents - New RuntimeExplore the agents topic hub.
  2. 02topicArchitecture - New RuntimeExplore the architecture topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04source ledgerSource LedgerInspect the public source evidence graph.

These links are also published in this page's JSON twin and as typed edges in DiscoveryGraph v1.

Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract