M
model-router-cost-quality-review
About model-router-cost-quality-review
This skill turns model-routing, provider, cost, quality, latency, fallback, and budget questions into a plan with owners, gates, metrics, and recovery paths. It is for teams designing routing policies and producing evaluation matrices, scorecards, and rollback criteria.
Key features
- 01Map task, quality, and budget needs
- 02Classify routing strategies
- 03Define routing inputs and policies
- 04Design quality checks and fallback behavior
- 05Create eval matrices and cost-quality scorecards
Use cases
- 01Design routing across models
- 02Assess cost versus task quality
- 03Plan fallback for provider failures
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sylphxai/ skills --skill model-router-cost-quality-reviewAfter installing, type/model-router-cost-quality-reviewin Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlreferences/model-router-cost-quality-patterns.md
Details
From the project READMEModel Router Cost Quality Review
Use this skill to convert AI model routing, provider selection, cost, quality, latency, fallback, eval, and budget questions into a concrete artifact with owners, gates, metrics, and recovery paths.
Workflow
- Identify task classes, user tiers, quality bar, latency SLO, context size, tool needs, safety/privacy constraints, provider options, budget guardrails, and observability gaps.
- Read
references/model-router-cost-quality-patterns.md. - Classify routing as fixed, tiered, policy-based, eval-gated, cascade, specialist, fallback, or human-escalated.
- Define routing inputs, route policy, quality checks, cost budgets, fallback behavior, cache rules, safety escalation, and experiment plan.
- Produce router design, state machine, decision table, event schema, eval matrix, cost-quality scorecard, and rollback gates.
When not to use
- Do not use for generic advice the base model already handles without this skill's specific artifact contract.
Guardrails
- Do not optimize token cost before defining task quality, failure severity, and user promise.
- Do not route sensitive, regulated, or customer-confidential inputs to providers without privacy and contract review.
- Do not let fallback silently lower safety, correctness, or tool-call capability.
- Do not use aggregate satisfaction as the only quality signal; include task-specific evals and failure samples.
Output format
Router context:
Audience / source of truth / risk boundary:
Cost-quality routing plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |
Routes, fallback, evals, and budget gates:
- <trigger> -> <policy, metric, edge case, support note>
Comments
Markdown supported