162-java-profiling-analyze skill
✓ VerifiedAnalyze Java profiling data to identify memory leaks, CPU hotspots, and threading issues using flamegraphs, JFR, and GC logs.
- GitHub stars
- 462
- Files
- 2
- Last commit
- Nov 11, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the 162-java-profiling-analyze skill do?
162-java-profiling-analyze analyzes Java profiling data to identify memory leaks, CPU hotspots, and threading issues using flamegraphs, JFR, and GC logs.
Summary generated from the skill's SKILL.md.
About the 162-java-profiling-analyze skill
Identifying memory leaks, CPU hotspots, and threading issues from Java performance data is the primary function of this skill. Developers use it when they need to interpret complex profiling artifacts like JFR files, flamegraphs, heatmaps, and GC logs. The agent scans the profiler/results/ directory to inventory files such as allocation-flamegraphs and thread dumps before performing a systematic analysis.
Once the data is inventoried, the agent categorizes problems including excessive allocations, GC pressure, deadlocks, and pool saturation. It produces structured documentation by creating profiling-problem-analysis-YYYYMMDD.md and profiling-solutions-YYYYMMDD.md files within the docs folder. To help teams manage technical debt, it assigns Impact and Effort scores from 1 to 5 to prioritize which bottlenecks to fix first.
This skill relies on cross-referencing multiple files to validate findings and ensures that all conclusions are based on realistic load scenarios. It works with data typically generated by tools like async-profiler, JProfiler, YourKit, or GCViewer to provide quantitative evidence for performance tuning.
What an agent can do with it
- 1Analyze JFR profilesAn AI agent can examine Java Flight Recorder data to find performance bottlenecks.
- 2Identify memory leaksThe skill detects excessive allocations and memory pressure within the application.
- 3Prioritize performance fixesDevelopers can rank profiling bottlenecks based on their impact and the effort required to resolve them.
- 4Document profiling findingsThe agent generates standardized markdown reports containing quantitative evidence of performance issues.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the 162-java-profiling-analyze skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the 162-java-profiling-analyze skill in Claude Code
~/.claude/skills/162-java-profiling-analyze/SKILL.md
$ npx degit jabrena/plinth/skills/162-java-profiling-analyze ~/.claude/skills/162-java-profiling-analyzeInstall the 162-java-profiling-analyze skill in Claude Code (project)
.claude/skills/162-java-profiling-analyze/SKILL.md
$ npx degit jabrena/plinth/skills/162-java-profiling-analyze .claude/skills/162-java-profiling-analyzeInstall the 162-java-profiling-analyze skill in Codex
~/.agents/skills/162-java-profiling-analyze/SKILL.md
$ npx degit jabrena/plinth/skills/162-java-profiling-analyze ~/.agents/skills/162-java-profiling-analyzeInstall the 162-java-profiling-analyze skill in Gemini CLI
~/.gemini/skills/162-java-profiling-analyze/SKILL.md
$ npx degit jabrena/plinth/skills/162-java-profiling-analyze ~/.gemini/skills/162-java-profiling-analyzeInstall the 162-java-profiling-analyze skill in Claude.ai
npx degit jabrena/plinth/skills/162-java-profiling-analyze 162-java-profiling-analyze && zip -r 162-java-profiling-analyze.zip 162-java-profiling-analyze # claude.ai → Customize → Skills → + → Create skill → Upload a skill → 162-java-profiling-analyze.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablejabrena/plinth/skills/162-java-profiling-analyze is public and reachablegithub.com/jabrena/plinth/tree/HEAD/skills/162-java-profilin ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/jabrena/plinth/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/jabrena/plinth/blob/HEAD/skills/162-java-profilin ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/jabrena/plinth/blob/HEAD/skills/162-java-profilin ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 67 linesgithub.com/jabrena/plinth/blob/HEAD/skills/162-java-profilin ↗Pass
SKILL.md
View on GitHubJava 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)
- Documentation: docs/profiling-problem-analysis-YYYYMMDD.md, docs/profiling-solutions-YYYYMMDD.md
- Prioritization: Impact (1–5) / Effort (1–5), focus on high priority first
- Tools: async-profiler, JFR, JProfiler/YourKit, GCViewer, flamegraphs, heatmaps
Scope: Validate profiling results represent realistic load scenarios. Cross-reference multiple files. Include quantitative metrics.
Constraints
Validate profiling results represent realistic load before analysis. Document assumptions and limitations. Cross-reference multiple files.
- VALIDATE: Ensure profiling results represent realistic load scenarios before analysis
- DOCUMENT: Record assumptions and limitations in analysis reports
- CROSS-REFERENCE: Use multiple profiling files to validate findings
- BEFORE APPLYING: Read the reference for problem analysis and solutions templates
- EDGE CASE: If request scope is ambiguous, stop and ask a clarifying question before applying changes
- EDGE CASE: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance
When to use this skill
- Analyze JFR profile
- Analyze the profile
- Analyze the performance
- Analyze the memory
- Analyze the threading
- Analyze the GC
- Analyze the profiling
- Prioritize Java profiling bottlenecks by impact
- Performance analysis
Workflow
- Read analysis reference and inventory inputs
Read references/162-java-profiling-analyze.md and inventory profiling artifacts in profiler/results/.
- Validate data quality and assumptions
Confirm datasets represent realistic load conditions and record assumptions/limitations before drawing conclusions.
- Identify and prioritize bottlenecks
Analyze memory/CPU/threading findings, cross-reference multiple files, and prioritize issues by Impact/Effort.
- Document findings and solution options
Create docs/profiling-problem-analysis-YYYYMMDD.md and docs/profiling-solutions-YYYYMMDD.md with quantitative evidence.
Reference
For detailed guidance, examples, and constraints, see references/162-java-profiling-analyze.md.
Files in this skill
2162-java-profiling-analyze skill questions
How do I install the 162-java-profiling-analyze skill in Claude Code?
Run npx degit jabrena/plinth/skills/162-java-profiling-analyze ~/.claude/skills/162-java-profiling-analyze. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the 162-java-profiling-analyze skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What types of profiling artifacts can this skill analyze?
The skill can inventory and analyze allocation flamegraphs, CPU heatmaps, memory leak reports, JFR files, GC logs, and thread dumps.
How are identified performance issues prioritized?
Issues are prioritized using an Impact/Effort scoring system ranging from 1 to 5 to focus on high-priority bottlenecks first.
What documentation is produced after the analysis?
The skill generates standardized markdown files for problem analysis and proposed solutions, including quantitative evidence.