164-java-profiling-verify

Use when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis, regression detection, or creating profiling-comparison-analysis and profiling-final-results documentation. This should trigger for requests such as Verify performance fix; Verify the performance; Verify the memory; Verify the threading; Compare before and after profiling results; Check for performance regressions after refactoring. Part of Plinth Toolkit

Quality

87%

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

86%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 overview skill that concisely sets up scope, constraints, and a sequenced workflow with validation checkpoints, delegating executable detail to a single clearly-signaled reference file. Actionability is slightly below top because concrete commands live in the reference rather than inline.

Dimension	Reasoning	Score
Conciseness	The body is lean (~60 lines) with no padding or explanation of concepts Claude already knows; every line earns its place and it assumes Claude's competence.	5 / 5
Actionability	Gives concrete file paths and specific actions ('Read references/164-java-profiling-verify.md and verify baseline artifacts exist and are non-empty'), but executable commands live in the delegated reference rather than the body itself.	4 / 5
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints ('VALIDATE: Ensure both baseline and post-refactoring reports exist and are non-empty before comparison') and edge-case handling; the detailed feedback loops reside in the reference.	4 / 5
Progressive Disclosure	A clear overview with a single well-signaled one-level-deep reference (references/164-java-profiling-verify.md, linked in both the Workflow and Reference sections); the referenced file exists and content is appropriately split.	5 / 5
	Total	18 / 20 Passed

Description

88%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 what the skill does and when to use it, with comprehensive natural-language trigger phrases. Minor overlap risk with sibling profiling skills keeps distinctiveness just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis'), giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what ('verify Java performance optimizations by comparing profiling results before and after refactoring') and when ('Use when you need to verify...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes many natural user phrases verbatim ('Verify performance fix', 'Verify the memory', 'Verify the threading', 'Compare before and after profiling results'), covering common variations a user would actually say.	5 / 5
Distinctiveness Conflict Risk	A clear niche (Java profiling verification, step 4 of a workflow) with minimal conflict risk, though trigger phrases like 'Verify the memory'/'Verify the threading' could overlap with other Java profiling skills.	4 / 5
	Total	19 / 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/164-java-profiling-verify/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.