These cases are split into routing checks and a capability rubric, run through the repo's standard skill-eval harness. The should_trigger and should_not_trigger prompts validate the description's routing: each should_trigger prompt must select this skill (including the non-obvious hotspot/hidden-behavior and Spanish phrasings), and each should_not_trigger prompt must route to the named sibling (analyze, harness, decision-records, debug, init) instead — that is how we confirm the boundary lines hold. The capability block is graded by a model against the must_include rubric, not asserted by a script: given an unfamiliar Node/Express + Postgres repo, the run is judged on whether it produced a breadth-first map (stack, entry points, one traced flow, ownership, a hidden side effect, churn hotspots, run instructions) written to CODEBASE-MAP.md — and crucially did not read the repo line-by-line. Run the whole file with the harness; there is no separate setup.