162-java-profiling-analyze

Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. This should trigger for requests such as Analyze JFR profile; Analyze the profile; Analyze the performance; Analyze the memory; Analyze the threading; Analyze GC logs from profiling; Prioritize Java profiling bottlenecks by impact. Part of Plinth Toolkit

Quality

89%

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 content is a well-structured, actionable overview with a clear sequenced workflow and a single well-signaled reference file. Minor redundancy and the lack of an explicit feedback loop keep conciseness and workflow_clarity just below the top anchor.

Suggestions

Remove the duplication between the Scope sentence and the Constraints block (e.g. fold VALIDATE/DOCUMENT/CROSS-REFERENCE into the workflow steps rather than restating them as both prose and bullets).

Promote Step 2 from a stated assumption-check into an explicit feedback loop: 'If results do not represent realistic load, report the gap and ask whether to re-profile before continuing.'

Trim the 'When to use' trigger list since those phrases already appear in the frontmatter description, leaving the body to focus on the workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear sections, but the Constraints block restates the Scope sentence ('Validate profiling results represent realistic load... Cross-reference multiple files') and the 'When to use' list repeats trigger phrases already in the description, adding minor redundancy.	4 / 5
Actionability	Concrete guidance is present — specific file globs to inventory, exact output file names with YYYYMMDD templates, and a defined Impact/Effort scoring rubric — but it is instruction-only with no executable commands or code, which is acceptable for this skill type yet leaves minor gaps in copy-paste readiness.	4 / 5
Workflow Clarity	The four-step workflow is clearly sequenced and Step 2 acts as a validation checkpoint with VALIDATE/DOCUMENT/CROSS-REFERENCE constraints plus edge-case handling, but there is no explicit validate-then-fix-then-retry feedback loop, so it sits just below the 5 anchor.	4 / 5
Progressive Disclosure	The SKILL.md body is a concise overview that points to a single, real, one-level-deep reference (references/162-java-profiling-analyze.md, verified to exist) with a clearly signaled link, matching the well-organized overview anchor.	5 / 5
	Total	17 / 20 Passed

Description

100%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 specific, trigger-rich, and complete, clearly stating both what the skill does and when to invoke it with natural phrasing. It occupies a distinct niche within a multi-step profiling workflow.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation... prioritizing fixes using Impact/Effort scoring' — with comprehensive coverage of the analysis domain.	5 / 5
Completeness	Explicitly answers both what (analyze Java profiling data from the detection phase) and when via the 'Use when you need to...' clause with concrete trigger phrases, matching the 5-anchor example.	5 / 5
Trigger Term Quality	Natural user phrases are embedded verbatim ('Analyze JFR profile', 'Analyze the profile', 'Analyze the performance', 'Analyze the memory', 'Analyze the threading', 'Prioritize Java profiling bottlenecks by impact') alongside file extensions like .jfr, giving comprehensive coverage including synonyms.	5 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche — Java profiling analysis as Step 2 of the Plinth Toolkit — with distinct, domain-specific triggers that minimize overlap with unrelated skills.	5 / 5
	Total	20 / 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/162-java-profiling-analyze/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.