# Evals — monitoring

These cases are run by the repo's eval harness, which loads this skill's `SKILL.md` (description + body) and scores three things with a judge model: that each `should_trigger` prompt selects `monitoring`, that each `should_not_trigger` prompt routes to the named sibling instead (every `route_to` id — `observability`, `error-handling`, `deployment`, `scaling`, `domains-dns` — is a real skill in this catalog), and that a response to the `capability` scenario covers the `must_include` rubric. The rubric is graded on substance, not exact wording: a setup that splits liveness from readiness, picks a concrete dated tool, monitors the critical journey plus cert/domain expiry, alerts on a two-window symptom/burn-rate rule, wires escalation + runbooks, says to test the page end-to-end, and steers clear of Opsgenie for a new setup should pass even if phrased differently. Run them with the standard harness against this directory; there is no special setup beyond the catalog being present.
