CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

132-java-testing-integration-testing

Use when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client infrastructure from import signals, injecting service coordinates dynamically via System.setProperty(), creating WireMock JSON mapping files with bodyFileName, isolating stubs per test method, verifying HTTP interactions, or eliminating anti-patterns such as Mockito-mocked HTTP clients or globally registered WireMock stubs. This should trigger for requests such as Review Java code for integration tests; Apply best practices for integration tests in Java code; Write Java integration tests with real infrastructure boundaries; Improve Testcontainers integration tests for Java code; Review integration test setup and teardown in Java projects. Part of Plinth Toolkit

65

Quality

82%

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

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

Well-structured overview with proper progressive disclosure to a single real reference file and a compile-gated workflow. Main weakness is redundancy: the Constraints section duplicates the workflow's compile/verify steps, and the 'When to use' section duplicates the frontmatter triggers.

Suggestions

Remove the duplicate compile/verify instructions — state them once (either in Constraints or in Workflow steps 1 and 4, not both) to improve conciseness.

Drop the 'When to use this skill' section or replace it with a pointer, since the frontmatter description already carries the full trigger list verbatim.

Add a feedback loop for verification failure in the workflow (e.g., 'If `mvn clean verify` fails, fix and re-run until green before finishing') to lift workflow clarity to the top anchor.

DimensionReasoningScore

Conciseness

The compile-before/verify-after rules appear three times (Constraints bullets, Workflow steps 1 and 4) and the 'When to use this skill' section restates the frontmatter triggers — noticeable duplication that could be tightened, matching anchor 3 rather than the 'minor instances' of anchor 4.

3 / 5

Actionability

Concrete copy-paste commands ('Run `./mvnw compile` or `mvn compile`', 'Run `./mvnw clean verify`') and a verified reference path; step 3 ('Implement BaseIntegrationTest, WireMock mappings/stubs') is high-level but delegates detail to the reference — minor gaps, anchor 4.

4 / 5

Workflow Clarity

Clear 4-step sequence with an explicit pre-change validation gate ('stop immediately if compilation fails') and post-change full verification, but there is no fix-and-retry feedback loop for a failing `clean verify`, so it sits at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

A lean ~58-line overview whose detail lives in references/132-java-testing-integration-testing.md — a real, verified file one level deep (it points to sibling skills by @name, not nested files) and clearly signaled in both Workflow step 2 and the Reference section, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Description

83%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: comprehensive concrete capabilities plus explicit, natural trigger phrasings. It loses points for second-person voice and slightly incomplete synonym coverage, and its Testcontainers trigger could collide with a dedicated sibling skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('generating a BaseIntegrationTest.java with WireMock', 'creating WireMock JSON mapping files with bodyFileName', 'isolating stubs per test method') approaching anchor 5, but the second-person opening 'Use when you need to...' triggers the 1-point specificity penalty per the rubric guidelines.

4 / 5

Completeness

Explicitly answers both 'what' ('set up, review, or improve Java integration tests — including generating... verifying HTTP interactions') and 'when' ('This should trigger for requests such as...') with concrete trigger phrases, exactly matching anchor 5.

5 / 5

Trigger Term Quality

Five verbatim natural user requests ('Review Java code for integration tests', 'Improve Testcontainers integration tests for Java code', 'Review integration test setup and teardown') plus tool keywords give good coverage, but a few natural terms are missing (e.g., 'stub external services', 'mock server', 'IT tests'), so it does not reach the comprehensive synonym/extension coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear WireMock/Java-integration-testing niche with distinct triggers, but the 'Improve Testcontainers integration tests' trigger and 'Part of Plinth Toolkit' sibling naming create minor overlap risk with closely related testing skills (anchor 4 rather than 5).

4 / 5

Total

17

/

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

jabrena/plinth

Path

skills/132-java-testing-integration-testing/SKILL.md

Revision

86b41dc

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill