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
69
61%
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 strong skill description that clearly defines its scope within Java profiling data analysis. It provides specific concrete actions, natural trigger terms that developers would use, an explicit 'Use when' clause, and enough distinctive detail (flamegraphs, Impact/Effort scoring, specific markdown file types) to avoid conflicts with other skills. The description is well-structured and informative without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with specific markdown files, and prioritizing fixes using Impact/Effort scoring. | 3 / 3 |
Completeness | Clearly answers both 'what' (analyze profiling data, interpret flamegraphs, categorize problems, document evidence, prioritize fixes) and 'when' with an explicit 'Use when' clause specifying the trigger conditions including the detection phase context. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'flamegraphs', 'memory allocation', 'CPU hotspots', 'threading issues', 'Java profiling', 'profiling data'. These are terms a developer would naturally use when seeking help with Java performance analysis. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Java profiling analysis specifically in the post-detection phase, with unique identifiers like 'profiling-problem-analysis' and 'profiling-solutions' markdown files, Impact/Effort scoring, and flamegraph interpretation. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a summary or index card than actionable guidance. It lists categories of analysis (memory, CPU, threading) and mentions documentation templates, but provides zero concrete steps, commands, code examples, or analysis techniques. Nearly all value is deferred to the reference file, leaving the skill body itself largely inert.
Suggestions
Add a concrete, numbered workflow with explicit steps — e.g., '1. List files: `ls profiler/results/` 2. Open flamegraph: `open allocation-flamegraph.svg` 3. Identify top 3 hotspots...' — with validation checkpoints between steps.
Include at least one concrete example of analyzing a specific profiling artifact (e.g., how to read a flamegraph, what patterns indicate a memory leak in a JFR recording) rather than just listing problem categories.
Provide a minimal template snippet for profiling-problem-analysis-YYYYMMDD.md inline so Claude knows the expected output format without needing to read the reference file first.
Remove the duplicate 'Analyze the profiling' entry in the 'When to use this skill' section and eliminate redundancy between the opening paragraph, 'What is covered', 'Scope', and 'Constraints' sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There's some redundancy — the constraints section repeats what's already stated in the scope line, and the 'What is covered' section largely restates the opening sentence. The 'When to use this skill' section has a duplicate entry. However, it's not excessively verbose. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable steps. It describes what to do at a high level (inventory, identify, document, prioritize) but gives no actual commands, code snippets, or specific instructions — everything actionable is deferred to the reference file. | 1 / 3 |
Workflow Clarity | While the opening sentence implies a sequence (inventory → identify → document → prioritize → correlate), there are no explicit numbered steps, no validation checkpoints, and no feedback loops. The workflow is described rather than structured. | 1 / 3 |
Progressive Disclosure | There is a clear reference to a detailed file (references/162-java-profiling-analyze.md), which is good. However, the SKILL.md itself contains almost no actionable overview content — it's essentially a table of contents that defers everything to one reference, making the skill body itself of limited standalone value. | 2 / 3 |
Total | 6 / 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
9ec21dd
- 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.