CtrlK
BlogDocsLog inGet started
Tessl Logo

141-java-refactoring-with-modern-features

Use when you need to refactor Java code to adopt modern Java features (Java 8+) — including migrating anonymous classes to lambdas, replacing Iterator loops with Stream API, adopting Optional for null safety, switching from legacy Date/Calendar to java.time, using collection factory methods, applying text blocks, var inference, or leveraging Java 25 features like flexible constructor bodies and module import declarations. This should trigger for requests such as Review Java code for modern Java development; Apply best practices for modern Java development in Java code; Modernize Java code with records pattern matching or switch expressions; Replace legacy idioms with modern Java features; Adopt Java 8+ language features safely. Part of Plinth Toolkit

80

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The SKILL.md body is concise, actionable, and well-structured, with a clear compile-before/verify-after workflow and clean progressive disclosure to a single existing reference. It avoids explaining concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, stating only coverage, constraints, workflow, and a reference pointer with no padding about what Java is or how libraries work; every section earns its place.

3 / 3

Actionability

Provides concrete executable commands ("./mvnw compile", "mvn clean verify"), an explicit reference path to read ("references/141-java-refactoring-with-modern-features.md"), and incremental refactor guidance; detailed good/bad examples are appropriately delegated to the reference.

3 / 3

Workflow Clarity

The 4-step workflow has an explicit compile-before checkpoint with "stop immediately if compilation fails" and a verify-after step, plus a feedback loop (fix and re-verify), matching the anchor for a clear sequence with explicit validation.

3 / 3

Progressive Disclosure

The body is a clear overview with a single one-level-deep reference that exists on disk (references/141-java-refactoring-with-modern-features.md), signaled via a "Reference" link and a workflow step pointing to it, with no nested references.

3 / 3

Total

12

/

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.

The description is specific, trigger-rich, and clearly bounded to Java modernization, explicitly answering both what it does and when to use it. It avoids vague fluff and uses third-person voice throughout.

DimensionReasoningScore

Specificity

Lists many concrete actions such as "migrating anonymous classes to lambdas", "replacing Iterator loops with Stream API", "adopting Optional", and "switching from legacy Date/Calendar to java.time", matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers what (refactor Java code to adopt modern Java features, with a enumerated list) and when via a "Use when you need to..." clause plus concrete trigger requests, satisfying the anchor for clearly answering both what AND when.

3 / 3

Trigger Term Quality

Includes natural user phrasings like "Review Java code for modern Java development", "Modernize Java code with records pattern matching or switch expressions", and "Replace legacy idioms with modern Java features", giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The Java-specific modernization niche with version-scoped feature triggers (Java 8+ through Java 25) is distinct and unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/plinth
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.