unified-router

Route tasks to optimal LLM engines, models, and thinking depth.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill unified-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unified-router
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/unified-router
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill unified-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The unified-router removes ad-hoc and inconsistent engine/model selection by automatically choosing the optimal LLM engine, model, and thinking depth for each task across Claude Code and Qwen Code, reducing cost, risk, and coordination errors.

Core Features & Use Cases

  • Signal-driven routing: Chooses engine based on authority level, risk tier, MCP server needs, file coordination, and cost sensitivity.
  • Model & depth selection: Selects appropriate models (e.g., opus/sonnet/haiku or qwen3.5/qwen3) and thinking budgets for architecture, implementation, or review tasks.
  • Bidirectional dispatch: Supports offloading from Claude→Qwen, escalation from Qwen→Claude, and new dispatch flags like --think and auto activation for structured handoffs.
  • Use Case: Automatically route a multi-file architecture plan to Claude opus while offloading single-file test generation to Qwen with --think to save tokens.

Quick Start

Ask unified-router to evaluate and dispatch the current task to the optimal engine and model with thinking enabled.

Frequently Asked Questions about unified-router

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

FAQPage Schema
How do I route tasks to the best LLM engine automatically?

To route tasks to the best LLM engine automatically, use signal-driven routing that evaluates authority, risk tier, and cost sensitivity to select the optimal model and thinking depth for your specific task.

How does model selection work for multi-agent orchestration?

Model selection for multi-agent orchestration works by evaluating task requirements and MCP server needs to choose appropriate models, applying dispatch flags like --think for structured handoffs between engines like Claude and Qwen.

Can I offload code generation from Claude to Qwen to save tokens?

Yes, you can offload code generation from Claude to Qwen to save tokens using bidirectional dispatch, which supports offloading single-file tasks while escalating complex multi-file architecture plans to Claude opus.

What is the best way to dispatch architecture planning versus test generation?

The best way to dispatch architecture planning versus test generation is to evaluate risk tier and file coordination, routing multi-file architecture plans to Claude opus while offloading single-file test generation to Qwen with --think.

Does unified routing support auto escalation between different models?

Yes, unified routing supports auto escalation between different models, allowing automatic escalation from Qwen to Claude when task complexity, authority level, or MCP server requirements demand a higher-tier engine.