CtrlK
BlogDocsLog inGet started
Tessl Logo

121-java-object-oriented-design

Use when reviewing, improving, or refactoring Java object-oriented design, including applying SOLID, DRY, or YAGNI; improving classes and interfaces; correcting encapsulation, inheritance, or polymorphism; resolving God Class, Feature Envy, or Data Clumps; and improving object creation, methods, or exception contracts. Triggers include review Java OOD, refactor Java OOD, improve Java OOD, fix OOP misuse, and identify Java code smells. Part of Plinth Toolkit

67

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/121-java-object-oriented-design/SKILL.md
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 content with strong progressive disclosure and a clear, validated workflow. The main weakness is structural redundancy between the coverage list, workflow, and constraints that inflates the token budget without adding guidance.

Suggestions

Collapse the 'What is covered in this Skill?' list and Workflow step 2's concern-classification list into a single authoritative taxonomy to remove duplication.

Trim redundant Constraints (e.g., merge INCREMENTAL SAFETY, DEPENDENCY SAFETY, and PRESERVE BEHAVIOR) since the workflow already encodes compile-after-each-refactoring and behavior preservation.

Add a brief fix-and-revalidate feedback loop to Workflow step 1 so a compilation failure leads to 'fix and recompile' rather than only 'stop'.

DimensionReasoningScore

Conciseness

The body is mostly efficient and list-based, but the 'What is covered' bullets, Workflow step 2's concern list, and several Constraints (INCREMENTAL SAFETY, DEPENDENCY SAFETY, PRESERVE BEHAVIOR) restate the same ideas, so it could be tightened.

3 / 5

Actionability

Provides copy-paste-ready commands ('./mvnw compile', 'mvn clean verify') and concrete named refactorings (extract classes, introduce abstractions, move behavior, introduce value objects), with the only gap being that code examples live in references rather than inline.

4 / 5

Workflow Clarity

A clear 6-step sequence with explicit validation checkpoints (compile before, compile after each refactoring, clean verify after) and a blocking 'stop immediately on compilation failure' rule, though it stops short of a fix-and-revalidate feedback loop.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview pointing to 8 verified, one-level-deep reference files, signaled both by a dedicated '## Reference' section and an inline concern-to-reference mapping in Workflow step 3, making navigation easy.

5 / 5

Total

16

/

20

Passed

Description

88%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, specific description that clearly states capabilities and trigger conditions with concrete keywords. Minor overlap with adjacent skills and slightly formulaic trigger phrasing keep it just below perfect.

Suggestions

Soften the overlap with skill 126 by scoping 'exception contracts' to 'exception contracts as part of a broader OOD review' in the description itself.

Make trigger phrases more natural, e.g. 'review my Java design', 'refactor this Java class', alongside the existing OOD/OOP terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the domain — 'applying SOLID, DRY, or YAGNI', 'correcting encapsulation, inheritance, or polymorphism', 'resolving God Class, Feature Envy, or Data Clumps', 'improving object creation, methods, or exception contracts' — giving comprehensive coverage rather than just a few.

5 / 5

Completeness

Explicitly answers both what (reviewing/improving/refactoring Java OOD with named actions) and when ('Use when reviewing, improving, or refactoring...' plus a dedicated 'Triggers include' clause), matching the anchor for concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicit trigger phrases ('review Java OOD, refactor Java OOD, improve Java OOD, fix OOP misuse, and identify Java code smells') give good keyword coverage with synonyms (OOD, OOP, code smells), though the phrasings are somewhat formulaic and a few natural variations are missing.

4 / 5

Distinctiveness Conflict Risk

'Java object-oriented design' is a clear niche with distinct triggers and minimal conflict risk, but the description's mention of 'exception contracts' creates minor overlap with the adjacent exception-handling skill (126).

4 / 5

Total

18

/

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.

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.