agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/161-java-profiling-detect/SKILL.md

161-java-profiling-detect

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

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; Collect JFR or async-profiler data for Java performance. Part of Plinth Toolkit

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run application with profiling JVM flags (run-java-process-for-profiling.sh)

    line 15
  2. Distinctive:

    Scope: Use the exact bash script templates without modification or interpretation.

    line 22
  3. Distinctive:

    SETUP: Create profiler directory structure: profiler/scripts, profiler/results

    line 29
  4. Very specific:

    SUPPLY CHAIN: Do not download profiler binaries at runtime.

    line 30
  5. Distinctive:

    BEFORE APPLYING: Read the reference for exact script templates and setup instructions

    line 32
  6. Distinctive:

    EDGE CASE: If request scope is ambiguous, stop and ask a clarifying question before applying changes

    line 33
  7. Distinctive:

    EDGE CASE: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance

    line 34
  8. Very specific:

    Read references/161-java-profiling-detect.md and use script templates exactly as provided.

    line 48
  9. Very specific:

    Create profiler/scripts and profiler/results, copy setup/profile scripts verbatim, and make scripts executable.

    line 52
  10. Distinctive:

    Start Java process with required profiling JVM flags and verify target process availability for profiler attachment.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Java Profiling Workflow / Step 1 / Collect data to measure potential issues

Set up the Java profiling detection phase using a trusted preinstalled async-profiler v4.x, problem-driven interactive profiling scripts, and comprehensive data collection for CPU hotspots, memory leaks, lock contention, GC issues, and I/O bottlenecks. Uses JEP 518 (Cooperative Sampling) and JEP 520 (Method Timing) for reduced overhead.

What is covered in this Skill?

  • Run application with profiling JVM flags (run-java-process-for-profiling.sh)
  • Interactive profiling script (profiler/scripts/profile-java-process.sh) — copy exact template
  • Directory structure: profiler/scripts/, profiler/results/, profiler/current/
  • Automated OS/architecture detection and trusted preinstalled async-profiler validation
  • CPU, memory, lock, GC, I/O profiling modes
  • Flamegraph and JFR output with timestamped results

Scope: Use the exact bash script templates without modification or interpretation.

Constraints

Copy bash scripts exactly from templates. Ensure JVM flags are applied for profiling compatibility. Verify Java processes are running before attaching profiler.

  • CRITICAL: Copy the bash script templates exactly — do not modify, interpret, or enhance
  • SETUP: Create profiler directory structure: profiler/scripts, profiler/results
  • SUPPLY CHAIN: Do not download profiler binaries at runtime; require ASYNC_PROFILER_HOME or profiler/current to point to a trusted, preinstalled async-profiler distribution
  • EXECUTABLE: Make scripts executable with chmod +x
  • BEFORE APPLYING: Read the reference for exact script templates and setup instructions
  • EDGE CASE: If request scope is ambiguous, stop and ask a clarifying question before applying changes
  • EDGE CASE: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance

When to use this skill

  • Improve the code with profiling
  • Apply Profiling
  • Refactor the code with profiling
  • Add profiling support
  • Collect JFR or async-profiler data for Java performance

Workflow

  1. Read profiling setup reference

Read references/161-java-profiling-detect.md and use script templates exactly as provided.

  1. Create profiler workspace and scripts

Create profiler/scripts and profiler/results, copy setup/profile scripts verbatim, and make scripts executable.

  1. Run application with profiling compatibility

Start Java process with required profiling JVM flags and verify target process availability for profiler attachment.

  1. Collect profiling artifacts

Capture CPU/memory/lock/GC/I/O data and produce timestamped flamegraph and JFR outputs for analysis.

Reference

For detailed guidance, examples, and constraints, see references/161-java-profiling-detect.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free