CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-missing-unit-test

Add a new unit test for a class that currently lacks one or add a new test case to an existing test file, verifying improvement with Kover.

Quality

78%

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 ./.agents/skills/add-missing-unit-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-structured workflow with concrete Gradle/Kover commands, explicit baseline and verification steps, and clear reporting requirements. The only meaningful gaps are the duplicated objective text and the absence of an explicit failure-recovery loop in the verify phase.

Suggestions

Remove the Objective section (or the opening paragraph) since they duplicate each other verbatim.

Add an explicit feedback loop in the Verify step, e.g. "If the new test fails, fix the test or the code and re-run before proceeding; only confirm coverage improvement when all tests pass."

DimensionReasoningScore

Conciseness

The body is command-first and efficient with no concept explanations, but the Objective section repeats the opening paragraph verbatim ("Add a new unit test for a class that currently lacks one..."), which could be trimmed.

4 / 5

Actionability

Provides concrete executable commands ("./gradlew testClasses", "./gradlew verifyPlugin", "./gradlew koverHtmlReport"), a concrete naming convention ("[ClassName]Test"), and a commit-message template, with only minor gaps such as no example test snippet.

4 / 5

Workflow Clarity

The five phases are clearly sequenced with explicit baseline and verification checkpoints (compile, run tests, verifyPlugin, re-run Kover), but there is no explicit feedback loop telling Claude what to do when a test fails or coverage does not improve.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references (none exist in the bundle); its well-organized headed sections fully satisfy progressive disclosure for a skill of this size.

5 / 5

Total

17

/

20

Passed

Description

66%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 specific, action-oriented description in third person that clearly conveys the skill's purpose and tooling. Its main weakness is the missing explicit "Use when..." trigger clause, which limits both completeness and natural trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to add unit tests, improve test coverage, or mentions Kover or untested classes."

Include natural synonyms users would say — "test coverage", "code coverage", "write tests", "JUnit" — alongside "unit test" and "Kover".

State the measurable outcome explicitly ("improve line coverage") so the improvement claim is concrete rather than implied by the Kover mention.

DimensionReasoningScore

Specificity

Lists several concrete third-person actions ("Add a new unit test for a class that currently lacks one", "add a new test case to an existing test file", "verifying improvement with Kover") with only minor gaps such as not mentioning coverage reporting explicitly.

4 / 5

Completeness

The description clearly answers "what" (add unit tests and verify with Kover) but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like "unit test", "test case", "test file", and "Kover" are present, but common user phrasings such as "test coverage", "code coverage", "write tests", or "JUnit" are missing.

4 / 5

Distinctiveness Conflict Risk

The Kover/Kotlin-Gradle framing carves out a mostly distinct niche with only minor overlap risk against generic test-writing skills; it is not fully distinct since general "add tests" requests could route here.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

flutter/flutter-intellij

Path

.agents/skills/add-missing-unit-test/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.