# Evals — financial-model

`cases.yaml` holds three groups of prompts for this skill's router and capability. Run them against whatever eval harness the repo provides, or check by hand: feed each `should_trigger` prompt to the router and confirm it selects `financial-model`; feed each `should_not_trigger` prompt and confirm it routes to the named sibling (`finance-ops`, `unit-economics`, `pricing`, `forecasting`, `pitch-deck`, `bookkeeping`) and not here — these encode the boundaries that bleed (near-term liquidity, isolated unit economics, pricing, single-series forecasts, the deck, the ledger). The `capability` case is graded against its `must_include` rubric on an actual generated model: build the model for the given seed scenario and tick each rubric line (separate assumptions layer, MRR waterfall, headcount-driven costs, cash-based runway and cash-out date, cash continuity, base/downside/upside off toggles, raise sized to 18–24 months, a benchmark sanity-check, the unit-economics hand-off). Pair the capability grade with `scripts/verify.sh` against the generated `model.csv` to confirm the artifact actually ties out (continuity, recompute checks, defect lint) — the rubric judges assumption quality, verify.sh judges internal consistency. No automated harness is assumed beyond reading the prompts and checking routing plus the rubric.
