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. Part of the skills-for-java project
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/162-java-profiling-analyze/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms that users would actually say when needing profiling analysis, explicitly states both what the skill does and when to use it, and carves out a distinct niche within Java performance profiling workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, prioritizing fixes using Impact/Effort scoring.' | 3 / 3 |
Completeness | Explicitly answers both what (analyze profiling data, interpret flamegraphs, document evidence, prioritize fixes) and when ('Use when you need to analyze Java profiling data collected during the detection phase') with clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Java profiling', 'flamegraphs', 'memory allocation', 'CPU hotspots', 'threading issues', and specific file types like 'profiling-problem-analysis' and 'profiling-solutions markdown files.' | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Java profiling analysis post-detection phase, mentions specific artifacts (flamegraphs, Impact/Effort scoring), and references the skills-for-java project context, making conflicts unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a reasonable overview/index pointing to detailed reference material, but it lacks the actionable content that would make it useful on its own. The workflow is described at a conceptual level without concrete examples of how to actually analyze flamegraphs, interpret JFR data, or document findings. The skill would benefit significantly from at least one concrete example of each major analysis type.
Suggestions
Add at least one concrete, executable example showing how to analyze a specific profiling artifact (e.g., a command to open JFR in JMC, or how to interpret a specific flamegraph pattern)
Include a sample snippet of what a profiling-problem-analysis-YYYYMMDD.md entry should look like with actual metrics
Add explicit validation steps such as 'Before documenting findings, verify: (1) sample duration > 5 minutes, (2) request rate matches production baseline, (3) at least 2 profiling sources agree on the hotspot'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - the constraints section repeats information from the scope section, and the 'What is covered' section could be more tightly integrated with the main content. | 2 / 3 |
Actionability | The skill describes what to do at a high level but provides no concrete code, commands, or executable examples. It lists tools and concepts but doesn't show how to actually use them - everything is deferred to a reference file. | 1 / 3 |
Workflow Clarity | The skill outlines a sequence (inventory → identify → document → prioritize) but lacks explicit validation checkpoints or feedback loops. For analysis involving multiple profiling files and documentation, there's no clear 'verify your analysis' step before proceeding. | 2 / 3 |
Progressive Disclosure | The skill appropriately serves as an overview with a clear one-level-deep reference to the detailed guidance file. The structure is well-organized with distinct sections for coverage, constraints, and when to use. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
7772a1b
- Reviewed
Table of Contents
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.