CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kotlin-testing

Patrones de pruebas Kotlin con Kotest, MockK, pruebas de coroutines, pruebas basadas en propiedades y cobertura con Kover. Sigue la metodología TDD con prácticas idiomáticas de Kotlin.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/es/skills/kotlin-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 body is highly actionable with comprehensive executable examples and a clear TDD workflow, but it is a long monolithic file with no progressive disclosure to separate reference files.

Suggestions

Split large reference material (Matchers, Generadores, Cobertura Kover config, CI/CD) into files under references/ and link to them from a lean SKILL.md overview.

Trim the closing 'Recuerda' paragraph and any redundant inline tables to reduce per-invocation token cost.

Tighten the top-level 'Cómo Funciona' steps to mirror the explicit validate-fix-retry checkpoints already shown in the TDD example.

DimensionReasoningScore

Conciseness

Mostly efficient with code-first sections and little explanation of concepts Claude already knows, but at ~825 lines the monolith loads a large token budget every invocation and could be tightened (e.g. the closing 'Recuerda' line and some inline reference tables).

3 / 5

Actionability

Fully executable, copy-paste-ready Kotlin examples across specs, MockK, coroutines, property/data-driven tests, lifecycle, Kover, and Ktor, plus concrete gradle commands — covering the common cases.

5 / 5

Workflow Clarity

The 'Cómo Funciona' steps and RED-GREEN-REFACTOR cycle give a clear sequence with explicit validation checkpoints (verify ROJO failure, verify VERDE pass, verify 80%+ coverage), though the top-level steps are somewhat high-level compared to the fully checkpointed TDD example.

4 / 5

Progressive Disclosure

Good in-document section structure with a quick-reference anchor index, but no bundle files exist and all detailed reference material (matchers, generators, coverage config, CI/CD) is inlined in one file rather than split into one-level-deep references.

3 / 5

Total

15

/

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 clearly communicates a distinct Kotlin-testing niche with strong trigger keywords, but it omits any explicit 'when to use' guidance, leaving the activation trigger implicit.

Suggestions

Add a 'Use when...' clause, e.g. 'Úsalo cuando escribas o agregues pruebas a código Kotlin, mencione Kotest/MockK/Kover, o siga TDD en proyectos Kotlin.'

Lead with concrete verbs (e.g. 'Escribe specs, mockea dependencias, mide cobertura') to lift specificity from categories to actions.

Include common synonyms like 'unit tests' or 'pruebas unitarias' so the trigger matches a wider range of phrasings.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities — 'Kotest', 'MockK', 'pruebas de coroutines', 'pruebas basadas en propiedades', 'cobertura con Kover' — but these are testing categories/tool names rather than the multiple distinct concrete verbs of a 5.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('pruebas Kotlin', 'Kotest', 'MockK', 'coroutines', 'TDD', 'Kover') that users would say, though a few common variants ('unit tests', 'JUnit') are absent.

4 / 5

Distinctiveness Conflict Risk

Narrow niche anchored to named Kotlin test frameworks (Kotest, MockK, Kover) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

docs/es/skills/kotlin-testing/SKILL.md

Reviewed

Table of Contents

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.