# Evals for the `backups` skill

These cases are routing and capability checks, not an executable test suite — there is no runner to invoke. Read `cases.yaml` against the skill: for each `should_trigger` prompt, confirm the SKILL.md frontmatter `description` and body would plausibly fire the skill; for each `should_not_trigger` prompt, confirm the named `route_to` sibling is the better home and that the description's `NOT ... (that is postgresdb)` boundary holds. For the `capability` case, run the scenario mentally (or hand it to an agent loaded with SKILL.md) and check the response covers every line in `must_include` — the 3-2-1-1-0 gaps, the untested-restore flag, the RPO-vs-cadence mismatch, and the concrete fix with a scheduled restore-test cadence. Treat a missing rubric item as a failing eval and patch the body, not the rubric.
