Name: kotlin-testing
Rating: 61.6 (1 reviews)
Author: affaan-m

kotlin-testing

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

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/kotlin-testing/SKILL.md

The canonical home for this skill is kotlin-testing in affaan-m/ECC

Quality

Content

77%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.

The content is highly actionable with a clear, validated TDD workflow, but it is a long monolithic file that inlines reference material a separate file would carry, and it includes some basic TDD explanation Claude does not need.

Suggestions

Move the matcher catalog, full spec-style examples, and property-generator reference into a references/ file (e.g., references/kotest-reference.md) and link to it from a concise SKILL.md overview.

Trim the RED-GREEN-REFACTOR explainer box and the closing "Tests are documentation" prose, which restate concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is dominated by useful executable code, but the RED-GREEN-REFACTOR explainer box and the opening/closing prose restate TDD basics Claude already knows, so it could be tightened.	3 / 5
Actionability	It provides fully executable, copy-paste-ready Kotlin code and concrete gradle commands (./gradlew test, koverHtmlReport) covering spec styles, mocking, coroutines, property testing, and coverage.	5 / 5
Workflow Clarity	The 7-step "How It Works" and the TDD walkthrough give a clear sequence with explicit validation checkpoints (verify FAIL, verify PASS, confirm 80%+ coverage) and a built-in RED/GREEN/REFACTOR feedback loop.	5 / 5
Progressive Disclosure	Section headers and a Quick Reference with anchor links give reasonable structure, but no bundle files exist and large reference-style content (matchers, all spec styles, property generators) is fully inlined in one ~820-line file.	3 / 5
	Total	16 / 20 Passed

Description

70%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.

The description is specific and distinctive, naming concrete Kotlin testing tools and capabilities, but it omits any explicit "Use when" trigger guidance, which caps its completeness. Adding a trigger clause would lift the weakest dimension.

Suggestions

Append an explicit "Use when..." clause naming concrete triggers (e.g., "Use when writing or adding tests to Kotlin projects, setting up Kotest/MockK, or configuring Kover coverage").

Reframe tool names as actions (e.g., "Write Kotest specs, mock dependencies with MockK, test coroutines") to strengthen the specificity of capabilities.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ("coroutine testing", "property-based testing", "Kover coverage") alongside named tools, but leans on tool enumeration rather than fully spelled-out actions, leaving minor gaps.	4 / 5
Completeness	It clearly states what the skill does, but there is no explicit "Use when..." trigger clause; "when" is only weakly implied, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms a user would say are present ("Kotlin testing", "Kotest", "MockK", "TDD"), with good coverage; a few synonyms like "unit test" are absent so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	The named Kotlin-specific tooling (Kotest, MockK, Kover) carves a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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 (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
Path: .kiro/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.