161-java-profiling-detect

Use when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven profiling (CPU, memory, threading, GC, I/O), interactive profiling scripts, JFR integration with Java 25 (JEP 518, JEP 520), or collecting profiling data with flamegraphs and JFR recordings. This should trigger for requests such as Improve the code with profiling; Apply Profiling; Refactor the code with profiling; Add profiling support; Collect JFR or async-profiler data for Java performance. Part of Plinth Toolkit

Quality

86%

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

78%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.

The body is a well-structured overview with good progressive disclosure, concrete setup instructions, and a clear sequenced workflow. It is slightly held back by mild redundancy between the intro and the bullet/constraint lists and by the absence of an explicit post-collection validation feedback loop.

Suggestions

Collapse the opening paragraph or the 'What is covered' list to remove overlap with the frontmatter description and the Constraints section.

Add an explicit validation step after 'Collect profiling artifacts' (e.g. verify the flamegraph HTML and JFR files exist and are non-empty before analysis) to strengthen the workflow's feedback loop.

Inline one or two of the concrete setup commands (mkdir -p profiler/scripts profiler/results; chmod +x) directly in the workflow steps rather than only describing them, to raise actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence (no explanation of what profiling is), but the opening paragraph restates much of the frontmatter description and overlaps with the 'What is covered' bullets and Constraints, a minor instance of redundancy that could be trimmed.	4 / 5
Actionability	Gives concrete, executable guidance — 'Create profiler/scripts and profiler/results', 'Make scripts executable with chmod +x', specific script paths and JVM-flag application — while correctly deferring the verbatim script bodies to the bundled reference and scripts; only minor gaps remain in the SKILL.md itself.	4 / 5
Workflow Clarity	A clear 4-step sequence (read reference, create workspace/scripts, run app with profiling flags, collect artifacts) with a verification checkpoint ('verify target process availability for profiler attachment') and edge-case handling, but lacks an explicit validate-the-output feedback loop after artifact collection.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview that signals one-level-deep references — references/161-java-profiling-detect.md and scripts/profile-java-process.sh, run-java-process-for-profiling.sh (both verified present in the bundle) — keeping the bulk of detail appropriately split into separate files with clear navigation.	5 / 5
	Total	17 / 20 Passed

Description

95%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.

The description is comprehensive, explicit on both what and when, and rich in natural trigger phrases with a distinct niche. The only issue is the second-person 'you' in the opening clause, which per the rubric reduces the specificity score by one point.

Suggestions

Rewrite the opening in third person / imperative to avoid the 'you' pronoun, e.g. 'Use when setting up Java application profiling to detect and measure performance issues ...', which would restore the specificity score.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'trusted preinstalled async-profiler v4.x setup, problem-driven profiling (CPU, memory, threading, GC, I/O), interactive profiling scripts, JFR integration ... flamegraphs and JFR recordings' — which is comprehensive, but the second-person phrasing 'Use when you need to set up' triggers the required 1-point specificity penalty.	4 / 5
Completeness	Explicitly answers both what ('set up Java application profiling to detect and measure performance issues — including ...') and when ('Use when you need to ... This should trigger for requests such as ...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Provides comprehensive natural trigger phrases users would actually say — 'Improve the code with profiling; Apply Profiling; Refactor the code with profiling; Add profiling support; Collect JFR or async-profiler data' — covering synonyms (profiling, JFR, async-profiler) and common phrasings.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — Java profiling via async-profiler v4.x and JFR with Java 25 JEPs — with distinct, specific triggers that are unlikely to fire for unrelated skills.	5 / 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/161-java-profiling-detect/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.