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

75

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

85%

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

A well-structured orchestration skill with a clear, validated workflow and excellent progressive disclosure. The main weakness is redundancy — the concern taxonomy is restated multiple times — which could be tightened for token efficiency.

Suggestions

Consolidate the OOD concern taxonomy: it appears three times ('What is covered in this Skill?', the 'Assess and classify' step, and the 'Map to references' step). Merge the overview list into the classification step to remove redundancy.

Drop the standalone 'When to use this skill' list, since the frontmatter description already encodes the same triggers and the list duplicates that information.

Tighten or remove the 'What is covered in this Skill?' bullet list, as the Constraints and Workflow sections already enumerate the same concern categories.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence (no basic-concept explanations), but the OOD concern taxonomy is repeated three times — 'What is covered', 'Assess/classify concerns', and 'Map to references' — and could be consolidated.

2 / 3

Actionability

Provides concrete, executable guidance: copy-paste-ready build commands ('./mvnw compile', 'mvn clean verify'), explicit reference file paths, and specific refactoring techniques, with detail appropriately delegated to references.

3 / 3

Workflow Clarity

The six-step workflow is clearly sequenced with explicit validation gates — compile-before (blocking on failure), incremental compile after each refactoring, and final 'mvn clean verify' — plus edge-case recovery (ask on ambiguity, report missing inputs).

3 / 3

Progressive Disclosure

Clear overview with one-level-deep references; all 8 referenced files exist in references/ and are well-signaled via both a Reference link list and a concern-to-file mapping in the workflow.

3 / 3

Total

11

/

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-crafted description that explicitly states concrete capabilities, provides natural trigger terms, and clearly answers both what and when. It is well-scoped to the Java OOD niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'reviewing, improving, or refactoring Java object-oriented design', 'applying SOLID, DRY, or YAGNI', 'resolving God Class, Feature Envy, or Data Clumps' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both what (review/improve/refactor Java OOD across named concern areas) and when ('Use when...' plus an explicit Triggers clause), matching the top anchor.

3 / 3

Trigger Term Quality

An explicit 'Triggers include review Java OOD, refactor Java OOD, improve Java OOD, fix OOP misuse, and identify Java code smells' clause gives good coverage of natural terms a user would say.

3 / 3

Distinctiveness Conflict Risk

Scoped to Java object-oriented design with Java-specific triggers, a clear niche unlikely to conflict with non-Java or non-OOD skills.

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.