CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quality-test-pilot

Writes high-quality unit tests for Kotlin Android codebases to increase meaningful test coverage. Use this skill to add tests for untested edge cases, ViewModel states, exception handling blocks, or UseCases using MockK, runTest, and the Given-When-Then pattern.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured, actionable skill with an explicit workflow, validation checkpoints, and clear guardrails (ask-first/never-do lists). Its main weaknesses are motivational Philosophy padding and the absence of a concrete Kotlin test code example illustrating the MockK/runTest pattern it mandates.

DimensionReasoningScore

Conciseness

The constraints and instructions are lean and assume Claude's competence, but the four 'Philosophy' bullets ('Untested code is broken code', 'A failing test is a feature, not a bug') are motivational padding that could be trimmed, fitting the minor-over-explanation anchor.

4 / 5

Actionability

Concrete executable commands ('./gradlew ktfmtFormat', './gradlew testDebugUnitTest --tests "YourTestClass"'), a test-naming convention example, and a PR title format are given, but no actual Kotlin test snippet shows the mandated runTest/MockK pattern — a minor gap.

4 / 5

Workflow Clarity

A clear five-step sequence (SCAN, SELECT & PROPOSE, BUILD, VERIFY, PRESENT) with an explicit user-approval checkpoint and a real validation feedback loop: format, run the specific test class, and verify the test fails when production behavior is temporarily inverted (mutation-check) then passes when restored.

5 / 5

Progressive Disclosure

The ~46-line body is well-organized into Goal/Constraints/Instructions/Examples with no external reference files needed; the only referenced file (the journal) is a clearly signaled runtime path one level deep, which satisfies the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

92%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 strong description: concrete capabilities, explicit 'Use this skill' trigger guidance, and a well-delineated Kotlin Android unit-testing niche. The only gap is a handful of natural trigger synonyms (JUnit, coroutine testing).

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'add tests for untested edge cases, ViewModel states, exception handling blocks, or UseCases' — and names the specific tooling ('MockK, runTest, and the Given-When-Then pattern'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

It explicitly answers both what ('Writes high-quality unit tests for Kotlin Android codebases to increase meaningful test coverage') and when ('Use this skill to add tests for untested edge cases, ViewModel states, exception handling blocks, or UseCases'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keywords ('unit tests', 'test coverage', 'edge cases', 'ViewModel', 'UseCases', 'MockK'), but a few common variations users would actually say are missing (e.g. 'JUnit', 'coroutine tests', 'increase coverage').

4 / 5

Distinctiveness Conflict Risk

Clear niche — Kotlin Android unit testing with MockK/runTest/Given-When-Then — with distinct triggers that are unlikely to fire for generic testing, code-review, or UI-test skills.

5 / 5

Total

19

/

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

nekomangaorg/Neko

Path

.agents/skills/test pilot/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.