CtrlK
BlogDocsLog inGet started
Tessl Logo

123-java-design-patterns

Use when you need to select, review, or implement Java design and integration patterns — including classic Java design patterns, REST API patterns, Kafka and event-driven patterns, database and persistence patterns, and cross-cutting integration patterns. This should trigger for requests such as Apply Java design patterns; Review REST API patterns; Design Kafka event-driven patterns; Improve database persistence patterns; Add resilient integration patterns. Part of Plinth Toolkit

72

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

87%

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

A well-architected router skill: concise, actionable process guidance with correctly structured one-level-deep references. The only notable gap is the absence of an explicit error-recovery feedback loop in the build/validate workflow.

Suggestions

Add an explicit validation feedback loop, e.g. in step 5 or the BUILD SAFETY constraint: "If `mvn clean verify` fails, fix the reported issues and re-run until it passes before considering the change complete."

Surface the build-failure retry as a numbered checkpoint in the Workflow so the validate → fix → re-validate cycle is as explicit as the selection and implementation steps.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no concept-padding (it never explains what design patterns are); every section — coverage, scope, constraints, workflow, references — earns its place.

3 / 3

Actionability

It gives concrete, executable guidance: exact build commands ("./mvnw compile", "mvn clean verify"), specific reference file paths to read, and concrete decision heuristics (PROBLEM FIRST, NO PATTERN SHOPPING, TRADE-OFFS REQUIRED); as an instruction-only skill, absence of code is not penalized.

3 / 3

Workflow Clarity

The five-step workflow is clearly sequenced and includes validation (step 5 and the BUILD SAFETY constraint with before/after commands), but it lacks an explicit build-failure feedback loop (validate → fix → re-run), which the rubric notes cap at 2 for skills touching database and refactoring operations.

2 / 3

Progressive Disclosure

The SKILL.md is a clean overview that points to five real, one-level-deep reference files (all verified to exist), signaled both in Workflow step 2 and in a dedicated Reference section with markdown links.

3 / 3

Total

11

/

12

Passed

Description

90%

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-structured description that clearly states capabilities and provides explicit, natural trigger phrases. Its main weakness is the second-person voice, which both violates the rubric's voice requirement and reduces the specificity score.

Suggestions

Rewrite in third person to match the rubric voice requirement, e.g. "Selects, reviews, and implements Java design and integration patterns. Use when selecting, reviewing, or implementing Java design patterns, REST API patterns, ..." — drop "Use when you need to" and "This should trigger for".

Make the leading actions more concrete (e.g. "selects appropriate patterns, reviews code for missing patterns, implements creational/structural/behavioral patterns") so the capability verbs are as tangible as the named domains.

DimensionReasoningScore

Specificity

The description lists concrete actions ("select, review, or implement") across five named pattern domains, which would anchor at 3, but it uses second-person voice ("Use when you need to...", "This should trigger for...") which the rubric penalizes by reducing specificity by one.

2 / 3

Completeness

It clearly answers both what ("select, review, or implement Java design and integration patterns" plus enumerated domains) and when ("Use when you need to...", "This should trigger for requests such as...") with explicit trigger guidance.

3 / 3

Trigger Term Quality

It provides explicit natural triggers a user would say ("Apply Java design patterns; Review REST API patterns; Design Kafka event-driven patterns; Improve database persistence patterns; Add resilient integration patterns"), giving good coverage of real request phrasings.

3 / 3

Distinctiveness Conflict Risk

The Java design-and-integration-patterns niche is well-scoped with distinct, domain-specific triggers, making conflict with unrelated skills unlikely.

3 / 3

Total

11

/

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.