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

72%

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

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.

The body is a well-structured, actionable workflow with concrete gradle commands and explicit verification via Kover, scoring high across the board. The main gaps are a duplicated objective line and the lack of an example test plus explicit failure-recovery loops.

Suggestions

Remove the redundant 'Objective' section or rewrite it so it does not duplicate the opening paragraph verbatim.

Add a short concrete example unit test (e.g. a `[ClassName]Test` skeleton with a mocked dependency and assertion) under 'Implement Test'.

Make the feedback loop explicit in 'Verify', e.g. 'If the new test fails, fix the test or code and re-run until it passes before re-running Kover.'

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with direct commands and bullets, but the 'Objective' section repeats the opening line verbatim ('to improve code coverage and reliability'), a minor instance of over-explanation that could be trimmed.	4 / 5
Actionability	Concrete, copy-paste-ready gradle commands and file paths are provided, but the core 'Implement Test' step gives only abstract guidance ('cover specific methods, edge cases, and branches') with no example test, leaving a minor gap.	4 / 5
Workflow Clarity	Five numbered steps with baseline and verify checkpoints give a clear sequence, but error-recovery feedback loops (e.g. 'if the test fails, fix and re-run') are implicit rather than explicit.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, and well-organized into clear sections with no need for external references, qualifying for the simple-skill exception at anchor 5.	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.

The description states concrete actions and natural trigger terms within a distinct Kover-based niche, but it omits any explicit 'Use when...' guidance, capping its completeness. Adding a trigger clause would substantially raise the score.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when a Kotlin/Gradle class lacks unit tests or coverage needs to be improved.'

Add natural synonyms such as 'code coverage' and 'test coverage' to broaden trigger-term match surface.

Tighten the two parallel 'add ... or add ...' phrasing into a single clause to improve conciseness without losing specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Add a new unit test', 'add a new test case to an existing test file', 'verifying improvement with Kover'), but is not fully comprehensive, fitting anchor 4 rather than 5.	4 / 5
Completeness	The 'what' is clear but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural keywords 'unit test', 'test case', 'test file', and 'Kover' are present, but synonyms like 'coverage' or 'code coverage' are missing, matching anchor 4.	4 / 5
Distinctiveness Conflict Risk	The Kover/Kotlin unit-testing niche is mostly distinct with only minor overlap risk against generic testing skills, fitting anchor 4 rather than a fully conflict-free 5.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: flutter/flutter-intellij
Path: .agents/skills/add-missing-unit-test/SKILL.md
Commit: 01f1775

Reviewed: about 13 hours 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.