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

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

100%

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

The content is a tight, well-structured workflow with concrete gradle commands, explicit validation and verification checkpoints, and a Kover-based coverage feedback loop. It is lean and fully actionable with no padding.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain what unit tests or Kover are, and every line is actionable instruction. Not the level below, which would include unnecessary explanation.	3 / 3
Actionability	Provides fully executable commands (./gradlew testClasses, ./gradlew verifyPlugin, ./gradlew koverHtmlReport), concrete paths (src/, testSrc/), and a copy-paste-ready commit message pattern.	3 / 3
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints and a feedback loop — baseline Kover coverage, then re-running tests and Kover after implementation to confirm improvement.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references, yet well-organized into clearly headed sections, which earns a 3 per the simple-skills guideline.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 clearly distinguishable, naming concrete actions and the Kover tool. Its main weakness is the absence of an explicit 'when to use' trigger clause and limited trigger-term variation.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when adding unit tests to improve Kotlin code coverage, or when the user asks to add or expand test coverage for a class').

Broaden trigger terms to include 'coverage', 'testing', and 'Kover coverage report' so it matches more natural user phrasings.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Add a new unit test for a class that currently lacks one', 'add a new test case to an existing test file', and 'verifying improvement with Kover' — rather than vague language.	3 / 3
Completeness	Clearly answers 'what' the skill does, but there is no 'Use when...' clause or equivalent explicit trigger, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Includes relevant natural terms like 'unit test', 'test case', and 'test file', but misses common variations a user might say such as 'coverage' or 'testing'.	2 / 3
Distinctiveness Conflict Risk	The niche is specific — adding unit tests with Kover coverage verification — and is unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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: 21aaf0b

Reviewed: 2 days 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.