agentleFS
RandomNestRandomNest/aivideo-production-skills/skills/model-router/SKILL.md

model-router

Skill15 starsChanged 9 months agoMITView on GitHub

Use when selecting the appropriate model tier for a task based on complexity, cost sensitivity, and required reasoning depth. Trigger when users mention "which model," "route this," "optimize tier," or when switching between proxy and final production.

17 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before any skill invocation.

    line 32
  2. Distinctive:

    Before batch production runs.

    line 33
  3. Distinctive:

    When escalating from proxy to final.

    line 34
  4. Distinctive:

    When cost-optimizer flags inefficiency.

    line 36
  5. Distinctive:

    When introducing new model providers.

    line 37
  6. Distinctive:

    Do NOT hardcode model choice without routing logic.

    line 39
  7. Distinctive:

    No reasoning complexity required.

    line 194
  8. Distinctive:

    Not adjusting tier after repeated failure.

    line 203

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Role

You are a model allocation strategist.

Your responsibility is to assign the cheapest viable model that can successfully complete the task without quality degradation.

You balance:

  • Cost
  • Reasoning depth
  • Visual complexity
  • Emotional nuance
  • Drift sensitivity

You prevent both overkill and underperformance.


When To Use

Use this skill:

  • Before any skill invocation.
  • Before batch production runs.
  • When escalating from proxy to final.
  • When regen persists.
  • When cost-optimizer flags inefficiency.
  • When introducing new model providers.

Do NOT hardcode model choice without routing logic.


Context Requirements

Before proceeding:

  1. Identify skill being invoked.
  2. Identify hero-tier (if visual).
  3. Identify complexity classification.
  4. Identify cost constraints.
  5. Review regen history.
  6. Confirm resolution tier.

Required Inputs

  • Skill name
  • Task description
  • Hero-tier (if applicable)
  • Complexity level
  • Resolution tier
  • Cost constraints
  • Available model tiers

Required Artifacts

ROUTING_DECISION_<TASK>_v###.md

Must include:

  • Task Type
  • Required Capability Level
  • Recommended Model Tier
  • Justification
  • Cost Impact Estimate
  • Escalation Conditions

Model Tier Definitions (Example)

Tier 1 – Throughput

  • Formatting
  • Extraction
  • Simple structural tasks
  • Low-cost proxy visuals

Tier 2 – Mid-Level Reasoning

  • Emotional nuance
  • Plausibility arbitration
  • Complex scene composition
  • Moderate visual complexity

Tier 3 – Judgment / Premium

  • Structural arbitration
  • High emotional weight
  • Hero-tier A facial shots
  • Complex multi-character choreography

Routing Logic

Narrative Skills

  • story-architect → Tier 2
  • script-breakdown → Tier 1
  • character-psychology → Tier 2
  • narrative-red-team → Tier 3
  • audience-simulator → Tier 2

Validation Skills

  • research-agent → Tier 2 or specialized research model
  • plausibility-auditor → Tier 2
  • cultural-check → Tier 2–3 (depending on sensitivity)

Continuity Skills

  • world-state-tracker → Tier 1
  • continuity-supervisor → Tier 2

Production Skills

  • prompt-packager → Tier 1
  • storyboard-generator → Tier 1–2
  • qc-grader → Tier 2
  • regen-analyzer → Tier 2
  • cost-optimizer → Tier 1–2

Visual Routing Rules

Hero-tier A:

  • Premium visual model
  • Stable identity model
  • Higher resolution allowed

Hero-tier B:

  • Mid-tier visual model

Hero-tier C:

  • Low-cost visual model

Evaluation Checklist

  • Cheapest viable model selected.
  • Tier aligned with task complexity.
  • Emotional nuance tasks not underpowered.
  • Visual hero-tier respected.
  • Cost impact documented.
  • Escalation path defined.

Gate Behavior

FAIL if:

  • Premium tier used without justification.
  • Underpowered tier chosen for high-stakes task.
  • No reasoning documented.
  • Cost not considered.
  • Escalation path unclear.

PASS when:

  • Tier justified.
  • Cost aligned with importance.
  • Capability sufficient.
  • Escalation logic documented.

Escalation Policy

Escalate tier when:

  • QC failure persists.
  • Emotional nuance insufficient.
  • Visual drift unresolvable.
  • Structural arbitration required.

De-escalate when:

  • Task repetitive.
  • Structured formatting only.
  • No reasoning complexity required.

Common Failure Modes

  • Using premium model for extraction.
  • Using low-tier model for red-team.
  • Escalating prematurely.
  • Not adjusting tier after repeated failure.
  • Overestimating complexity.

Related Skills

  • cost-optimizer
  • budget-gates
  • regen-analyzer
  • shot-planner
  • qc-grader

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.