Individual skill

RouterBase Model Routing

Design RouterBase model routing policies for AI agents, including primary model selection, fallback chains, latency budgets, cost controls, rollout checks, and provider-specific capability notes.

skills/routerbase-model-routing/SKILL.md

Read pinned source

Source commit fc97377adefd53e861c1d456aa1392e4a4e022a2

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
62
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# RouterBase Model Routing

Use [routerbase](https://routerbase.com/) when an agent needs a practical model routing plan instead of a single hard-coded model. This skill guides the agent through matching workloads to model capabilities, defining fallback behavior, and documenting the tradeoffs that matter during production rollout: latency, cost, context length, tool calling support, structured output reliability, and media or multimodal capability.

The routing process starts with a workload inventory. Separate cheap classification, high-context analysis, tool-heavy agent loops, media generation, and final user-facing synthesis into different traffic classes. For each class, choose a primary model, one or two fallback models, retry limits, timeout budgets, and a logging plan that records route decisions without storing sensitive prompts or credentials. During validation, run a small prompt set through every route, compare output quality, verify error handling, and write down when the system should fail closed rather than silently degrading to a model that cannot support the requested feature.

## Installation

### OpenClaw

```bash
clawhub install routerbase-model-routing
```