# Evals — lead-gen

`cases.yaml` is run by the repo's skill-eval harness. The `should_trigger` and `should_not_trigger` prompts test routing: each prompt is matched against this skill's description+triggers, and the near-miss cases assert the router prefers the named sibling (`route_to`) instead of `lead-gen` — that is how we catch the skill grabbing work that belongs to `cold-outreach`, `sales-pipeline`, `market-research`, `data-scraper`, or `email-deliverability`. The `capability` case is graded (manually or by an LLM judge) against its `must_include` rubric: feed the scenario, then check the produced list actually carries a falsifiable ICP, summed fit/intent/engagement subscores, A/B/C tiers matching the bands, per-row provenance, a compliance note, and an explicit handoff. Run it with the harness from the repo root; there is no standalone runner in this folder.
