domains / families / devops / model-routing-orchestrator

model-routing-orchestrator

separate

Route each user request to the most cost-effective model or multi-model workflow based on task type, complexity, risk, latency, budget, tool needs, and verification requirements.

When to use

• which model should answer a given user request
• whether a cheap model is enough
• when to escalate to a stronger reasoning model
• when to use one model versus multiple models
• when to use tools instead of relying on pure model reasoning
• how to handle complex calculations, code, multimodal input, long context, or high-risk tasks
• how to balance cost, speed, and answer quality in production

When not to use

• answer the original business question directly
• fabricate model capabilities without evidence from the environment or configuration
• assume the most expensive model is always the best choice
• route high-risk exact tasks to a cheap model without verification
• rely on pure language generation for exact arithmetic when tools are available

Skill page

Source