intelligent-router_skill

This skill intelligently routes sub-agent tasks to the most suitable model based on complexity and cost to balance quality and savings.
  • Python

2.6k

GitHub Stars

4

Bundled Files

4 months ago

Catalog Refreshed

6 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill intelligent-router

  • _meta.json1.2 KB
  • install.sh2.2 KB
  • README.md11.3 KB
  • SKILL.md10.4 KB

Overview

This skill provides intelligent model routing for sub-agent task delegation. It selects the optimal model based on task complexity, capability needs, and cost, routing simple work to cheaper models and preserving premium models for high-stakes tasks. The router supports tiered classification, confidence scoring, fallback chains, and agentic task detection to reduce cost and failure rates.

How this skill works

The router analyzes task text with a 15-dimension weighted scoring system and computes a confidence score via a smooth S-curve. It classifies tasks into SIMPLE, MEDIUM, COMPLEX, REASONING, or CRITICAL tiers and picks models configured in your config.json. Automatic fallback chains and retry logic handle failures; agentic patterns bump multi-step tasks to higher tiers. Cost estimates and coding-specific flows guide whether to delegate or run the task on a single premium model.

When to use it

  • When spawning sub-agents or delegating tasks across multiple models
  • When you need to balance cost vs. quality for many small tasks
  • Before running multi-step or tool-using agent workflows
  • When you want automatic retries and fallback behavior on model failure
  • To profile and estimate model costs before execution

Best practices

  • Configure all available models with accurate costs, capabilities, and context windows in config.json
  • Run the classifier or score CLI before spawning sub-agents to check tier and confidence
  • Use the REASONING tier only for formal proofs or step-by-step logic with high confidence thresholds
  • For coding: prefer MEDIUM + SIMPLE QA for small patches and COMPLEX/CRITICAL for multi-file or architecture work
  • Keep fallback chains short (max 3 attempts) and document model failure patterns for future routing improvement

Example use cases

  • Route monitoring and summarization tasks to SIMPLE-tier models to save cost
  • Classify and route code fixes: MEDIUM model for single-file fixes, COMPLEX for multi-file refactors
  • Detect agentic tasks (deploy, test, build) and escalate to appropriate tiers automatically
  • Estimate costs for a planned workload and compare coder+QA cost vs premium model cost
  • Use REASONING tier for theorem proofs or formal verification with confidence >= 0.97

FAQ

Each tier has a primary model and 1–2 fallbacks. On failure the router retries with the next model, up to three attempts total.

When should I override the router's recommendation?

Override when you know a model-specific capability is required (vision, function-calling) or when cost constraints demand a manual selection.

How is agentic detection triggered?

Agentic detection uses action verbs, multi-step patterns, and tool presence; detected tasks are bumped to at least MEDIUM tier.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational