Use case
A developer using a coding agent, mid-session, faces current context plus a set of available skills and must decide which skill to invoke next without picking wrong or missing one.
Today people name the skill by hand in the prompt or let the model decide on its own, with no separate ranking or abstention mechanism; this old practice is inferred from the product description, not user testimony.
Once skills multiply, agents pick wrong or invoke everything, forcing developers to correct repeatedly and burn context turns; public material only shows ranking and abstention exist, with no user complaints or adoption data, so pain intensity is a workflow-structure inference.
xOcto's call
Demand is evidenced
Trend: agent capability is moving from the model picking tools itself to an external skill-routing layer that isolates the choice. Entry: target engineering teams already maintaining large internal skill libraries with a retrieval-and-abstention layer; but it depends on a third-party API key and model vendors may absorb skill routing, so the window is narrow.
Reason to use it
Why users would choose it
Inference: versus naming a skill by hand in the prompt, it reads live session context and outputs ranked JSON with abstention, removing the step where the developer decides which skill to call; teams maintaining many internal skills and already using Claude Code hooks are more likely to try it. No retention or repeat-use evidence yet.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Worth trying. Inference: versus naming a skill by hand in the prompt, it reads live session context and outputs ranked JSON with abstention, removing the step where the developer decides which skill to call; teams maintaining many internal skills and already using Claude Code hooks are more likely to try it. No retention or repeat-use evidence yet.
Entry and what to borrow
Trend: agent capability is moving from the model picking tools itself to an external skill-routing layer that isolates the choice. Entry: target engineering teams already maintaining large internal skill libraries with a retrieval-and-abstention layer; but it depends on a third-party API key and model vendors may absorb skill routing, so the window is narrow.