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
SkillScore75Maintained
Automatic
◆Coding pack
Last verified 8/20/2026
What it changes
Passed 16 of 21 test cases with the skill, and 13 of 21 without it.
Without skill63%
With skill75%
Checks it passed that the model alone missed
Asks whether to proceed with setup guidance.
Uses numeric Impact scores rated from 1 to 5.
Uses numeric Effort scores rated from 1 to 5.
and 3 more in the full report
3 fixed15 passed either way6 still failing0 broke
Pass-rate lift
+13 pp
Tokens
+3%
Agent turns
0%
Response time
-41%
Model gemini-3.6-flashMeasured 8/20/2026v118 of 24 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
Where in our repository structure should the standardized profiling problem report and solution report be saved, and what naming convention must be used for those markdown files?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses the path template docs/profiling-problem-analysis-YYYYMMDD.md for the problem analysis file.
Missed
Passed
Uses the path template docs/profiling-solutions-YYYYMMDD.md for the solutions file.
Missed
Passed
case-10 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md58 lines2 files
Java Profiling Workflow / Step 2 / Analyze profiling data
Analyze profiling results systematically: inventory results (flamegraphs, JFR, GC logs, thread dumps), identify problems (memory leaks, CPU hotspots, threading issues), document findings using standardized templates (profiling-problem-analysis-YYYYMMDD.md, profiling-solutions-YYYYMMDD.md), prioritize using Impact/Effort scores, and correlate multiple profiling files for validation.
What is covered in this Skill?
Inventory: scan profiler/results/ for allocation-flamegraph, heatmap-cpu, memory-leak, *.jfr, *.log, *.txt
Problem identification: memory (leaks, excessive allocations, GC pressure), performance (CPU hotspots, blocking), threading (deadlocks, contention, pool saturation)
Use when you need to generate or improve Java project documentation — including README.md files, package-info.java files, and Javadoc enhancements — through a modular, step-based interactive process that adapts to your specific documentation needs. This should trigger for requests such as Improve the code with documentation; Apply documentation; Refactor the code with documentation; Generate README or developer documentation for a Java project; Document Java APIs architecture or project workflow