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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

The body is well-structured with clear progressive disclosure (one-level-deep references, all present) and a strong, validated workflow (compile-before, stop-on-failure, verify-after). Its main weaknesses are redundancy — routing rules are stated twice and the 'When to use' list echoes the description — and actionability that names deliverables abstractly while deferring the actual technique mechanics to the references.

Suggestions

Remove the duplicated routing: keep the request-to-reference mapping in Workflow step 2 and drop the redundant 'FOCUSED ROUTING' / 'BROAD REVIEW' bullets from the Constraints section, or vice versa.

Delete the 'When to use this skill' list since its trigger phrases already appear verbatim in the frontmatter description, or replace it with a pointer to the description to avoid maintaining two copies.

Add a one-line concrete spec for each named deliverable in step 3 (e.g., what columns a 'RIGHT-BICEP gap matrix' contains or what an 'A-TRIP quality finding' entry looks like) so the body's guidance is actionable before the reference is loaded.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concept-explanation padding, but routing is duplicated: the three 'FOCUSED ROUTING' and 'BROAD REVIEW' bullets in Constraints restate the routing detailed again in Workflow step 2, and the 'When to use this skill' list repeats the description's triggers, so not every token earns its place — falling short of the score-3 'lean' anchor.	2 / 3
Actionability	Provides concrete executable commands ('./mvnw compile', 'mvn clean verify') and specific reference routing, but the substantive test-writing guidance ('produce a RIGHT-BICEP gap matrix', 'an A-TRIP quality finding list', 'a CORRECT boundary checklist') is named only in the abstract and deferred to references, leaving body-level guidance incomplete per the score-2 'some concrete guidance but missing key details' anchor rather than fully copy-paste ready at score 3.	2 / 3
Workflow Clarity	Four clearly sequenced steps with explicit validation checkpoints — 'Run ./mvnw compile... stop immediately if compilation fails' (stop-on-fail feedback loop) and 'Run ./mvnw clean verify' after applying — matching the score-3 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor; validation is present so the destructive/batch cap at 2 does not apply.	3 / 3
Progressive Disclosure	A concise overview points one level deep to three real, verified reference files (all present in ./references/), signaled both by a linked Reference section and by request-based routing rules, with content appropriately split between body and references — matching the score-3 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	10 / 12 Passed

Description

100%

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, well-scoped description: it names three concrete techniques with their purposes, gives explicit 'Use when' triggers plus natural example request phrasings, and carves out a distinct Java-testing niche. It fully answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions' — each tied to a distinct purpose, matching the score-3 anchor rather than the narrower score-2 'some actions' anchor.	3 / 3
Completeness	Clearly answers both what ('apply testing strategies for Java code — RIGHT-BICEP..., A-TRIP..., or CORRECT...') and when via an explicit 'Use when you need to apply...' clause plus concrete trigger examples, satisfying the score-3 'what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	Embeds natural request phrasings a user would actually say — 'Review Java code for testing strategies', 'Apply RIGHT-BICEP testing strategies in Java code', 'Apply A-TRIP... Apply CORRECT...' — giving good coverage of natural terms rather than only jargon or generic phrasing.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Java unit-testing with three named mnemonics) with distinct triggers unlikely to fire for non-Java or non-testing skills; the 'Part of Plinth Toolkit' suffix does not erode that distinctiveness, keeping it at the score-3 anchor.	3 / 3
	Total	12 / 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: jabrena/plinth
Commit: aaee915

Reviewed: 1 day 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.