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. Part of the skills-for-java project
74
67%
Does it follow best practices?
Impact
Pending
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 articulates what the skill does (Java profiling setup and performance measurement) and when to use it. It includes specific tools (async-profiler v4.0, JFR), concrete profiling domains (CPU, memory, threading, GC, I/O), and output formats (flamegraphs, JFR recordings). The description uses proper third-person voice and provides excellent trigger term coverage for Java developers.
| 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', 'collecting profiling data with flamegraphs and JFR recordings'. | 3 / 3 |
Completeness | Explicitly answers both what (setup profiling, detect performance issues, various profiling types) AND when ('Use when you need to set up Java application profiling to detect and measure performance issues'). The 'Use when' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Java', 'profiling', 'performance issues', 'async-profiler', 'CPU', 'memory', 'threading', 'GC', 'I/O', 'flamegraphs', 'JFR'. These are terms developers naturally use when discussing Java performance. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: Java profiling specifically with async-profiler v4.0, JFR, Java 25 JEPs. The specific tool versions and Java-specific terminology make it unlikely to conflict with general debugging or other language profiling skills. | 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 functions primarily as a table of contents pointing to a reference file rather than providing actionable guidance itself. While it correctly identifies what profiling covers and when to use it, the complete absence of executable code or concrete commands in the body undermines its utility. The skill would benefit from including at least the basic setup commands and one example script inline.
Suggestions
Include the actual bash script template or at minimum the core profiling commands directly in the skill body rather than deferring everything to the reference file
Add a numbered workflow with explicit steps: 1) Create directories, 2) Download async-profiler, 3) Set JVM flags, 4) Run profiling script, with validation checkpoints
Provide at least one concrete, copy-paste ready example command (e.g., the chmod command, directory creation, or a sample profiler invocation)
Remove redundancy between the description paragraph and the 'What is covered' bullet list
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy between the description and the 'What is covered' section. The bullet points are helpful but could be tighter. | 2 / 3 |
Actionability | Despite mentioning 'exact bash script templates' multiple times, no actual code or commands are provided in the skill body. All concrete guidance is deferred to the reference file, making this skill abstract rather than executable. | 1 / 3 |
Workflow Clarity | The skill mentions steps (create directories, make scripts executable, verify processes) but lacks clear sequencing and explicit validation checkpoints. The workflow is implied rather than explicitly structured. | 2 / 3 |
Progressive Disclosure | There is a clear reference to a detailed file, but the skill body itself provides almost no actionable content - it's essentially just a pointer to the reference file with some context. The balance between overview and reference is off. | 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.
7772a1b
Table of Contents
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.