# Evals — document-processing

`cases.yaml` is a routing-and-capability fixture, not an automated runner. To use it, take each prompt under `should_trigger` and confirm a router/agent picks `document-processing` for the stated `why`; take each `should_not_trigger` prompt and confirm it routes instead to the named `route_to` sibling (`structured-extraction`, `e-signature`, `spreadsheet-ops`, `rag`, `data-scraper`) — a miss here is a boundary leak, the most common failure for this skill. For `capability`, give the model the `scenario` with only the SKILL.md loaded and grade the response against every line in `must_include` (it must detect the missing text layer, choose a *local* OCR pipeline because the user said no cloud, hand the Markdown to structured-extraction rather than regexing fields, add an OCR spot-check, and use current libs not PyPDF2). If the repo has a top-level eval harness, point it at this file; otherwise read the cases by hand.
