# Evals — cold-outreach

These cases are read by the catalog's routing harness (or by hand). There is no bundled runner. `should_trigger` asserts that the SKILL.md description + body are specific enough that the listed prompt would load `cold-outreach`; `should_not_trigger` asserts a near-miss prompt routes to the named real sibling instead (each `route_to` id must exist in the catalog); and `capability` is a rubric — feed the scenario to an agent with this skill loaded and grade the generated sequence against every `must_include` bullet (each is pass/fail). To sanity-check a *generated* draft against the structural rules, run `../scripts/verify.sh path/to/draft.md` from this directory — it is read-only and flags missing opt-out, multiple CTAs, over-ceiling word count, and spam/AI-tell phrases.
