161-java-profiling-detect
Use when you need to set up Java application profiling to detect and measure performance issues — including automated async-profiler v4.0 setup, problem-driven profiling (CPU, memory, threading, GC, I/O), interactive profiling scripts, JFR integration with Java 25 (JEP 518, JEP 520), or collecting profiling data with flamegraphs and JFR recordings. This should trigger for requests such as Improve the code with profiling; Apply Profiling; Refactor the code with profiling; Add profiling support. Part of cursor-rules-java project
74
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/161-java-profiling-detect/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 around Java application profiling, lists concrete capabilities and tools, and provides explicit trigger guidance with example user phrases. The 'Use when' clause is well-positioned at the start, and the inclusion of specific technologies (async-profiler v4.0, JFR, JEP 518/520) makes it highly distinctive. Minor note: the trailing 'Part of cursor-rules-java project' adds context but doesn't significantly aid skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: automated async-profiler v4.0 setup, problem-driven profiling (CPU, memory, threading, GC, I/O), interactive profiling scripts, JFR integration with Java 25 (JEP 518, JEP 520), collecting profiling data with flamegraphs and JFR recordings. | 3 / 3 |
Completeness | Clearly answers both 'what' (Java profiling setup with async-profiler, JFR integration, flamegraphs, etc.) and 'when' with an explicit 'Use when' clause at the start and specific trigger phrases like 'Apply Profiling', 'Refactor the code with profiling'. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'profiling', 'performance issues', 'CPU', 'memory', 'flamegraphs', 'JFR', and explicit example phrases like 'Improve the code with profiling', 'Add profiling support'. Covers both technical and natural language variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on Java application profiling with specific tools (async-profiler v4.0, JFR, Java 25 JEPs). Unlikely to conflict with general Java development or other performance-related skills due to the specificity of profiling tooling mentioned. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill acts primarily as a pointer to a reference file rather than providing actionable guidance itself. It describes what should be done at a high level but includes zero concrete code, commands, JVM flags, or script templates — all of which are deferred to the reference. The workflow structure is reasonable but lacks validation checkpoints and executable specifics.
Suggestions
Include at minimum the key JVM flags and one concrete profiler command inline in the SKILL.md so Claude has actionable content without needing to read the reference file first.
Add explicit validation steps to the workflow, e.g., 'Verify profiler downloaded successfully: ls profiler/scripts/async-profiler-*' and 'Confirm Java process is running: jps -l | grep <target>'.
Show at least a minimal executable example of the profile script invocation or the directory setup commands directly in the workflow steps rather than deferring everything to the reference.
Remove the 'What is covered in this Skill?' bullet list which largely duplicates the description and workflow — this would improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'What is covered in this Skill?' section largely duplicates the description and workflow) and explains scope that could be tightened. The bullet lists are somewhat redundant with the workflow steps. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. It repeatedly says to 'copy exact templates' and 'use script templates exactly as provided' but never shows any actual script content, JVM flags, or commands. All actionable content is deferred entirely to the reference file. | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence and mentions verification ('verify target process availability'), but lacks explicit validation checkpoints, error recovery feedback loops, and concrete commands at each step. For operations involving profiler attachment and JVM flag configuration, the absence of validation steps is a gap. | 2 / 3 |
Progressive Disclosure | There is a single clear reference to a detailed file (references/161-java-profiling-detect.md), which is good one-level-deep disclosure. However, since no bundle files were provided to verify the reference exists, and the SKILL.md itself contains almost no actionable content (everything is deferred), the balance between overview and reference is poor — the skill body is too thin to stand on its own. | 2 / 3 |
Total | 7 / 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
762cb86
- 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.