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

164 Java Profiling Verify

by jabrena in jabrena/plinth

A skill your agent uses when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report…

Apache-2.0Auto-check passedDevelopment

Install 164 Java Profiling Verify

skills CLI
$ npx skills add jabrena/plinth --skill 164-java-profiling-verify -a claude-code

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

GitHub CLI
$ gh skill install jabrena/plinth 164-java-profiling-verify --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/164-java-profiling-verify .claude/skills/164-java-profiling-verify && 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
164-java-profiling-verify
GitHub stars
446
Token cost
~941 tokens
SKILL.md length
332 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 verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report…

  • Post-refactoring report generation
  • SKILL.md covers Constraints, When to use this skill, Workflow and Reference
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Quantitative before/after metrics comparison

What it does

164 Java Profiling Verify is an agent skill from jabrena/plinth. Use when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis, regression detection, or creating profiling-comparison-analysis and profiling-final-results documentation. This should trigger for requests such as Verify performance fix; Verify the performance; Verify the memory; Verify the threading; Compare…

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/164-java-profiling-verify.md`).

It sits in Development, covering Performance optimization and Refactoring. 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

  • Post-refactoring report generation
  • Quantitative before/after metrics comparison
  • Side-by-side flamegraph analysis
  • Regression detection

Example prompts

  • “/164-java-profiling-verify”

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

164 Java Profiling Verify loads about 941 tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 163 tokens; SKILL.md has 332 words of instructions outside code blocks.

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

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). 332 words, ~941 tokens.

Download SKILL.mdSave it as .claude/skills/164-java-profiling-verify/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
164-java-profiling-verify
description
Use when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis, regression detection, or creating profiling-comparison-analysis and profiling-final-results documentation. This should trigger for requests such as Verify performance fix; Verify the performance; Verify the memory; Verify the threading; Compare before and after profiling results; Check for performance regressions after refactoring. Part of Plinth Toolkit
license
Apache-2.0
metadata.author
Juan Antonio Breña Moral
metadata.version
0.19.0

Java Profiling Workflow / Step 4 / Verify results

Verify performance optimizations through rigorous before/after comparison: ensure baseline and post-refactoring profiling data use identical test conditions, generate post-refactoring reports, compare metrics (memory, CPU, GC, threading), perform side-by-side flamegraph analysis, document findings in profiling-comparison-analysis-YYYYMMDD.md and profiling-final-results-YYYYMMDD.md, and validate success criteria.

What is covered in this Skill?

  • Pre-refactoring baseline: run profiler with same load before changes
  • Post-refactoring: generate new reports with identical test conditions
  • Comparison: memory (leaks, allocations, GC), CPU (hotspots, contention), visual flamegraph comparison
  • Documentation: profiler/docs/profiling-comparison-analysis-YYYYMMDD.md, profiler/docs/profiling-final-results-YYYYMMDD.md
  • File naming: baseline/after suffixes, timestamp-based organization
  • Validation: verify reports exist, compare metrics, identify regressions

Scope: Identical test conditions are critical. Document test scenarios. Validate application runs with refactored code before generating new reports.

Constraints

Use identical test conditions between baseline and post-refactoring. Verify both report sets are complete. Document test scenarios.

  • CONSISTENCY: Use identical test conditions and load patterns for baseline and post-refactoring
  • VALIDATE: Ensure both baseline and post-refactoring reports exist and are non-empty before comparison
  • DOCUMENT: Record test scenarios and load patterns for reproduction
  • BEFORE APPLYING: Read the reference for comparison templates and validation steps
  • 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

  • Verify performance fix
  • Verify the performance
  • Verify the memory
  • Verify the threading
  • Verify the GC
  • Verify the profiling
  • Compare before and after profiling results
  • Performance benchmark
  • Check for performance regressions after refactoring

Workflow

  1. Read verification reference and confirm baseline data

Read references/164-java-profiling-verify.md and verify baseline artifacts exist and are non-empty.

  1. Generate post-refactoring profiling data

Run profiling with identical load/test conditions to produce comparable post-refactoring artifacts.

  1. Compare before/after metrics and visuals

Perform quantitative comparisons for memory/CPU/GC/threading and side-by-side flamegraph analysis.

  1. Document final verification outcome

Create comparison and final results reports with regressions, gains, and reproducible scenario details.

Reference

For detailed guidance, examples, and constraints, see references/164-java-profiling-verify.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/164-java-profiling-verify of jabrena/plinth.

  • SKILL.md
  • references/164-java-profiling-verify.md

Open the folder on GitHubat commit dca88dc

Compare with similar skills

164 Java Profiling Verify 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.

164 Java Profiling Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
164 Java Profiling Verify this skilljabrena/plinth446—~941Automated safety check: PassApache-2.0
Caffeine Cache Optimization Experimentsben-manes/caffeine18k—~2.6kAutomated safety check: NotesApache-2.0
Svelte5 Best PracticesSikandarJODD/cnblocks4301 repos~810Automated safety check: PassMIT
React Best Practicesshapeshift/web2061 repos~2kAutomated safety check: PassMIT
Caffeine Performance Auditben-manes/caffeine18k—~559Automated safety check: PassApache-2.0
Groovy 5 Developer Guideapache/grails-core2.9k—~3kAutomated safety check: PassApache-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

  • Svelte5 Best Practices

    SikandarJODD/cnblocks

    Svelte 5 runes, snippets, SvelteKit patterns, and modern best practices for TypeScript and component development.

    430 GitHub starsUsed in 1 repo~810 tokens
    DevelopmentAuto-check passed

  • React Best Practices

    shapeshift/web

    Comprehensive React and Next.js performance optimization guide with 40+ rules for eliminating waterfalls, optimizing bundles, and improving rendering.

    206 GitHub starsUsed in 1 repo~2k tokens
    DevelopmentAuto-check passed

  • 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

  • Java Design Patterns Reference

    decebals/claude-code-java

    A practical Java reference for Builder, Factory, Singleton, Strategy, Observer and other patterns, with a table matching problems to patterns.

    751 GitHub starsUsed in 1 repo~4.4k tokens
    DevelopmentAuto-check passed

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 today
    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 today
    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 today
    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 today
    Auto-check passed

  • 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…

    446 GitHub stars~903 tokensUpdated today
    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 today
    Auto-check passed

Works with

Categories

Questions about 164 Java Profiling Verify

What does 164 Java Profiling Verify do?

A skill your agent uses when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report…. 164 Java Profiling Verify is an agent skill from jabrena/plinth. Use when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis, regression detection, or creating profiling-comparison-analysis and profiling-final-results documentation.

When should I use 164 Java Profiling Verify?

164 Java Profiling Verify fits situations like: post-refactoring report generation; quantitative before/after metrics comparison; side-by-side flamegraph analysis; regression detection.

How do I install 164 Java Profiling Verify in Claude Code?

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

How do I install 164 Java Profiling Verify in Codex?

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

Can I use 164 Java Profiling Verify 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 164-java-profiling-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/164-java-profiling-verify, .gemini/skills/164-java-profiling-verify, .github/skills/164-java-profiling-verify and .opencode/skills/164-java-profiling-verify in your project.

What does 164 Java Profiling Verify need to run?

SKILL.md names no scripts, command-line tools or credentials: 164 Java Profiling Verify is instructions for the agent only.

Does 164 Java Profiling Verify 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 164 Java Profiling Verify 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 164 Java Profiling Verify use?

164 Java Profiling Verify 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 164 Java Profiling Verify use?

About 941 tokens (SKILL.md is roughly 3.8k 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 3.3k tokens, read only when the agent opens those files.

What are the alternatives to 164 Java Profiling Verify?

Skills that share tags, products or a category with 164 Java Profiling Verify: Caffeine Cache Optimization Experiments (ben-manes/caffeine, 18k stars), Svelte5 Best Practices (SikandarJODD/cnblocks, 430 stars), React Best Practices (shapeshift/web, 206 stars) and Caffeine Performance Audit (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 164 Java Profiling Verify?

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.