New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

161 Java Profiling Detect

by jabrena in jabrena/plinth

A skill your agent uses 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…

Apache-2.0Auto-check passedDevelopment

Install 161 Java Profiling Detect

skills CLI
$ npx skills add jabrena/plinth --skill 161-java-profiling-detect -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jabrena/plinth 161-java-profiling-detect --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/161-java-profiling-detect .claude/skills/161-java-profiling-detect && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
161-java-profiling-detect
GitHub stars
446
Token cost
~903 tokens
SKILL.md length
344 words
Files
4 (incl. scripts, references)
Skills in repo
124
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses 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…

  • Problem-driven profiling (CPU
  • SKILL.md covers Constraints, When to use this skill, Workflow and Reference
  • Runs Shell scripts from its folder
  • Interactive profiling scripts

What it does

161 Java Profiling Detect is an agent skill from jabrena/plinth. 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…

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/161-java-profiling-detect.md`, `scripts/profile-java-process.sh` and `scripts/run-java-process-for-profiling.sh`).

It sits in Development, covering Performance optimization. It works with Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

  • Problem-driven profiling (CPU
  • Interactive profiling scripts
  • JFR integration with Java 25 (JEP 518
  • Collecting profiling data with flamegraphs and JFR recordings

Example prompts

  • “/161-java-profiling-detect”

Requirements

  • A Bash shell

What it can do on your machine

Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

161 Java Profiling Detect loads about 903 tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 154 tokens; SKILL.md has 344 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~154
When it runs · the whole SKILL.md, loaded when a task matches
~903
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 344 words, ~903 tokens.

Download SKILL.mdSave it as .claude/skills/161-java-profiling-detect/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
161-java-profiling-detect
description
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
license
Apache-2.0
metadata.author
Juan Antonio Breña Moral
metadata.version
0.19.0

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.

© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/161-java-profiling-detect of jabrena/plinth.

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

Open the folder on GitHubat commit dca88dc

Compare with similar skills

161 Java Profiling Detect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

161 Java Profiling Detect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
161 Java Profiling Detect this skilljabrena/plinth446—~903Automated safety check: PassApache-2.0
Caffeine Cache Optimization Experimentsben-manes/caffeine18k—~2.6kAutomated safety check: NotesApache-2.0
Caffeine Performance Auditben-manes/caffeine18k—~559Automated safety check: PassApache-2.0
Groovy 5 Developer Guideapache/grails-core2.9k—~3kAutomated safety check: PassApache-2.0
Climber Step Minimizationben-manes/caffeine18k—~3kAutomated safety check: NotesApache-2.0
Eviction Policy Regret Auditben-manes/caffeine18k—~16kAutomated safety check: NotesApache-2.0

Similar skills

  • Caffeine Cache Optimization Experiments

    ben-manes/caffeine

    Runs controlled JMH experiments on the Caffeine cache to find shared contention and hot-path waste, then reviews correctness and returns a reviewable patch.

    18k GitHub stars~2.6k tokensUpdated 2 days ago
    DevelopmentAuto-check: notes

  • Caffeine Performance Audit

    ben-manes/caffeine

    Audits the Caffeine cache source for hot-path costs such as allocations, contention and memory layout, reporting only findings tied to specific lines.

    18k GitHub stars~559 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Groovy 5 Developer Guide

    apache/grails-core

    Guidance for Groovy 5 work in Grails projects: syntax, closures, traits, DSLs, metaprogramming, Spock tests, static compilation and Java 21 integration.

    2.9k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed

  • Climber Step Minimization

    ben-manes/caffeine

    Prices each step of the window climber algorithm by disabling it in turn, to find steps that no longer earn their keep and branches that no longer fire.

    18k GitHub stars~3k tokensUpdated 2 days ago
    DevelopmentAuto-check: notes

  • Eviction Policy Regret Audit

    ben-manes/caffeine

    Searches synthetic workloads for cases where Caffeine's adaptive eviction policy falls short of its achievable hit rate, then classifies each gap by cause.

    18k GitHub stars~16k tokensUpdated 2 days ago
    DevelopmentAuto-check: notes

  • Cache Trace Analyzer

    ben-manes/caffeine

    Analyzes a cache trace file for the Caffeine simulator, characterizes its access pattern and recommends which eviction policies to compare.

    18k GitHub stars~702 tokensUpdated 2 days ago
    DevelopmentAuto-check: notes

More from jabrena/plinth

All 124 skills in this repo

  • 703 Technologies Fuzzing Testing

    jabrena/plinth

    A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    446 GitHub stars~874 tokensUpdated yesterday
    Auto-check passed

  • 033 Architecture Diagrams

    jabrena/plinth

    A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…

    446 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • 112 Java Maven Plugins

    jabrena/plinth

    A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…

    446 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed

  • 151 Java Performance Jmeter

    jabrena/plinth

    A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…

    446 GitHub stars~842 tokensUpdated yesterday
    Auto-check passed

  • 001 Commands Inventory

    jabrena/plinth

    A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…

    446 GitHub stars~697 tokensUpdated yesterday
    Auto-check passed

  • 002 Agents Inventory

    jabrena/plinth

    A skill your agent uses when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project…

    446 GitHub stars~675 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about 161 Java Profiling Detect

What does 161 Java Profiling Detect do?

A skill your agent uses 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…. 161 Java Profiling Detect is an agent skill from jabrena/plinth.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.

When should I use 161 Java Profiling Detect?

161 Java Profiling Detect fits situations like: problem-driven profiling (CPU; interactive profiling scripts; JFR integration with Java 25 (JEP 518; collecting profiling data with flamegraphs and JFR recordings.

How do I install 161 Java Profiling Detect in Claude Code?

Run `npx skills add jabrena/plinth --skill 161-java-profiling-detect -a claude-code`. Or copy the skill folder (skills/161-java-profiling-detect in jabrena/plinth) into .claude/skills/161-java-profiling-detect in your project. Claude Code loads it when a task matches its description.

How do I install 161 Java Profiling Detect in Codex?

Run `npx skills add jabrena/plinth --skill 161-java-profiling-detect -a codex`. Or copy the skill folder (skills/161-java-profiling-detect in jabrena/plinth) into .agents/skills/161-java-profiling-detect in your project. Codex loads it when a task matches its description.

Can I use 161 Java Profiling Detect in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 161-java-profiling-detect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/161-java-profiling-detect, .gemini/skills/161-java-profiling-detect, .github/skills/161-java-profiling-detect and .opencode/skills/161-java-profiling-detect in your project.

What does 161 Java Profiling Detect need to run?

Going by SKILL.md and its folder, 161 Java Profiling Detect needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does 161 Java Profiling Detect access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is 161 Java Profiling Detect safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does 161 Java Profiling Detect use?

161 Java Profiling Detect is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 161 Java Profiling Detect use?

About 903 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to 161 Java Profiling Detect?

Skills that share tags, products or a category with 161 Java Profiling Detect: Caffeine Cache Optimization Experiments (ben-manes/caffeine, 18k stars), Caffeine Performance Audit (ben-manes/caffeine, 18k stars), Groovy 5 Developer Guide (apache/grails-core, 2.9k stars) and Climber Step Minimization (ben-manes/caffeine, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 161 Java Profiling Detect?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 446 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.