testing-java

Java testing with JUnit 5 and Mockito: test lifecycle, mocking, and integration test patterns

1.14x

Quality

63%

Does it follow best practices?

Impact

92%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/testing-java/SKILL.md

Quality

Discovery

40%

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 identifies a clear technical niche (Java testing with JUnit 5 and Mockito) which provides good distinctiveness, but it reads more like a topic label than an actionable skill description. It lacks concrete actions (what Claude will do) and completely omits trigger guidance (when to use it), significantly reducing its effectiveness for skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about writing Java tests, creating mocks, setting up test fixtures, or working with JUnit 5 or Mockito.'

List specific concrete actions the skill enables, e.g., 'Writes unit tests using JUnit 5 annotations, creates mock objects and stubs with Mockito, configures test lifecycle hooks, and sets up integration test patterns.'

Include additional natural trigger terms users might say, such as 'unit test', '@Test', '@Mock', 'assertions', 'test coverage', 'verify', 'stub'.

Dimension	Reasoning	Score
Specificity	Names the domain (Java testing) and some specific areas (test lifecycle, mocking, integration test patterns), but doesn't list concrete actions like 'write unit tests', 'create mock objects', 'configure test fixtures'.	2 / 3
Completeness	Describes what the skill covers (Java testing topics) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only partially specified, warranting a 1.	1 / 3
Trigger Term Quality	Includes good keywords like 'JUnit 5', 'Mockito', 'mocking', 'integration test', but misses common user terms like 'unit test', '@Test', '@Mock', 'test class', 'assertions', 'verify', or 'stub'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'JUnit 5' and 'Mockito' creates a clear, distinct niche that is unlikely to conflict with other skills. These are specific frameworks that clearly delineate this skill's domain.	3 / 3
	Total	8 / 12 Passed

Implementation

87%

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

This is a strong, concise skill that provides actionable Java testing guidance with executable code examples and clear conventions. The content is well-organized and token-efficient, covering JUnit 5, Mockito, and integration testing patterns without unnecessary explanation. The only weakness is the lack of an explicit workflow sequence with validation checkpoints, particularly around the coverage enforcement step.

Suggestions

Add a brief workflow sequence for the test-write-validate cycle, e.g., '1. Write test → 2. Run `mvn test` → 3. Check coverage with `gradle jacocoTestReport` → 4. If below 80%, add tests → 5. Enforce with `jacocoTestCoverageVerification`'.

Dimension	Reasoning	Score
Conciseness	Every section is lean and assumes Claude's competence with Java, JUnit, and Mockito. No unnecessary explanations of what testing is or how libraries work—just the patterns and rules.	3 / 3
Actionability	Provides fully executable code examples for test structure, parameterized tests, and specific commands for running tests and generating coverage reports. The mocking rules and integration test guidance are concrete and specific.	3 / 3
Workflow Clarity	The skill covers individual testing concerns well but doesn't present a clear sequenced workflow for writing and validating tests. There are no explicit validation checkpoints (e.g., run tests → check coverage → fix failures → re-run), which would be valuable for the coverage enforcement step.	2 / 3
Progressive Disclosure	For a skill under 50 lines with no need for external references, the content is well-organized into clearly labeled sections that progress logically from framework basics to structure, parameterized tests, mocking rules, integration tests, and coverage.	3 / 3
	Total	11 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ucdavis/ai-skills-registry
Commit: c0b2e4b

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