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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

A well-structured overview with a clear, validated workflow and clean one-level reference link. The main gaps are minor redundancy across sections and an abstract core-refactor step whose specifics live entirely in the reference.

Suggestions

Collapse the 'What is covered in this Skill?' and 'When to use this skill' lists into the workflow/intro to remove restatement of the description.

Add one or two concrete refactor patterns (e.g., a representative hotspot fix shape or a pointer to a specific section of the reference) so the core action step is not purely abstract.

Remove the version/date-style phrasing in filenames ('-YYYYMMDD') from prose where a generic name would read cleaner, or note the date format once.

Dimension	Reasoning	Score
Conciseness	The body is largely free of concept explanation Claude already knows, but the intro paragraph, 'What is covered in this Skill?' bullets, and 'When to use' list restate the description and the workflow steps, so it could be tightened.	2 / 3
Actionability	Provides concrete commands ('./mvnw clean verify or mvn clean verify') and named file paths, but the core refactor step ('Implement focused code changes for documented CPU, memory, or threading hotspots, incrementally and safely') stays abstract and defers specifics to the reference.	2 / 3
Workflow Clarity	Four steps are clearly sequenced with an explicit validation checkpoint and feedback loop ('Run ./mvnw clean verify ... if tests fail, fix issues before continuing'), satisfying the destructive/batch feedback-loop requirement.	3 / 3
Progressive Disclosure	The SKILL.md is an organized overview pointing to a single, clearly signaled one-level-deep reference (references/163-java-profiling-refactor.md), which exists in the bundle.	3 / 3
	Total	10 / 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, specific description with explicit triggers and a well-defined niche. Its only weakness is the second-person voice ('Use when you need to ...') which violates the third-person guideline and costs a specificity point.

Suggestions

Rephrase to third person (e.g., 'Refactors Java code based on trusted profiling analysis findings ... Use when refactoring code with profiling ...') to recover the specificity point lost to the voice penalty.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('refactor Java code', 'reviewing ... docs/profiling-problem-analysis and docs/profiling-solutions files', 'identifying specific performance bottlenecks', 'implementing targeted code changes to address CPU, memory, or threading issues'), which would merit 3, but the second-person phrasing 'Use when you need to refactor' triggers the -1 voice penalty.	2 / 3
Completeness	Explicitly answers both what (review docs, identify bottlenecks, refactor) and when ('Use when you need to refactor Java code ...', 'This should trigger for requests such as ...').	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'Refactor the code with profiling; Apply profiling; Optimize hot path; Reduce allocations found in profiling; Fix CPU bottlenecks from profiling analysis' — with good variation.	3 / 3
Distinctiveness Conflict Risk	A clear Java profiling-refactor niche with distinct triggers tied to profiling analysis artifacts, unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: aaee915

Reviewed: 1 day 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.