kotlin-testing

Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices. Use when writing Kotlin tests with Kotest or MockK, or testing coroutines and checking coverage.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

73%Weight 40%Scale 1-5

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

Highly actionable content with an excellent sequenced TDD workflow and executable examples, but it is monolithic: encyclopedic reference material lives inline in SKILL.md instead of being split into clearly signaled reference files, hurting both conciseness and progressive disclosure.

Suggestions

Move the detailed reference catalogs (Kotest spec styles, matchers, MockK, coroutine testing, property-based testing, Ktor) into separate files under references/ and keep SKILL.md as a concise overview with one-level-deep links, matching the 'Quick Reference' section's intent.

Trim the opening summary paragraph and the closing 'Tests are documentation' note, which restate information already conveyed by the examples.

Pull the bulk matcher catalog and CI/CD YAML into reference files so SKILL.md focuses on the TDD workflow and quick-start patterns.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with runnable examples, but the ~820-line body inlines large reference-style catalogs (full spec styles, matchers list, lifecycle/CI sections) and carries mild padding (the opening summary and 'Tests are documentation' closing restate what the examples already show).	3 / 5
Actionability	Provides fully executable, copy-paste-ready Kotlin code across all patterns plus concrete gradle commands ('./gradlew koverHtmlReport', './gradlew test --tests ...') covering the common cases.	5 / 5
Workflow Clarity	The TDD RED-GREEN-REFACTOR cycle is explicitly sequenced with validation checkpoints (verify FAIL, verify PASS, refactor-then-retest) and a coverage verification step, including a feedback loop for failures.	5 / 5
Progressive Disclosure	No bundle/reference files exist; the entire detailed API-level content (spec styles, matchers, mocking, coroutines, Kover, Ktor, CI) is inlined into one monolithic SKILL.md with only internal anchor links rather than being split into one-level-deep reference files.	2 / 5
	Total	15 / 20 Passed

Description

92%Weight 40%Scale 1-5

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 strong, specific description that clearly states capabilities and provides an explicit 'Use when' trigger clause with concrete terms. Only minor room for improvement via synonyms and file extensions in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete capabilities — 'Kotest, MockK, coroutine testing, property-based testing, and Kover coverage' — giving comprehensive coverage of distinct actions.	5 / 5
Completeness	Explicitly answers both 'what' (the listed testing capabilities and 'Follows TDD methodology') and 'when' via a concrete 'Use when writing Kotlin tests with Kotest or MockK, or testing coroutines and checking coverage' trigger clause.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('Kotlin tests', 'Kotest', 'MockK', 'coroutines', 'coverage') but is missing common synonyms and file/extension variants that would round out coverage.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Kotlin testing with named libraries) with distinct, library-specific triggers that minimize overlap with other skills.	5 / 5
	Total	19 / 20 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 (826 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/kotlin-testing/SKILL.md
Commit: d8409a4

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.