mcpField
1
161-java-profiling-detect

161-java-profiling-detect

github.com/jabrenaDevelopment456341 installsUpdated 1d ago
Repository

About 161-java-profiling-detect

A skill for collecting Java application profiling data with a trusted, preinstalled async-profiler. It covers CPU, memory, locks, GC, and I/O, producing timestamped flamegraphs and JFR output.

Key features

  1. 01Use preinstalled async-profiler
  2. 02Profile CPU, memory, locks, GC, and I/O
  3. 03Set up and run profiling scripts
  4. 04Produce flamegraphs and JFR files

Use cases

  1. 01Collect performance data from a Java application
  2. 02Investigate lock contention or GC issues
  3. 03Create flamegraphs and JFR for later analysis

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jabrena/plinth --skill 161-java-profiling-detect

After installing, type/161-java-profiling-detectin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
161-java-profiling-detect.md
scripts/
run-java-process-for-profiling.sh
profile-java-process.sh

Details

From the project README

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.

Comments

Markdown supported