Imported from projectious-work/aibox (context/templates/processkit/v0.26.14/context/skills/processkit/model-recommender/SKILL.md). Install upstream with npx skills add projectious-work/aibox --skill model-recommender. Copyright stays with the author.

Model Recommender

Intro

This skill scores AI models across six capability dimensions, two gate dimensions (Availability and User Access), and per-token pricing — then helps you pick the right model. Persistent Role and TeamMember routing uses provider-neutral Artifact(kind=model-profile) artifacts; those profiles expand to concrete Artifact(kind=model-spec) candidates only after runtime access gates are applied. It has three workflows: Profile View (spider-chart for one or more models, with optional sub-dimension drill-down), Task Router (cluster a task plan and route each cluster to the optimal model), and Roster Refresh (live internet research to update benchmark scores and discover new models). Gates always apply before capability scoring: a model the user can't access or that is currently down is excluded regardless of how well it scores.

For the complete provider/model/version characteristic matrix, including open-weight metadata, token accounting, rate limits, and model-class routing, see references/model-characteristics.md.

Overview

The six dimensions

Every model and every task is evaluated against the same six axes. Each scores 1–5.

The qualitative G 1–5 score is a fast filter; for hard requirements (HIPAA, GDPR, jurisdiction), use the structured fields on each roster version entry:

• jurisdiction.vendor_hq_country (ISO-3166-1 alpha-2)
• jurisdiction.applicable_legal_regimes[] (e.g. EU-GDPR, US-HIPAA, CN-DSL)
• jurisdiction.data_residency_regions[]
• data_privacy.dpa_available
• data_privacy.data_retention_days (0 / "zero" for no retention)
• data_privacy.training_on_customer_data (never|opt-in|opt-out|always|unknown)
• data_privacy.pii_eligible, phi_hipaa_eligible, gdpr_eligible
• data_privacy.sub_processors_url

These fields back the G score with auditable facts and let query_models() filter on a hard requirement instead of a fuzzy 1–5 cutoff (e.g. require data_privacy.phi_hipaa_eligible == true before any HIPAA-touching task is routed).

Each roster version entry also carries:

• knowledge_cutoff (date) — vendor-published training cutoff
• vendor_model_id — exact SDK model id (claude-opus-4-7-20251031)
• latency_p50_ms — quantitative companion to S score

Roster records may also carry:

• model_classes[] — fast, standard, and/or powerful routing class hints
• architecture — parameter count, tokenizer, quantization, base/instruct lineage
• license — open-weight and commercial-use terms
• deployment — self-hosting/runtime/VRAM facts
• supported_parameters[] — tools, structured outputs, prompt caching, reasoning, grounding, batch, and similar endpoint features
• versions[].token_accounting and versions[].rate_limits

Score rubric:

Gate dimensions (applied before capability scoring)

Gates are binary — they disqualify a model entirely, not partially. Apply them first; only models that pass both gates are scored on the six dimensions.

Gate 1 — User Access: Does the user have an active subscription, API key, and sufficient quota for this model? Ask at the start of any routing session if unknown. Maintain user access state in mcp/user_config.json via set_config(available_models=[...]). The MCP query_models and list_models tools respect this automatically.

Gate 2 — Availability: Is the provider's API currently operational? Check with check_availability() for live status. Three sub-states:

• operational — no known issues
• degraded — elevated error rate or latency; usable but risky for production
• major_outage — do not route here; escalate to fallback

Additional flags to surface when relevant:

• Rate limit exhausted — user has hit their per-minute or daily cap; fallback required
• Quota / budget exceeded — subscription limit reached; model is effectively unavailable
• Subscription expired — no access until renewed

When a model's gate status is unknown, ask the user rather than assuming it passes.

Cost and value

Cost is a sub-dimension of Speed (S.cost_efficiency) in the spider chart but is also surfaced explicitly because raw per-token prices and derived value matter independently of speed.

Model profile routing: default Role/TeamMember bindings target Artifact(kind=model-profile) entities named for capability needs (code-balanced, general-fast, research-deep), not providers or model families. Concrete provider/model names belong in model-spec artifacts and in the profile's candidate list. This keeps identities and roles portable across Codex, Claude Code, Gemini CLI, Aider, Continue, Cursor, Copilot, OpenCode, Hermes, and future harnesses.

Per-token pricing: stored on each Artifact(kind=model-spec) under spec.versions[].pricing and normalized by the MCP server. Use get_pricing() to view and sort. Self-hosted models (Llama) have null API pricing — infra cost applies instead.

Value score: (R + E + L) / 3 / output_cost_per_1M × 10. Higher is better. Surfaces models with frontier-class capability at low cost. DeepSeek models score highest on value but are excluded for G-sensitive work.

When the user asks "what's the best value for money" or has a per-hour budget, use get_pricing(sort_by="value_score") and filter by accessible models.

MCP tools

The mcp/server.py provides structured queries over the roster. Use these instead of reading markdown files when the user asks for comparisons, filtered lists, or pricing analysis.

Workflow A — Profile View

Use when the user wants to understand a specific model or compare two.

Output format (render one block per model):

Model: Claude Sonnet 4.6
Provider: Anthropic · Tier: Frontier mid-size · Updated: 2026-Q1
────────────────────────────────────────────────
  Reasoning    ▓▓▓▓▓▓▓▓░░  4/5  Strong
  Engineering  ▓▓▓▓▓▓▓▓▓▓  5/5  Exceptional
  Speed        ▓▓▓▓▓▓░░░░  3/5  Moderate
  Breadth      ▓▓▓▓▓▓▓▓░░  4/5  Strong
  Reliability  ▓▓▓▓▓▓▓▓░░  4/5  Strong
  Governance   ▓▓▓▓▓▓▓▓▓▓  5/5  Exceptional
────────────────────────────────────────────────
Best for:   Complex coding, code review, refactoring, agentic workflows,
            tasks touching sensitive data or enterprise privacy requirements
Avoid for:  Extreme cost sensitivity at very high volume, real-time <100ms
            UX, native audio/video processing

Bar widths: 5→▓▓▓▓▓▓▓▓▓▓, 4→▓▓▓▓▓▓▓▓░░, 3→▓▓▓▓▓▓░░░░, 2→▓▓▓▓░░░░░░, 1→▓▓░░░░░░░░

For head-to-head comparison of two models, render both blocks, then add a one-paragraph verdict: which model wins overall and for what use cases.

Sub-dimension drill-down: When the user wants detail on a specific dimension (e.g., "which of these two is better at tool use?"), call compare_models([...], scope="E") and render the sub-dimension table:

Engineering sub-dimensions: Claude Sonnet 4.6 vs GPT-4o
─────────────────────────────────────────────────────
Sub-dimension          Sonnet 4.6   GPT-4o
Function codegen            5          4
Repo-scale tasks            5          4
Tool use / BFCL             5          4
Agentic planning            5          3
Codebase navigation         5          4
─────────────────────────────────────────────────────
Top-level E score           5          4

Trigger: "drill down on [dimension]", "compare at the detail level", "which is better at [sub-dimension]", "I need strong tool use specifically".

Workflow B — Task Router

Use when the user has a plan, task list, or backlog and wants to know which model to use for which work. This is the Dispatch matching mode: tasks are missions, models are heroes.

Steps:

1. Parse the task list. Accept any format: markdown bullets, numbered list, WorkItems, or a free-form plan.

2. Classify each task with a fine-grained task class when possible (architecture, code_review, summarization, rag, ocr, low_latency_chat, etc.). These classes are routing hints, not a replacement for the six R/E/S/B/L/G dimensions.

3. Score each task against the six dimensions: which dimensions does this task require? Use the Task Scoring Quick-Reference below.

4. Cluster tasks by their dominant dimension profile. Tasks with the same top-2 dimensions belong in the same cluster. Typical clusters:

   • Deep-Think (R+E dominant) — complex architecture, novel algorithms
   • Production-Coder (E dominant) — routine implementation, bug fixes
   • High-Volume (S dominant) — repetitive generation, bulk transforms
   • Long-Context (B dominant) — large codebase sweeps, doc analysis
   • Privacy-First (G dominant) — PII, PHI, regulated data, secrets

5. Recommend a model per cluster from the user's accessible models. Call query_models(R=..., E=..., G=..., task_class="...", apply_user_filter=True) to find the best available match. State the primary recommendation and one fallback.

6. Theoretical-best hint. After recommending from the user's accessible models, run the same query with apply_user_filter=False. If the theoretical-best model differs from the recommended one, show the hint:

   ⚡ Theoretical best (not in your access): Claude Opus 4.6
      Gap: R:5 E:5 vs your best R:4 E:5 — 1 point on Reasoning matters for
      this cluster (novel algorithm design). Consider adding Opus access if
      the task justifies it → anthropic.com/api
   

   Omit the hint if the user's accessible model already matches the theoretical best, or if the gap is only 1 point on a non-dominant dimension.

7. Output the routing table:

Task Routing Analysis
══════════════════════════════════════════════

Cluster 1 — Deep-Think (Reasoning + Engineering)   [N tasks]
  Profile:    R:5  E:5  S:2  B:3  L:4  G:4
  Your model: Claude Sonnet 4.6  (fallback: Qwen 2.5 Coder 32B self-hosted)
  ⚡ Theoretical best: Claude Opus 4.6 — R gap: 4→5; worth it for novel algorithms
  Tasks:
    • Design consensus algorithm for distributed cache
    • Refactor auth middleware to zero-trust model

Cluster 2 — Production-Coder (Engineering)          [N tasks]
  Profile:    R:3  E:5  S:3  B:3  L:4  G:4
  Your model: Claude Sonnet 4.6  (no gap — this is the theoretical best)
  Tasks:
    • Implement JWT refresh token rotation
    • Add pagination to /api/v2/users endpoint

Cluster 3 — High-Volume (Speed)                     [N tasks]
  Profile:    R:2  E:3  S:5  B:3  L:3  G:3
  Your model: Claude Haiku 4.5  (fallback: Gemini Flash 2.0)
  ⚡ Theoretical best: Gemini Flash 2.0 — slightly cheaper at this volume;
     only matters if processing >10M tokens/month
  Tasks:
    • Generate unit test stubs for all 200 endpoints
    • Reformat 5,000 changelog entries to new template

Cluster 4 — Privacy-First (Governance)              [N tasks]
  Profile:    R:3  E:3  S:3  B:3  L:4  G:5
  Your model: Llama 3.3 70B self-hosted  (no gap — self-hosted is optimal)
  Tasks:
    • Process patient consent records
    • Summarize HIPAA audit logs

══════════════════════════════════════════════
Total: N tasks across M clusters.
Suggested sequence: Cluster 4 → Cluster 1 → Cluster 2 → Cluster 3.

Workflow D — Setup Questionnaire

Use when the user says "set up my models", "configure my access", "which models do I have access to", "help me set up the recommender", "onboard me", or "I only have access to X". Replaces manual JSON editing with a guided conversation.

Steps:

1. Show current state. Call get_config(). If available_models is non-empty, say "You currently have [N] models configured — I'll update your settings." If empty, say "Your model access isn't set up yet. Let me walk you through it."

2. Ask about provider access. One question, accept a free-form answer:

   "Which AI providers do you have active API access to? Options: Anthropic, OpenAI, Google (Gemini), Meta/self-hosted (Llama), Mistral, xAI (Grok), Cohere, Alibaba/Qwen, MiniMax, DeepSeek, Microsoft (Phi), or other."

3. For each confirmed provider, ask about model tiers:

   • Anthropic: "Do you have Haiku only, Haiku + Sonnet, or full access (all three)?"
   • OpenAI: "Standard (GPT-4o), reasoning tier (o3/o4-mini), or both?"
   • Google: "Gemini 2.5 Pro, Flash, or both?"
   • Open-source (Llama/Qwen/Phi/Gemma): "Self-hosted or via a third-party API (Together, Groq, etc.)?" — this determines the effective G score.
   • Others: accept the provider-level answer.

4. Data sensitivity floor. One question:

   "What's the highest sensitivity of data you typically work with in this project? (a) Public only — open-source code, public information (b) Internal / proprietary — code or business data that isn't public (c) Personal data — names, emails, addresses, any PII (d) Regulated — HIPAA (medical), financial, legal, or government data" Map: (a)→G:0, (b)→G:3, (c)→G:4, (d)→G:5.

5. Budget preference. One question:

   "Budget preference? (a) Cost-first — use the cheapest model that meets the requirement (b) Balanced — trade off cost and quality (c) Quality-first — use the best model regardless of cost" Map: (a)→low, (b)→medium, (c)→high. Set budget_tier.

6. Exclusions. One question:

   "Any models to always exclude? (e.g., 'no DeepSeek', 'nothing from China', 'only Anthropic')" Parse response and add to blocked_models.

7. Summarise and confirm. Display a brief summary:

   Here's your configuration:
     Accessible models: [list]
     Governance floor:  G:4 (personal data)
     Budget:            balanced
     Blocked:           deepseek-v3, deepseek-r1
   Apply this? (yes / adjust)
   

8. Apply. On confirmation, call set_config(...) with all fields. Then call list_models() and show the effective roster so the user can verify it looks right.

Workflow C — Roster Refresh

Use when the user says "update the model scores", "check for new models", "are there newer benchmarks", or "refresh the roster". This is the only workflow that requires internet access.

Steps:

1. Check validated date. Read the current roster metadata via the MCP server or _meta.validated from the packaged model_scores.json projection. If less than 3 months old, ask the user if they want to proceed anyway.

2. Discover new models. Web-search for "new LLM models [current year]" and "AI model releases [last 3 months]". For each new model found:

   • Note it as a candidate addition (do NOT auto-write a roster file)
   • Report it to the user with a one-line capability summary
   • Ask: "Do you want me to add [model] to the roster?"
   • Only add after explicit confirmation; adds are additive (never overwrite existing entries)

3. Refresh benchmark scores. Fetch current leaderboard pages listed in _meta.leaderboards. For each model already in the roster:

   • Check if its SWE-bench rank has changed significantly
   • Check if its LMSYS Arena Elo has moved by >50 points
   • Check Artificial Analysis for latency/cost updates
   • Propose score changes as a diff — do NOT auto-apply

4. Check for new benchmarks. Search for benchmarks that have gained traction since the last validated date (e.g., new agentic evals, new multimodal evals). If found, assess whether they warrant a new sub-dimension. Report to user; do NOT add sub-dimensions without discussion.

5. Check pricing. Fetch the provider pricing pages in _meta.pricing_pages. Compare to stored pricing fields. Report any price changes.

6. Present proposed changes. List:

   • New models to add (awaiting confirmation)
   • Score adjustments (with before/after and source)
   • Price updates (before/after)
   • New benchmark candidates

7. Apply only confirmed changes. Update the relevant timestamped context/artifacts/ART-YYYYMMDD_HHMM-ModelSpec-*.md model-spec artifacts first. If the packaged model_scores.json projection is kept for compatibility, refresh it from the artifacts and bump _meta.validated to the current quarter.

Constraint: refresh is additive. Never delete models from the roster during refresh merely because they are no longer top-ranked. If a provider still offers a model, keep it and update its lifecycle:

• active — current normal routing candidate.
• legacy — still offered; useful for price, compatibility, or a niche task.
• deprecated — provider announced retirement or alias migration; include deprecated_after / replacement_model when known.
• retired — no longer callable; excluded from active routing unless explicitly requested.
• unverified — observed but not fully validated from primary sources.

Task Suitability Classes

Task classes are a second routing layer on top of the six dimensions. They capture concrete work types so an older or cheaper model can remain preferred for suitable work while frontier models are reserved for tasks that justify their cost.

Use list_task_classes() for the live catalogue. Current classes include:

architecture, algorithm_design, debugging, implementation, refactoring, code_review, test_generation, repo_navigation, agentic_workflow, tool_calling, structured_output, data_extraction, summarization, long_context_synthesis, rag, citation_answering, research_synthesis, math_reasoning, scientific_reasoning, legal_analysis, medical_admin, financial_analysis, translation, multilingual_chat, classification, sentiment_analysis, creative_writing, marketing_copy, data_analysis, sql_generation, spreadsheet_analysis, ocr, image_understanding, chart_understanding, diagram_reasoning, voice, audio_transcription, video_understanding, low_latency_chat, bulk_generation, privacy_sensitive, self_hosted_enterprise.

Examples:

query_models(task_class="architecture", R=4, E=5, limit=3)
query_models(task_class="summarization", min_task_suitability=4, S=4)
query_models(task_class="privacy_sensitive", G=5, require_task_suitability=True)

Task Scoring Quick-Reference

A task can score high on multiple dimensions. When in doubt, assign the top-2 and cluster on those.

Model roster summary

The roster contains 62 models across 17 providers, with lifecycle metadata that separates availability from ranking. Estimated or unverified models are marked on the model-spec artifact and surfaced by the MCP projection as _estimated: true or lifecycle: "unverified"; validate them via Workflow C before production routing.

Live table: list_models() — returns the roster filtered by your user config.
Full table with context windows: see references/roster-quick-ref.md.
Narrative profiles: see references/model-profiles.md.

Providers covered: Anthropic, OpenAI, Google (API + open weights), xAI (Grok), Meta/Llama, Alibaba/Qwen, Moonshot/Kimi, Z.AI/GLM, Microsoft/Phi, MiniMax, Mistral, Cohere, DeepSeek, AWS Nova, NVIDIA Nemotron, Xiaomi/MiMo.

⚠️ G:1 warning: DeepSeek APIs, Alibaba Cloud API, MiniMax API, and any unreviewed Xiaomi-hosted MiMo API operate under Chinese jurisdiction. Never route sensitive, regulated, or personal data to these APIs. Self-hosting their open weights raises governance to G:3–4.

Commands

• /pk-route task-description — route a task or task plan to the optimal AI model
• /pk-model-setup — run the guided questionnaire to configure model access and preferences
• /pk-model-refresh — run Workflow C to research and refresh the model roster from live benchmarks
• /pk-explain-routing role [seniority] [scope] — explain the role routing trace

Gotchas

• Skipping the gate check before routing. Always check User Access and Availability before scoring capability. A model scoring E:5 G:5 is useless if the user's API key is expired or the provider is in a major outage. Call check_availability() and get_config() at the start of any Task Router session, or ask the user explicitly if MCP is unavailable.

• Assuming access from context. If the user mentions "Claude" it does not mean they have Opus, Sonnet, and Haiku — they may only have one tier. Ask or call get_config() before recommending a specific tier.

• Recommending a model the user has rate-limited. Rate limits and quota exhaustion are not visible on status pages — they are per-account states. If the user says "it keeps failing", check for rate-limit errors before re-routing to the same model. Suggest the next model in the fallback chain.

• Conflating low cost with high value. DeepSeek models have the highest raw value score but score G:1, which disqualifies them for most enterprise work. Always surface the governance warning alongside the value score when a low-cost model has a G:1 or G:2 rating. Cost optimization within a G floor is the correct framing, not raw cost minimization.

• Not telling the user the actual price. When recommending a model for a bulk task ("generate 10,000 descriptions"), compute an estimate: (estimated tokens × price per 1M / 1,000,000). Even a rough estimate ($0.50 vs. $8.00) changes the decision. Use get_pricing() for current rates.

• Treating the roster as current truth. Model scores change with every release. The profiles in references/model-profiles.md have a "validated" date. If the user's model is newer or the date is >6 months old, caveat your recommendation and point to Artificial Analysis or LMSYS Arena for live data.

• Recommending a model the user can't access. Before recommending o3 or Opus 4.6, ask (or check context) whether the user has access and budget. A perfect score on paper is useless if the quota is exhausted or the model is not provisioned. Offer a concrete fallback every time.

• Scoring the task instead of the task cluster. When routing a plan, assess what the cluster as a whole needs, not individual task quirks. One unusual subtask should not pull an entire cluster to a different model.

• Ignoring the Governance dimension for "internal" work. Many teams assume internal code is not sensitive. But source code with credentials, unreleased algorithms, or regulated business logic can be just as sensitive as PII. When in doubt, ask whether the organization has an AI data classification policy before routing to non-sovereign models.

• Conflating Speed with Engineering. A fast model (S:5) is not necessarily a good coder (E:5). Haiku and Flash are excellent at high-volume, low-complexity code tasks but will struggle with novel architecture or debugging subtle async races. Always check both dimensions before routing engineering work to a speed-optimized model.

• Presenting scores as objective benchmarks. The 1-5 scores in this skill are informed calibrations, not direct benchmark readings. When the user needs precision (e.g., choosing between two models scoring 4 vs. 4 on the same dimension), surface the underlying benchmarks (SWE-bench Verified, GPQA Diamond, BFCL v4) and link to current leaderboards. The skill's scores are a starting point, not the final word.

• Over-routing to expensive models. The task router should push work toward the cheapest model that meets the required profile, not the highest- scoring model globally. Opus 4.6 is not the right answer for a task that only needs E:3 S:4 — that is Haiku or Sonnet territory.

• Skipping the sequence suggestion. After clustering, always add a recommended execution sequence. Some clusters are prerequisites for others (e.g., design decisions made with Opus should precede implementation with Sonnet). The sequence is often more valuable than the per-cluster picks.

• Calling set_config without user confirmation. set_config overwrites user_config.json in full — it is marked destructiveHint: true. Always show the proposed configuration to the user and wait for explicit approval before calling set_config. Never chain set_config into a batch of other calls.

• Treating check_availability failures as errors. check_availability makes live HTTP requests to provider status pages. Network failures, rate limits, and subscription expiry are not detectable from status pages. Treat any failure or non-operational status as unknown, report it to the user, and do not retry more than once without explicit user awareness.

Full reference

Sub-dimension detail

Full sub-dimension specs, benchmark mappings, and scoring guidelines are in references/dimension-specs.md. For structured sub-dimension comparison, use compare_models(model_ids, scope="R") (or E/S/B/L/G).

Complete model profiles

Narrative descriptions, per-sub-dimension scores, and best-for/avoid-for lists are in references/model-profiles.md. Structured model records are canonical in timestamped context/artifacts/ART-YYYYMMDD_HHMM-ModelSpec-*.md files as Artifact(kind=model-spec); the MCP server is the preferred interface for queries and may retain mcp/model_scores.json as a packaged projection.

Pricing and value analysis

• get_pricing(sort_by="value_score") — ranked by capability per dollar
• get_pricing(sort_by="output_per_1m") — ranked cheapest output first
• Provider pricing pages are in mcp/model_scores.json under _meta.pricing_pages
• For bulk cost estimates: tokens × (output_price / 1,000,000)
• Self-hosted models (Llama): no API cost, but require GPU infra (~$1–3/hr/A100)

Availability and user access

• check_availability() — fetches live status from provider status pages
• get_config() / set_config(...) — manage user access list and governance floor
• Provider status pages: mcp/model_scores.json under _meta.status_pages
• Rate limits and quota: must be checked manually via the provider's API dashboard (Anthropic: console.anthropic.com, OpenAI: platform.openai.com, etc.)

Dimension trade-off map

Common trade-offs to surface when the user is torn between two options:

How scores were derived

Scores are calibrated from:

• Public benchmarks: SWE-bench Verified (E), GPQA Diamond (R), MATH/AIME (R), BFCL v4 (E+B), LMSYS Arena Elo (L), Artificial Analysis Intelligence Index (R+E)
• Provider documentation and model cards for Speed and Governance dimensions
• Practitioner reports and Artificial Analysis latency/cost benchmarks

Keeping profiles current

When a major new model releases or an existing model is updated:

1. Add or update its entry in references/model-profiles.md
2. Update the summary table in SKILL.md Overview
3. Bump the validated date in model-profiles.md
4. If scores change significantly, note what changed and why

Anti-patterns

• Single-dimension routing. Never pick a model on one dimension alone. A model that excels at reasoning but scores L:2 on reliability will produce confident, wrong answers. Always check the dimensions that matter for the task's tolerance for error.
• Assuming "best overall model" = right model. The highest-ranked model on LMSYS Arena is not always the right pick. A task requiring G:5 rules out the entire LMSYS top tier (all score G:2 or lower). Optimize for the user's actual constraints, not global rankings.
• Ignoring fallbacks. Always provide a fallback. The recommended model may be unavailable, rate-limited, or over budget mid-session. A router with no fallback fails the user at the worst moment.
• Not re-routing when a cluster grows. If a new task is added to the plan that doesn't fit the cluster's profile, surface it rather than silently absorbing it. A Governance-sensitive task silently absorbed into a DeepSeek-routed cluster is a data breach waiting to happen.