161-java-profiling-detect

Use when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x 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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-organized overview that appropriately defers detail to a single one-level reference and lists real scripts, but the body itself is not directly executable (templates live in the reference) and lacks an artifact-validation feedback loop, capping actionability and workflow clarity at 2.

Suggestions

Inline a minimal copy-paste-ready snippet for the core attach command (or a direct chmod/mkdir sequence) so the body is executable without opening the reference.

Add an explicit validate-fix-retry checkpoint after collecting profiling artifacts (e.g., verify the flamegraph/JFR file is non-empty and re-run on failure) to satisfy the workflow-clarity feedback-loop expectation.

Tighten redundancy between the intro, 'What is covered', and Workflow sections to reduce overlap and improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (bulleted coverage list, no over-explaining of profiling concepts), but the intro sentence restates the description and the 'What is covered', Constraints, and Workflow sections overlap, so it could be tightened; not level-3 lean.	2 / 3
Actionability	It names concrete scripts and the profiler directory structure, but the actual executable templates are deferred to the reference ('Read the reference for exact script templates', 'copy script templates verbatim'), leaving the body itself without copy-paste-ready code; not fully executable as written.	2 / 3
Workflow Clarity	The 4-step workflow is clearly sequenced with some checkpoints (verify target process availability, edge-case clarifying questions), but there is no validate-then-fix-then-retry feedback loop on the collected artifacts, so it stops short of the level-3 anchor.	2 / 3
Progressive Disclosure	The body is a concise overview with a single, clearly signaled one-level-deep reference (references/161-java-profiling-detect.md) and real scripts in scripts/, matching the level-3 anchor of well-signaled one-level references.	3 / 3
	Total	9 / 12 Passed

Description

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.

The description is comprehensive, specific, and well-triggered, explicitly answering both what the skill does and when to use it with natural trigger phrases. It is clearly distinguishable and uses third-person voice throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'trusted preinstalled async-profiler v4.x setup', 'problem-driven profiling (CPU, memory, threading, GC, I/O)', 'flamegraphs and JFR recordings', and 'JEP 518/520' — matching the level-3 anchor of multiple specific actions.	3 / 3
Completeness	Clearly answers both 'what' (profiling setup, modes, outputs) and 'when' via 'Use when you need to set up...' and 'This should trigger for requests such as...', matching the level-3 anchor.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases are given — 'Improve the code with profiling', 'Apply Profiling', 'Refactor the code with profiling', 'Add profiling support' — giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow (Java async-profiler profiling with JFR/JEP specifics) and triggers are distinct, making it unlikely to fire for the wrong skill; written in third person.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: 86eb63d

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.