163-java-profiling-refactor

Use when you need to refactor Java code based on trusted profiling analysis findings — including reviewing repository-owned or maintainer-sanitized docs/profiling-problem-analysis and docs/profiling-solutions files, identifying specific performance bottlenecks, and implementing targeted code changes to address CPU, memory, or threading issues. This should trigger for requests such as Refactor the code with profiling; Apply profiling; Optimize hot path; Reduce allocations found in profiling; Fix CPU bottlenecks from profiling analysis. Part of Plinth Toolkit

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%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-structured skill body with a clear, validated workflow and sound progressive-disclosure scaffolding. Its weaknesses are mild redundancy across sections and an abstract central refactor action whose specifics are deferred to external profiling docs and a thin reference file.

Suggestions

De-duplicate the trigger phrases and the './mvnw clean verify' command so each appears in one place (e.g., triggers only in 'When to use', the command only in the Workflow/Constraints).

Add a brief, concrete refactor-technique example or pattern (e.g., reducing allocations in a hot loop, caching repeated calls) so the central action is actionable without relying solely on external docs.

Either move genuinely detailed guidance/examples into references/163-java-profiling-refactor.md to fulfill the 'detailed guidance, examples, and constraints' promise, or trim that promise to match the reference's actual depth.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence without explaining known concepts, but the trigger phrases and the './mvnw clean verify' command recur across 'What is covered', 'When to use', Constraints, and Workflow, which is minor redundancy that could be trimmed.	4 / 5
Actionability	Concrete commands ('./mvnw clean verify') and concrete file paths ('docs/profiling-problem-analysis-YYYYMMDD.md') give mostly executable guidance, but the central refactor step is abstract ('Implement focused code changes...incrementally and safely') with no refactor-technique examples, leaving a minor gap.	4 / 5
Workflow Clarity	A clear 4-step sequence with an explicit validation step and a feedback loop ('if tests fail, fix issues before continuing') plus a Constraints checklist; validation is present so the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	A well-organized overview with one clearly signaled, one-level reference that resolves to a real file, but the reference is thin and largely duplicates the body rather than delivering the promised 'detailed guidance, examples, and constraints', a minor split gap.	4 / 5
	Total	17 / 20 Passed

Description

83%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 both capabilities and trigger conditions for a Java profiling-based refactoring skill. Its main weakness is second-person voice and slightly broad triggers that risk overlap with adjacent toolkit skills.

Suggestions

Rewrite in third person to avoid the specificity penalty (e.g., 'Refactors Java code based on trusted profiling analysis findings. Use when refactoring code with profiling...').

Tighten the broad triggers 'Apply profiling' and 'Optimize hot path' by tying them explicitly to existing profiling analysis (e.g., 'Optimize hot path identified in profiling analysis') to reduce overlap with sibling profiling skills.

Add a couple of natural synonyms such as 'performance tuning' or 'speed up Java code' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (reviewing profiling-problem-analysis/profiling-solutions files, identifying bottlenecks, implementing targeted CPU/memory/threading fixes) for comprehensive coverage, but the second-person phrasing 'Use when you need to refactor' triggers the rubric's -1 specificity penalty.	4 / 5
Completeness	Explicitly answers both what ('refactor Java code...reviewing...identifying...implementing targeted code changes') and when ('Use when...This should trigger for requests such as...') with concrete trigger phrases, matching the anchor.	5 / 5
Trigger Term Quality	Five natural trigger phrases ('Refactor the code with profiling; Apply profiling; Optimize hot path; Reduce allocations found in profiling; Fix CPU bottlenecks from profiling analysis') give good coverage, but they are narrow profiling+verb variants missing synonyms like 'performance tuning' or 'speed up', so not a 5.	4 / 5
Distinctiveness Conflict Risk	A clear Java-profiling-refactor niche with profiling-tied triggers, but 'Apply profiling' and 'Optimize hot path' are broad enough to overlap with sibling profiling/analysis skills in the toolkit, so minor overlap risk rather than minimal.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/163-java-profiling-refactor/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.