130-java-testing-strategies

Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code; Apply A-TRIP testing strategies in Java code; Apply CORRECT boundary condition verification in Java code. Part of Plinth Toolkit

Quality

80%

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

77%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 body with a clear validation-gated workflow and exemplary one-level-deep progressive disclosure to real reference files. Its one weakness is structural redundancy: routing rules and compile/verify commands appear in both the Constraints and Workflow sections.

Suggestions

Eliminate the duplication between the FOCUSED ROUTING Constraints bullets and Workflow step 2 — state the routing logic once (preferably in the workflow) and reference it from Constraints.

State the compile and verify commands once; the Workflow steps already carry them, so the MANDATORY/SAFETY/VERIFY bullets can reference the workflow instead of repeating the commands.

Add a brief inline example of one named deliverable (e.g., a 3-row RIGHT-BICEP gap matrix) so the 'apply strategy-driven improvements' step is fully copy-paste-ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids over-explaining concepts Claude knows, but the FOCUSED ROUTING rules and the compile/verify commands are duplicated between the Constraints section and Workflow steps 1–2 and 4, which could be tightened by stating each once.	3 / 5
Actionability	It gives concrete executable commands ('./mvnw compile or mvn compile', './mvnw clean verify'), explicit reference routing, and named deliverables ('RIGHT-BICEP gap matrix', 'A-TRIP quality finding list', 'CORRECT boundary checklist'), with the minor gap that no inline example illustrates what those deliverables look like.	4 / 5
Workflow Clarity	The four-step workflow has an explicit validation checkpoint with a feedback loop ('stop immediately if compilation fails') plus a post-change verify step, and the Constraints section functions as a checklist (MANDATORY/SAFETY/VERIFY/EDGE CASE), matching the anchor for clear sequence with explicit validation and error-recovery feedback.	5 / 5
Progressive Disclosure	SKILL.md is a concise overview that routes to three real, one-level-deep reference files (confirmed present in references/) via conditional triggers, and a final Reference section lists all three with markdown links, giving clear well-signaled navigation.	5 / 5
	Total	17 / 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 that explicitly states what it does and when to trigger, with concrete named testing methodologies and natural trigger phrases. Its main limitation is technique-level rather than operation-level action specificity and minor synonym coverage gaps.

Suggestions

Add natural synonyms users might say (e.g., 'flaky tests', 'test coverage gaps', 'boundary cases') to broaden trigger-term coverage toward a 5.

Make the actions slightly more concrete (e.g., 'produce a RIGHT-BICEP gap matrix', 'generate a CORRECT boundary checklist') to lift specificity from technique-level to operation-level.

Clarify how this skill differs from sibling Plinth Toolkit Java skills to reduce the implied overlap risk.

Dimension	Reasoning	Score
Specificity	The description names the Java-testing domain and three concrete technique-level actions — 'RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions' — but the actions are category-level rather than granular operations, leaving minor coverage gaps.	4 / 5
Completeness	It explicitly answers both 'what' (apply RIGHT-BICEP/A-TRIP/CORRECT testing strategies to Java code) and 'when' (an explicit 'Use when...' clause plus concrete trigger phrases), matching the anchor for clear and explicit what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	It embeds natural verbatim trigger phrases users would say ('Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code; Apply A-TRIP...; Apply CORRECT boundary condition verification'), giving good keyword coverage, though synonyms like 'flaky tests' or 'test coverage gaps' are absent.	4 / 5
Distinctiveness Conflict Risk	The Java-specific scope plus three named methodologies (RIGHT-BICEP, A-TRIP, CORRECT) form a clear niche with distinct triggers, but the 'Part of Plinth Toolkit' tag implies potential overlap with sibling Java skills, a minor conflict risk.	4 / 5
	Total	17 / 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: jabrena/plinth
Path: skills/130-java-testing-strategies/SKILL.md
Commit: 77b8825

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