kotlin-testing

Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced testing skill with executable examples and clear TDD validation loops, but it is a monolithic ~800-line document that repeats some commands and would benefit from splitting detailed reference material into separate files.

Suggestions

Move the matcher catalog, full spec-style reference, and CI/CD YAML into separate files under references/ (e.g. MATCHERS.md, SPEC-STYLES.md, CI.md) and link to them from a concise overview.

Deduplicate the Kover/gradle commands so each appears once; reference the single source from the Quick Reference section.

Tighten the Quick Reference to genuine pointers and trim repeated inline examples to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The prose is lean and avoids explaining basics Claude knows, but the ~800-line body repeats commands (e.g. `koverHtmlReport` in three places) and inlines extensive reference material that could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready Kotlin code and concrete `./gradlew` commands for every pattern — specs, mocking, coroutines, property tests, Kover, Ktor, and CI.	3 / 3
Workflow Clarity	The TDD workflow is explicitly sequenced (RED-GREEN-REFACTOR) with validation checkpoints — "Run tests - verify FAIL" and "Run tests - verify PASS" — and the How-It-Works steps include verifying expected failure before implementing.	3 / 3
Progressive Disclosure	Well-organized into sections, but all detailed reference material (every spec style, full matcher catalog, CI YAML) is inline in SKILL.md with no bundle files; content that should be split into separate reference files is monolithic.	2 / 3
	Total	10 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-targeted description with strong trigger terms and clear distinctiveness, weakened only by the absence of an explicit "Use when..." clause that would tell Claude precisely when to invoke it. It uses correct third-person voice throughout.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or adding tests to Kotlin projects, configuring Kotest/MockK, or setting up Kover coverage."

Lead with the verb-action framing ("Write and configure Kotlin tests...") to match the specificity anchor's action-oriented style.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — "Kotest, MockK, coroutine testing, property-based testing, and Kover coverage" — naming distinct tools and testing sub-domains rather than vague abstractions.	3 / 3
Completeness	Clearly answers what the skill does, but lacks an explicit "Use when..." trigger clause; per the rubric, a missing explicit trigger guidance caps completeness at 2.	2 / 3
Trigger Term Quality	Uses the exact natural terms a user would say when needing this skill — "Kotlin testing", "Kotest", "MockK", "coroutine testing", "property-based testing", "Kover coverage", and "TDD".	3 / 3
Distinctiveness Conflict Risk	The Kotlin-testing niche with named frameworks (Kotest, MockK, Kover) is clearly distinguishable and unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (825 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 4130457

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.