Conciseness

The body is almost entirely lean code examples with no hand-holding prose — no 'what is pytest' explanation, no library comparisons. However, much of it restates standard pytest knowledge Claude already has (basic fixture syntax, patch/MagicMock, parametrize), and the trailing '## Keywords' section is filler duplicating the description, so not every token earns its place.

Actionability

Every example is complete, executable pytest code and every command in the Commands section is copy-paste ready. The examples cover the common cases: fixtures with teardown and scopes, conftest sharing, patch/mock with assertion, parametrize tables, markers, async tests, and run/filter commands.

Workflow Clarity

As a single-purpose pattern reference with unambiguous, well-separated sections, it avoids the validation cap and reads clearly. It falls short of 5 because there is no sequencing for the real-world task (configure markers in pytest.ini/pyproject, write tests, run with -x/-k/-m) and no guidance on when to choose each pattern.

Progressive Disclosure

No bundle files exist and the body has no external references; content is organized into clear, well-labeled sections appropriate to a patterns reference. It does not reach 5 because at ~175 lines everything is inline with no pointers to deeper material, and content such as the full markers/commands reference could arguably live in a separate file.

Specificity

The description names the domain ("Pytest testing patterns for Python") but contains no concrete actions — 'fixtures, mocking, markers' are topic nouns, not capabilities like 'write fixtures' or 'mock services'. This matches the anchor 'names the domain but actions are minimal or generic'; it falls short of anchor 3, which requires 1-2 concrete actions.

Completeness

An explicit "Trigger: When writing Python tests - fixtures, mocking, markers" clause clearly answers 'when', but the 'what' ("Pytest testing patterns for Python") is a domain label without concrete capabilities. Both are present and the 'when' is explicit, yet the vague 'what' keeps it below anchor 5.

Trigger Term Quality

"Pytest", "Python tests", "fixtures", "mocking", and "markers" are natural phrases users would say when needing this skill. Coverage is good but misses common variations such as 'unit tests', 'test suite', 'conftest', or 'parametrize', keeping it below anchor 5.

Distinctiveness Conflict Risk

Naming the specific tool 'pytest' gives it a clear niche, but the broad trigger "When writing Python tests" could overlap with a generic Python-testing or unittest skill. Mostly distinct with minor overlap risk — anchor 4 rather than 5's 'minimal conflict risk'.