Repository navigation
feat: add opt-in skill-routing modifier - #547
Merged
Merged
Conversation
bompus
force-pushed
the
skill-routing-modifier
branch
from
November 5, 2026 00:59
2b55238 to
75eb55a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an opt-in
skill-routingmodifier (off by default, nothing changes for existing setups): at the start of each task the agent checks what the user is doing and picks the one available skill that best fits, keeps it for follow-ups and small edits, picks again on a new task or changed goal, and uses none (without saying so) when none fits.Problem. With many skills installed, agents often finish a task without calling one that fits, even when the request matches the skill's description. Hosts load only each skill's description up front, so the model has to notice the match on its own.
Evidence (Claude Code 2.1.318,
claude plugin eval, a 60-skill catalog, only the Skill tool allowed, 3 runs per case, tool-call graders on the raw trace, no model judge):Limits. Small: 3 runs and six fit-a-skill prompts in the second test; the first test's cases were written for their skills and were not held out. Only the first message of a task was tested, so the "keep the same skill for follow-ups" bullet has no measurement. The block was supplied as appended system text.
Why a modifier. Some users prefer to rely on skill descriptions alone, and the cost is a little extra reasoning at the start of each task (about 0.1 to 0.5 extra turns per trial here). It composes after Session purpose.
Changes:
rules/modifiers/skill-routing.md, a README modifier row, a CHANGELOG entry under Unreleased.bun test test/(974 pass, 0 fail) andbun run checkpass locally.