# Evals — dashboard

`cases.yaml` is a human/LLM-graded trigger and capability set, not an auto-runner. To use it: read each `should_trigger` prompt and confirm an agent routing skills would reach into `dashboard`, then read each `should_not_trigger` prompt and confirm it routes to the named sibling instead (the boundary against `kpi-framework`, `analytics`, `reporting`, `forecasting`, `business-intelligence`, and `ab-testing`) — eyeball the routing, don't just trust the labels. For the `capability` case, have the agent actually produce a `dashboard.yaml` from the 14-metric scenario, then grade the output against the `must_include` rubric and run `scripts/verify.sh path/to/dashboard.yaml`; a real pass means the rubric items are all present AND verify.sh exits 0. verify.sh needs `python3` with PyYAML and is read-only, so it is safe to run on any candidate artifact.
