Conciseness

The body is lean and directive with no concept-explanation padding ('A mocked client, template, or transaction manager can't show timeouts, retries, redelivery, or publish-after-commit'). Not 5: 'Verified on Spring Boot 4.1.1 with Postgres 18, Kafka 4.1 and WireMock 3.13' embeds version-number provenance outside any old-patterns/deprecated section, a rot cost the rubric penalizes; not 3: nothing else could be trimmed.

Actionability

Concrete directives throughout ('Timeout tests use the production timeout value', 'test secured routes through @AutoConfigureMockMvc') plus a 13-entry table mapping each edge to a real template file. Not 5: the only inline code is a two-line contrast fragment, so the body itself is not copy-paste ready — full code is one hop away in assets/; not 3: the guidance is specific and executable at every step.

Workflow Clarity

A clear sequence is carried by section order (Rules → Before writing → Templates → Secured routes → Report) with explicit validation in rule 3 ('Break the guarded line and watch the test go red ... If a test fails on the current code, report it with the contract clause; never weaken the assertion') and a Report checklist. Not 5: the process order is implicit in the section arrangement rather than an explicit step sequence; not 3: validation checkpoints are present and unmissable.

Progressive Disclosure

All 13 asset references in the Templates table resolve one level deep with edge-keyed navigation, and the body stays a lean overview. Not 5: the two 'Before writing' references ('../code-reviewer/references/testing/traps.md', '../code-reviewer/references/testing/boot4-test-toolkit.md') point outside the skill's own bundle and do not resolve from this skill's directory; not 3: the core structure of lean body → indexed asset files is exemplary.

Specificity

Enumerates multiple concrete capabilities with comprehensive coverage: 'HTTP clients that call other services (WireMock: 4xx and 5xx responses, timeouts, retries)', 'Kafka or RabbitMQ listeners (redelivery, poison messages, dead-letter topics)', 'full-API tests against real databases with Testcontainers', plus what it supplies ('verified Boot 4.1 templates and the framework traps'). Not 4: every edge and its failure modes are named with no coverage gaps.

Completeness

'Use when writing or adding tests for Spring Boot code at a service's edges: ...' gives an explicit and detailed when; 'Supplies verified Boot 4.1 templates and the framework traps ...' states the what; exclusions ('Not for reviewing existing tests ... or Boot 3 to 4 test migration') add boundary clarity. Both what and when are explicit with concrete trigger phrases.

Trigger Term Quality

Includes natural terms users would say: 'writing or adding tests', 'Spring Boot', 'WireMock', 'Kafka or RabbitMQ', 'Testcontainers', 'Boot 4'. Not 5: common user phrasings such as 'integration test', 'controller/repository test', or 'test coverage' are absent; not 3: all major technologies and actions a user would name are present.

Distinctiveness Conflict Risk

Clear niche (edge/integration testing at a service's boundaries in Boot 4) with explicit fences against the nearest siblings: 'Not for reviewing existing tests (see code-reviewer) or Boot 3 to 4 test migration (see springboot-migration)'. Minimal conflict risk.