What problem does it solve? Choosing which local or hosted models should fill each routing tier is error-prone: configs drift from what is actually pulled, benchmarks go stale, and broken or oversized models silently occupy slots. This Skill provides a structured audit and selection method so every roster entry is evidence-backed and runs on the target hardware. ## Core Features & Use Cases - Roster auditing: Reconciles configured models against ollama list, flags configured-but-not-pulled and pulled-but-broken entries, and sweeps registry pages for known issues. - Evidence-based ranking: Ranks candidates by agentic benchmarks (SWE-bench Verified, Terminal-Bench, Tau2, NL2Repo) rather than general benchmarks, with dated scores. - Hardware and jurisdiction fit: Assigns models to machine classes by RAM footprint and records vendor origin, hosting, and retention policy in structured fields. - Use Case: A team maintaining an OpenCode/Ollama setup runs a quarterly refresh: the Skill audits the current config, evaluates a newly released model against incumbents, and outputs a JSON roster keyed by router tier with keep/drop/monitor dispositions. ## Quick Start Ask the assistant to review the current ollama model roster against ADR 0007 and produce an updated tiered roster with dispositions.