# Evals for testing-go

These cases are prompts to sanity-check routing and capability coverage, not an automated test harness. To exercise routing, feed each `should_trigger` and `should_not_trigger` prompt to the skill router and confirm that `testing-go` is selected for the former and the named sibling (`go`, `testing-py`, `testing-web`, `e2e-testing`, `review`) for the latter. For the `capability` entry, give the scenario to the agent with this skill loaded and check the generated Go test code against the `must_include` rubric by hand — every bullet should be visibly satisfied (table-driven subtests, synctest/fake clock with no real sleep, correct parallel handling, a fake or httptest double, `-race` plus a coverage command, and a `b.Loop()` benchmark). No CI integration is assumed.
