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.
A skill your agent uses when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading…
Install 162 Java Profiling Analyze
$ npx skills add jabrena/plinth --skill 162-java-profiling-analyze -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jabrena/plinth 162-java-profiling-analyze --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/162-java-profiling-analyze .claude/skills/162-java-profiling-analyze && rm -rf skills-srcUse ~/.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/
Install the "162-java-profiling-analyze" agent skill from https://github.com/jabrena/plinth/tree/main/skills/162-java-profiling-analyze into .claude/skills/162-java-profiling-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "162-java-profiling-analyze", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jabrena/plinth/tree/main/skills/162-java-profiling-analyzeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jabrena/plinth --skill 162-java-profiling-analyze -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jabrena/plinth 162-java-profiling-analyze --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/162-java-profiling-analyze .agents/skills/162-java-profiling-analyze && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "162-java-profiling-analyze" agent skill from https://github.com/jabrena/plinth/tree/main/skills/162-java-profiling-analyze into .agents/skills/162-java-profiling-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "162-java-profiling-analyze", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 162-java-profiling-analyze -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jabrena/plinth 162-java-profiling-analyze --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/162-java-profiling-analyze .cursor/skills/162-java-profiling-analyze && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "162-java-profiling-analyze" agent skill from https://github.com/jabrena/plinth/tree/main/skills/162-java-profiling-analyze into .cursor/skills/162-java-profiling-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "162-java-profiling-analyze", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jabrena/plinth.git --path skills/162-java-profiling-analyze--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jabrena/plinth --skill 162-java-profiling-analyze -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jabrena/plinth 162-java-profiling-analyze --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/162-java-profiling-analyze .gemini/skills/162-java-profiling-analyze && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "162-java-profiling-analyze" agent skill from https://github.com/jabrena/plinth/tree/main/skills/162-java-profiling-analyze into .gemini/skills/162-java-profiling-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "162-java-profiling-analyze", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jabrena/plinth 162-java-profiling-analyzeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jabrena/plinth --skill 162-java-profiling-analyze -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/162-java-profiling-analyze .github/skills/162-java-profiling-analyze && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "162-java-profiling-analyze" agent skill from https://github.com/jabrena/plinth/tree/main/skills/162-java-profiling-analyze into .github/skills/162-java-profiling-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "162-java-profiling-analyze", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 162-java-profiling-analyze -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jabrena/plinth 162-java-profiling-analyze --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/162-java-profiling-analyze .opencode/skills/162-java-profiling-analyze && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "162-java-profiling-analyze" agent skill from https://github.com/jabrena/plinth/tree/main/skills/162-java-profiling-analyze into .opencode/skills/162-java-profiling-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "162-java-profiling-analyze", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
162-java-profiling-analyze- GitHub stars
- 446
- Used in
- 1 other repo
- Token cost
- ~928 tokens
- SKILL.md length
- 310 words
- Files
- 2 (incl. 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 analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading…
- You need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs
- SKILL.md covers Constraints, When to use this skill, Workflow and Reference
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Memory allocation patterns
What it does
162 Java Profiling Analyze is an agent skill from jabrena/plinth. Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. This should trigger for requests such as Analyze JFR profile; Analyze the profile; Analyze the performance; Analyze the memory; Analyze the threading…
Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/162-java-profiling-analyze.md`).
It sits in Development, covering Performance optimization and Prioritization frameworks. 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
- You need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs
- Memory allocation patterns
- Threading issues
- Systematic problem categorization
Example prompts
- “/162-java-profiling-analyze”
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
No scripts in the folder and no shell commands in SKILL.md.
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
162 Java Profiling Analyze loads about 928 tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 162 tokens; SKILL.md has 310 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 310 words, ~928 tokens.
Download SKILL.mdSave it as
.claude/skills/162-java-profiling-analyze/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- 162-java-profiling-analyze
- description
- Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. This should trigger for requests such as Analyze JFR profile; Analyze the profile; Analyze the performance; Analyze the memory; Analyze the threading; Analyze GC logs from profiling; Prioritize Java profiling bottlenecks by impact. Part of Plinth Toolkit
- license
- Apache-2.0
- metadata.author
- Juan Antonio Breña Moral
- metadata.version
- 0.19.0
Java Profiling Workflow / Step 2 / Analyze profiling data
Analyze profiling results systematically: inventory results (flamegraphs, JFR, GC logs, thread dumps), identify problems (memory leaks, CPU hotspots, threading issues), document findings using standardized templates (profiling-problem-analysis-YYYYMMDD.md, profiling-solutions-YYYYMMDD.md), prioritize using Impact/Effort scores, and correlate multiple profiling files for validation.
What is covered in this Skill?
- Inventory: scan profiler/results/ for allocation-flamegraph, heatmap-cpu, memory-leak, *.jfr, *.log, *.txt
- Problem identification: memory (leaks, excessive allocations, GC pressure), performance (CPU hotspots, blocking), threading (deadlocks, contention, pool saturation)
- Documentation: docs/profiling-problem-analysis-YYYYMMDD.md, docs/profiling-solutions-YYYYMMDD.md
- Prioritization: Impact (1–5) / Effort (1–5), focus on high priority first
- Tools: async-profiler, JFR, JProfiler/YourKit, GCViewer, flamegraphs, heatmaps
Scope: Validate profiling results represent realistic load scenarios. Cross-reference multiple files. Include quantitative metrics.
Constraints
Validate profiling results represent realistic load before analysis. Document assumptions and limitations. Cross-reference multiple files.
- VALIDATE: Ensure profiling results represent realistic load scenarios before analysis
- DOCUMENT: Record assumptions and limitations in analysis reports
- CROSS-REFERENCE: Use multiple profiling files to validate findings
- BEFORE APPLYING: Read the reference for problem analysis and solutions templates
- 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
- Analyze JFR profile
- Analyze the profile
- Analyze the performance
- Analyze the memory
- Analyze the threading
- Analyze the GC
- Analyze the profiling
- Prioritize Java profiling bottlenecks by impact
- Performance analysis
Workflow
- Read analysis reference and inventory inputs
Read references/162-java-profiling-analyze.md and inventory profiling artifacts in profiler/results/.
- Validate data quality and assumptions
Confirm datasets represent realistic load conditions and record assumptions/limitations before drawing conclusions.
- Identify and prioritize bottlenecks
Analyze memory/CPU/threading findings, cross-reference multiple files, and prioritize issues by Impact/Effort.
- Document findings and solution options
Create docs/profiling-problem-analysis-YYYYMMDD.md and docs/profiling-solutions-YYYYMMDD.md with quantitative evidence.
Reference
For detailed guidance, examples, and constraints, see references/162-java-profiling-analyze.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 1 other file (references) in skills/162-java-profiling-analyze of jabrena/plinth.
- SKILL.md
- references/162-java-profiling-analyze.md
Open the folder on GitHubat commit dca88dc
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jabrena/plinth, which our catalogue first saw on October 7, 2026.
Compare with similar skills
162 Java Profiling Analyze 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| 162 Java Profiling Analyze this skilljabrena/plinth | 446 | 1 repos | ~928 | Automated safety check: Pass | Apache-2.0 | |
| Caffeine Cache Optimization Experimentsben-manes/caffeine | 18k | — | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| Caffeine Performance Auditben-manes/caffeine | 18k | — | ~559 | Automated safety check: Pass | Apache-2.0 | |
| Groovy 5 Developer Guideapache/grails-core | 2.9k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Climber Step Minimizationben-manes/caffeine | 18k | — | ~3k | Automated safety check: Notes | Apache-2.0 | |
| Eviction Policy Regret Auditben-manes/caffeine | 18k | — | ~16k | Automated safety check: Notes | Apache-2.0 |
Similar skills
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.
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.
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.
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.
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.
More from jabrena/plinth
All 124 skills in this repo703 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…
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…
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…
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…
161 Java Profiling Detect
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…
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…
Related
Works with
Categories
Questions about 162 Java Profiling Analyze
What does 162 Java Profiling Analyze do?
A skill your agent uses when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading…. 162 Java Profiling Analyze is an agent skill from jabrena/plinth. Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring.
When should I use 162 Java Profiling Analyze?
162 Java Profiling Analyze fits situations like: you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs; memory allocation patterns; threading issues; systematic problem categorization.
How do I install 162 Java Profiling Analyze in Claude Code?
Run `npx skills add jabrena/plinth --skill 162-java-profiling-analyze -a claude-code`. Or copy the skill folder (skills/162-java-profiling-analyze in jabrena/plinth) into .claude/skills/162-java-profiling-analyze in your project. Claude Code loads it when a task matches its description.
How do I install 162 Java Profiling Analyze in Codex?
Run `npx skills add jabrena/plinth --skill 162-java-profiling-analyze -a codex`. Or copy the skill folder (skills/162-java-profiling-analyze in jabrena/plinth) into .agents/skills/162-java-profiling-analyze in your project. Codex loads it when a task matches its description.
Can I use 162 Java Profiling Analyze 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 162-java-profiling-analyze -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/162-java-profiling-analyze, .gemini/skills/162-java-profiling-analyze, .github/skills/162-java-profiling-analyze and .opencode/skills/162-java-profiling-analyze in your project.
What does 162 Java Profiling Analyze need to run?
SKILL.md names no scripts, command-line tools or credentials: 162 Java Profiling Analyze is instructions for the agent only.
Does 162 Java Profiling Analyze 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 162 Java Profiling Analyze 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. Review the folder before installing.
What licence does 162 Java Profiling Analyze use?
162 Java Profiling Analyze 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 162 Java Profiling Analyze use?
About 928 tokens (SKILL.md is roughly 3.7k 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.4k tokens, read only when the agent opens those files.
What are the alternatives to 162 Java Profiling Analyze?
Skills that share tags, products or a category with 162 Java Profiling Analyze: 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 162 Java Profiling Analyze?
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.