Conciseness

The body is lean and assumes competence: commands are given directly with no library tutorials or filler. A couple of motivational/rationale sentences ("O contrato precisa aguentar o que o spec permite", and the one-line summary of what the source doc explains) could still be trimmed, matching the anchor for efficient content with minor over-explanation rather than the every-token-earns-its-place anchor.

Actionability

Two fully executable commands are given ("apm run schemathesis --param spec=<caminho-ou-url-do-openapi>" and "python3 -m schemathesis run <caminho-ou-url-do-openapi>") plus explicit guidance to point at the real spec and not fabricate one. It falls short of anchor 5 because there is no guidance on interpreting or remediating a failing run (e.g., which checks to inspect, fixing divergence and re-running).

Workflow Clarity

This is a simple single-purpose skill under 50 lines, and the single action is unambiguous: run Schemathesis against the platform API spec before closing the task, with explicit conditions for when it applies (route, schema, status, or OpenAPI changes) and when it does not block (Python-only changes). The Schemathesis run itself is the validation checkpoint, satisfying the simple-skill exception.

Progressive Disclosure

The skill is under 50 lines, needs no external reference files (no references/, scripts/, or assets/ bundles exist), and is organized into clear sections (source of truth, what it complements, how to run). The single pointer to docs/schemathesis.md is clearly signaled and one level deep, matching the anchor for a well-organized short skill.

Specificity

"Run Schemathesis against the spec before calling the task done" is a single concrete action in a named domain (HTTP API / OpenAPI), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several distinct actions, so it falls below anchor 4.

Completeness

Both parts are explicit: the "when" ("Use when the task changes an HTTP API, an OpenAPI spec, or routes covered by contract tests") is concrete and specific, and the "what" ("Run Schemathesis against the spec before calling the task done") states a clear action. It stops short of anchor 5 because the "what" does not say what the check actually does (validate the implementation against the contract), only that the tool should be run.

Trigger Term Quality

Natural phrases a user would say are present: "changes an HTTP API", "an OpenAPI spec", "routes covered by contract tests". Common synonyms and variations (e.g., "REST endpoint", "swagger", ".yaml spec") are missing, which keeps it at good-but-not-comprehensive coverage (anchor 4).

Distinctiveness Conflict Risk

The triggers are anchored to a specific niche (OpenAPI specs, contract-tested routes), making it mostly distinct with only minor overlap risk against general API-testing or code-review skills. It is not a fully clear niche with minimal conflict, as any HTTP API change could plausibly also invoke generic testing skills.