# Evals — medium-publishing

These cases check routing and capability for the `medium-publishing` skill. Run them through the skill-eval harness: each `should_trigger` prompt should fire this skill; each `should_not_trigger` prompt should route to the named sibling instead (`medium-writing` for the article's craft, `medium-strategy` for growth/cadence, `social-publisher` for multi-platform scheduling, `seo-geo` for site-wide SEO). The `capability` case is rubric-graded — feed the scenario to the skill and check the response covers every `must_include` item (closed API, import-tool-first, auto canonical + backdate, manual canonical fallback, 5-tag limit, formatting gotchas, and no false promise of API automation). There is no `verify.sh`: this is a process/operational skill whose output is an article published on a third-party platform via UI steps, so rigor lives in this capability rubric and the post-publish checklist in SKILL.md.
