Conciseness

The body is mostly lean and assumes Claude's Quarkus/JUnit knowledge, but the Constraints section states the same compile rule four ways ("MANDATORY: Run ./mvnw compile", "PREREQUISITE: Project must compile", "SAFETY: If compilation fails, stop immediately", "BLOCKING CONDITION: Compilation errors must be resolved by the user") and "When to use this skill" duplicates the description's trigger phrases verbatim. This is 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the noticeably padded anchor 2, since the redundancy is confined to two short sections.

Actionability

Gives concrete, executable commands ("Run `./mvnw compile` or `mvn compile`", "Run `./mvnw clean verify` or `mvn clean verify`") and names specific mechanisms (@InjectMock, @InjectSpy, QuarkusTestProfile, *Test/*IT conventions), deferring code patterns to the verified reference file. Not a 5 because the body itself contains no code examples for the common cases — everything pattern-level lives in the reference — and not a 3 because the commands given are directly runnable and the coverage list is concrete.

Workflow Clarity

The four-step workflow (read reference and assess context → gather scope → apply changes → run verification and report) is clearly sequenced, with an explicit compile-before gate ("MANDATORY: Run ./mvnw compile... before applying any change") and a verify-after step. Not a 5 because there is no feedback loop for verification failure — the workflow says "summarize what changed, what was verified" but not what to do if `clean verify` fails — leaving a minor validation gap at anchor 4.

Progressive Disclosure

The body is a concise overview with a single clearly-signaled, one-level-deep reference ([references/421-frameworks-quarkus-testing-unit-tests.md](references/421-frameworks-quarkus-testing-unit-tests.md)), which exists and holds the detailed rules and examples (verified on disk, 661 lines). The reference is surfaced three times (workflow step 1, "BEFORE APPLYING", and the Reference section) and no detail content that belongs in the reference is inlined. This matches the anchor for a clear overview with well-signaled, one-level-deep references.

Specificity

The description lists many concrete, specific actions — "pure tests with @ExtendWith(MockitoExtension.class)", "@QuarkusTest with @InjectMock for full CDI mock replacement", "@InjectSpy for partial CDI bean mocking", "QuarkusTestProfile for test-specific configuration overrides", "naming conventions (*Test → Surefire, *IT → Failsafe)" — which on content alone matches the comprehensive anchor 5. However, it opens in second person ("Use when you need to write fast unit tests..."), and the rubric explicitly penalizes second-person voice by reducing the specificity score by 1, bringing it to 4.

Completeness

Both halves are explicit: the 'what' is "write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class)..." and the 'when' appears twice — "Use when you need to write fast unit tests for Quarkus applications" and "This should trigger for requests such as: Add or improve unit tests in a Quarkus project...". This clearly and explicitly answers both what AND when with concrete trigger phrases, matching anchor 5.

Trigger Term Quality

It enumerates natural request phrasings users would actually say — "Add or improve unit tests in a Quarkus project", "Reduce slow @QuarkusTest usage with Mockito-first tests", "Convert repeated test methods to @ParameterizedTest", "Write fast pure unit tests for Quarkus services" — plus the technical keywords (Quarkus, Mockito, REST Assured, @InjectSpy) users would mention. This gives comprehensive coverage of natural terms including variations, matching anchor 5; no penalty applies to this dimension.

Distinctiveness Conflict Risk

The niche is narrow (Quarkus unit testing specifically) and it actively routes away neighboring skills: "For framework-agnostic Java use @131-java-testing-unit-testing" and, in the body, escalation to @422 integration tests. Quarkus-specific annotations make accidental triggering by generic Java testing requests unlikely — a clear niche with distinct triggers, matching anchor 5.