The body is code-forward and assumes Claude's competence — it never explains what a test framework, Gradle, or coroutines are. The 'How to use' list functions as a step-indexed table of contents rather than padding, and the worked example reinforces rather than restates. It is not 2 because there is no concept-explaining filler or unnecessary tutorial prose to tighten.

Provides fully executable, copy-paste-ready Kotlin: a build.gradle.kts dependency block with versions and useJUnitPlatform(), StringSpec/FunSpec/BehaviorSpec test examples, checkAll property cases, a coroutine test, withData rows, and the CI command './gradlew test jacocoTestReport'. It is not 2 because the code is concrete and complete rather than pseudocode or abstract description.

An explicit 8-step sequence (Steps 1-8) with a 'How to use' summary mapping sub-tasks to step numbers, plus a worked example and an anti-patterns table. Test authoring is not a destructive/batch operation, so the cap-at-2 validation rule does not apply; the run/coverage step (Step 8) and the worked-example verification serve as the validation checkpoint. It is not 2 because the sequence and checkpoints are explicit.

SKILL.md is a concise overview that offloads the matcher catalog and isolation-mode table to a single real, one-level-deep reference (references/matchers-and-isolation.md), signaled three times with clear link text. It is not 2 because references are well-signaled, shallow, and the split is appropriate rather than inline monolith or nested pointer chains.

Lists multiple concrete actions and capabilities ('Configures and runs Kotest', 'rich matcher library', 'built-in property-based testing', 'coroutines support', 'data-driven testing', 'isolation modes per-spec or per-test', 'integrates with Gradle JVM test task') rather than vague language. It is somewhat padded by enumerating all 9 spec styles, but the anchor for 3 is met and there is no abstract or buzzword-only language that would drop it to 2.

Explicitly answers both what it does (configures/runs Kotest with the listed features) and when to use it ('Use when working with Kotlin and wanting Kotlin-idiomatic DSL over JUnit 5's annotation-driven approach'). It is not 2 because the 'when' is stated explicitly with a trigger clause, not merely implied.

Covers natural terms a user would say when reaching for this skill ('Kotlin', 'Kotlin-native test framework', 'Kotest', 'property-based testing', 'coroutines', 'Gradle', 'JUnit 5') and provides an explicit 'Use when working with Kotlin and wanting Kotlin-idiomatic DSL' trigger. It does not fall to 2 because the relevant natural vocabulary is well covered, not just technical jargon.

Names a specific framework (Kotest) and explicitly differentiates from JUnit 5, jqwik, and assertj ('not a drop-in replacement for a standalone JVM assertion library; for assertion-only use paired with JUnit 5 / TestNG / Spock see assertj'), giving it a clear niche. It is not 2 because the named framework and the comparison sharpen it beyond a generic overlap-prone description.