# Evals — community

`cases.yaml` is a judging harness, not an executable test suite. Run it with a human or an LLM judge. The `should_trigger` and `should_not_trigger` cases check routing discipline: each `should_trigger` prompt should pull in this skill (including the non-obvious "graveyard" and Catalan phrasings), and each `should_not_trigger` prompt should route to the named sibling (`retention`, `newsletter`, `social-publisher`, `webinar`) instead of here. The `capability` case is run end-to-end against a real session: give the agent the scenario and score the response against the `must_include` rubric — every bullet must be satisfied (purpose+north-star gate, platform rationale, onboarding path, 3-layer moderation, a ritual with cadence, the metrics, and the emitted artifact validated by `scripts/verify.sh`). Structural defects in the emitted `moderation-config` are caught mechanically by `scripts/verify.sh`; the rubric covers the process rigor that no script can check.
