# Evals: contracts

These cases are routing and coverage checks, not an automated pass/fail suite. Read `cases.yaml` against `SKILL.md`. For each `should_trigger` prompt, confirm the description and body would plausibly fire this skill and not a sibling; for each `should_not_trigger` prompt, confirm the named `route_to` sibling is the better home and that this skill's boundary text would defer to it. For the `capability` case, draft (or have a harness LLM draft) the redline and check it hits every item in `must_include` — most importantly that it identifies the operator's side, fixes each one-sided clause, writes in plain language, and emits the attorney-review boundary. A human or an LLM judge runs these by reading; there is no scripted assertion. The separate `scripts/verify.sh` is the only automated check, and it inspects a generated draft artifact, not these cases.
