CtrlK
BlogDocsLog inGet started
Tessl Logo

145-java-refactoring-high-performance

Use when you need to refactor Java code for high performance — including memory/allocation reduction, CPU hot-path optimization, and syntax/API/control-flow improvements. This should trigger for requests such as Review Java code for high performance; Optimize Java hot path; Reduce Java allocations; Improve Java latency/throughput. Part of Plinth Toolkit

64

Quality

75%

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/145-java-refactoring-high-performance/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.

A well-organized index-style skill with strong progressive disclosure and a clear measure-first workflow. The body is concise but leans heavily on references for actionable technique, so it lacks executable guidance inline.

Suggestions

Add one or two short inline bad/good code snippets (e.g. a single allocation-reduction pattern) so the body is actionable without requiring a reference read for the most common case.

Make the validation checkpoint more concrete by naming a measurement approach or tool (e.g. JMH, async-profiler) rather than only 'compare before/after behavior'.

Remove the overlap between the 'What is covered' bullet list and the 'When to use' list to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids explaining basic Java/perf concepts; minor redundancy between the 'What is covered' list, 'When to use' list, and the description's triggers could be trimmed.

4 / 5

Actionability

Gives concrete reference-selection guidance (specific file per bottleneck type) but no executable optimization code or commands in the body itself — the actual techniques are entirely delegated to the references, leaving the body's instructions at a high level.

3 / 5

Workflow Clarity

A clear four-step sequence (identify/baseline → select references → apply → validate/compare) with an explicit keep/revert validation step; minor gap is that validation is described abstractly with no specific measurement commands or tools.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview pointing to three real, one-level-deep reference files, each clearly signaled with markdown links and described by bottleneck type in the workflow; content is appropriately split and easy to navigate.

5 / 5

Total

16

/

20

Passed

Description

78%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, well-structured description that clearly states capability and trigger conditions with natural user phrasing. The only notable issue is second-person voice ('you need to') which costs a specificity point.

Suggestions

Rephrase to third person to avoid the specificity penalty, e.g. 'Use when refactoring Java code for high performance ...' instead of 'Use when you need to refactor ...'.

Add a few synonym triggers (e.g. 'speed up Java', 'Java performance tuning') to round out keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('refactor Java code for high performance') and lists three concrete action areas ('memory/allocation reduction, CPU hot-path optimization, and syntax/API/control-flow improvements'), which is a solid 4, but reduced by 1 for the second-person phrasing ('Use when you need to refactor').

3 / 5

Completeness

Explicitly answers both what ('refactor Java code for high performance — including ...') and when ('Use when you need to ... This should trigger for requests such as ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides four natural trigger phrases a user would actually say ('Review Java code for high performance', 'Optimize Java hot path', 'Reduce Java allocations', 'Improve Java latency/throughput'); a few common synonyms like 'speed up Java' or 'Java performance tuning' are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Java high-performance refactoring) with distinct triggers, but 'refactor Java code' creates minor overlap risk with a general Java refactoring skill.

4 / 5

Total

16

/

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.