# Evals: wordpress

`cases.yaml` checks routing and capability for the wordpress skill. `should_trigger` lists prompts (including a non-obvious HPOS migration and Spanish/Catalan phrasings) that must select this skill; `should_not_trigger` lists adjacent prompts that must route to a named sibling (php, laravel, shopify, secure-coding, nextjs). The `capability` block is a scaffolding scenario with a `must_include` rubric. There is no automated runner here — evaluate by hand or with your harness: read each `should_trigger`/`should_not_trigger` prompt, confirm the skill description would (or would not) match and that the route_to sibling is the better home, then run the capability scenario against the skill and check the produced plugin hits every rubric line. A case fails if the skill mis-routes or the output misses a `must_include` item.
