# Evals — linkedin-outreach

These cases are read by the catalog's routing harness (or by hand); there is no bundled runner. `should_trigger` asserts the SKILL.md description + body are specific enough that the listed prompt loads `linkedin-outreach`. `should_not_trigger` asserts a near-miss prompt routes to the named real sibling instead (each `route_to` id — `cold-outreach`, `lead-gen`, `sales-pipeline`, `linkedin-content`, `linkedin-strategy` — exists in the catalog). `capability` is a rubric: feed the scenario to an agent with this skill loaded and grade the generated motion against every `must_include` bullet (each is pass/fail). To sanity-check a *generated ledger* against the schema and placeholder banlist, run `../scripts/verify.sh path/to/touches.csv` from this directory — it is read-only, defaults to `02-DOCS/linkedin-outreach/touches.csv`, and exits 0 cleanly when no ledger exists yet.
