Content is mostly actionable but padded with repeated 'Per [schemathesis-readme][readme]' attribution clauses (~6 occurrences) and a somewhat redundant Install/Running-via-CLI split, plus an overview quote that re-explains what Schemathesis is; it is not level 1 because the bulk is concrete flags/checks/code rather than concept explanation, and not level 3 because the attributions and minor redundancy could be trimmed.

Provides a copy-paste worked CLI example, executable pytest snippet ('@schema.parametrize()' / 'case.call_and_validate()'), a complete GitHub Actions workflow in the reference, and flag/check tables — matching the level-3 anchor for fully executable, copy-paste-ready guidance.

The 4-step 'How to use' sequence includes a validation checkpoint (reproduce any failure from the printed curl + Hypothesis seed), a CI gate as verification, and an Anti-patterns checklist serving as error-recovery feedback; matches the level-3 anchor with explicit checkpoints and a feedback loop.

SKILL.md is an overview that signals one-level-deep detail to references/ci-and-pytest-integration.md (verified to exist) for CI wiring and hooks, with no nested second-level references; content is appropriately split and easy to navigate, matching the level-3 anchor.

Lists multiple concrete actions — 'Generates property-based API tests', 'runs them via the schemathesis run CLI or as a pytest decorator', 'configures the canonical checks (status_code_conformance, response_schema_conformance, content_type_conformance, response_headers_conformance, not_a_server_error)', 'gates CI on schema-conformance failures plus 5xx detection' — matching the level-3 anchor; it is not level 2 because the actions are comprehensive and named, not just a domain plus partial actions.

Explicitly answers 'what' (generates/runs/configures/gates) and 'when' via the 'Use when the project ships an OpenAPI or GraphQL schema and the team wants schema-driven coverage' clause, matching the level-3 anchor; it is not level 2 because the trigger is explicit, not implied.

Includes natural terms a user would say for this need — 'OpenAPI 2/3.x or GraphQL schema', 'property-based API tests', '5xx', 'schema-driven coverage' — matching the level-3 anchor; it is not level 2 because common variations are covered rather than partial.

Carves a clear niche — property-based schema-driven fuzzing via Schemathesis — with distinct triggers unlikely to fire for example-based testing skills; uses consistent third-person voice ('Generates', 'runs', 'gates') per the voice guideline.