route-task

Scores tasks on five axes to recommend capability bands and effort levels for model routing.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill route-task-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: route-task
Source: https://github.com/allemaar/open-skills/tree/main/skills/route-task
Command: npx skills add https://github.com/allemaar/open-skills --skill route-task-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding which model or executor should handle a given task is often guesswork. This Skill provides a structured rubric that scores any task on five readable axes (Risk, Uncertainty, Scope, Coupling, Verification) to derive a capability band (0-3) and effort volume (0-24), turning routing decisions into auditable, evidence-based recommendations. ## Core Features & Use Cases - Five-Axis Task Scoring: Rates Scope, Coupling, Risk, Uncertainty, and Verification from 0-4 using anchored criteria read directly from the task, never from agent self-assessments. - Capability and Volume Computation: Maps scores to a capability band (cheapest capable through strongest at max effort) and a volume tertile that positions the effort or reasoning knob the runtime exposes. - Plan Gate Detection: Flags design_open when architecture or design questions are genuinely unresolved, signaling that a phased plan should precede build. - Use Case: Before dispatching a worker to refactor a payment module, run the rubric to discover Risk=4, which routes the task to the strongest available model rather than the cheapest executor. ## Quick Start Ask the agent to score this task with /route-task before dispatching it to a worker model.

Frequently Asked Questions about route-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which model should handle a task?

Score the task on five axes (Risk, Uncertainty, Scope, Coupling, Verification) using the rubric's anchored 0-4 scale. The maximum of Risk and Uncertainty maps to a capability band from 0 (cheapest capable) to 3 (strongest at maximum effort), which the runtime resolves against its own live model roster.

How to score a task for AI model routing?

Rate each of the five axes from 0 to 4 using the anchor definitions, then compute capability as max(Risk, Uncertainty) mapped to 0-3 and volume as (Scope + Coupling + Verification) times 2. Emit the full route record with one evidence sentence per axis as the audit trail.

Does the routing rubric override my model choice?

No, the rubric only recommends and never mandates. It never overrides an explicit handler model choice, never authorizes spend or dispatch, and degrades to the session model whenever the roster is ambiguous or a ladder position cannot be resolved.

What are the limitations of capability-band task routing?

The 1 and 3 anchor scores are deliberately undefined pending calibration, and the max(Risk, Uncertainty) formula cannot distinguish combined high scores from a single high axis. Coupling's dual role as floor and volume input is unvalidated, so surprises should be logged in the report card's feedback field.

When should a plan gate trigger before building?

The plan gate fires as design_open when design or architecture is genuinely unresolved, an architecture finding demands it, or the handler requires a plan. It is evidence-derived and independent of the capability band, signaling that a phased plan should precede the build.