How do I install the 161 Java Profiling Detect skill?

Run npx skillmds@latest add jabrena/161-java-profiling-detect in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 161 Java Profiling Detect safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 161 Java Profiling Detect?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 161 Java Profiling Detect free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 161 Java Profiling Detect?

jabrena (@jabrena) published this skill. Their other Agent Skills are listed on their SkillMD profile.

161 Java Profiling Detect by jabrena

Name: 161 Java Profiling Detect
Author: jabrena

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. Part of the skills-for-java project

jabrena c52999e 2 files · 88.7 KB Updated Sep 17, 2026

File contents

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

Set up the Java profiling detection phase: automated environment setup with async-profiler v4.0, 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 async-profiler download
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
EXECUTABLE: Make scripts executable with chmod +x
BEFORE APPLYING: Read the reference for exact script templates and setup instructions

When to use this skill

Review Java code for profiling
Add profiling support

Reference

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

---name: 161-java-profiling-detectdescription: 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 projectlicense: Apache-2.0---# Java Profiling Workflow / Step 1 / Collect data to measure potential issuesSet up the Java profiling detection phase: automated environment setup with async-profiler v4.0, 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 async-profiler download- 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.## ConstraintsCopy 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- **EXECUTABLE**: Make scripts executable with chmod +x- **BEFORE APPLYING**: Read the reference for exact script templates and setup instructions## When to use this skill- Review Java code for profiling- Add profiling support## ReferenceFor detailed guidance, examples, and constraints, see [references/161-java-profiling-detect.md](references/161-java-profiling-detect.md).

Frequently asked questions