15

151-java-performance-jmeter

Automates JMeter setup and execution for Java services to test performance and load capacity.

Install

mkdir -p .claude/skills/151-java-performance-jmeter && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19374" && unzip -o skill.zip -d .claude/skills/151-java-performance-jmeter && rm skill.zip

Installs to .claude/skills/151-java-performance-jmeter

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use 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 loops, threads, and ramp-up, or running performance tests from the project root with custom or default settings. This should trigger for requests such as Improve the code with JMeter performance testing; Apply JMeter performance testing; Refactor the code with JMeter performance testing; Add JMeter support; Create a JMeter test plan for a Java service. Part of Plinth Toolkit
550 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • Create run-jmeter.sh script from template
  • Configure load test loops, threads, and ramp-up
  • Set up project structure for JMeter results
  • Apply executable permissions to scripts
  • Document CLI options and environment variables

How it works

The skill verifies JMeter installation, copies a verbatim template to the project root, and configures the required directory structure for load testing.

Inputs & outputs

You give it
Java project directory
You get back
run-jmeter.sh script and load testing directory structure

When to use 151-java-performance-jmeter

  • Set up load testing for a Java service
  • Configure loop, thread, and ramp-up counts
  • Execute performance tests from the project root

About this skill

Run performance tests based on JMeter

Provide a complete JMeter performance testing solution by creating the run-jmeter.sh script from the exact template, making it executable, and configuring the project structure for load testing. Supports custom loops, threads, ramp-up, and environment variable overrides.

What is covered in this Skill?

  • Create run-jmeter.sh in project root from the exact template (no modifications)
  • Project structure: src/test/resources/jmeter/load-test.jmx, target/ for results
  • Script options: -l (loops), -t (threads), -r (ramp-up), -g (GUI), -h (help)
  • Environment variables: JMETER_LOOPS, JMETER_THREADS, JMETER_RAMP_UP
  • Verify JMeter is installed and available before proceeding

Scope: Copy the script template verbatim. Do not modify, interpret, or enhance the template content.

Constraints

JMeter must be installed and available in PATH. If not available, show a message and exit. Use only the exact template for the run-jmeter.sh script.

  • PREREQUISITE: Verify JMeter is installed and accessible via jmeter --version before creating the script
  • CRITICAL: Copy the run-jmeter.sh template exactly — do not modify, interpret, or enhance
  • PERMISSION: Make the script executable with chmod +x run-jmeter.sh
  • BEFORE APPLYING: Read the reference for the exact script template and usage 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 JMeter performance testing
  • Apply JMeter performance testing
  • Refactor the code with JMeter performance testing
  • Add JMeter support
  • Create a JMeter test plan for a Java service

Workflow

  1. Verify JMeter prerequisite

Check jmeter --version and stop with guidance if JMeter is not installed or not available in PATH.

  1. Read JMeter reference template

Read references/151-java-performance-jmeter.md and use the run-jmeter.sh template exactly as provided.

  1. Create script and project structure

Create run-jmeter.sh in project root, ensure required JMeter directories/files exist, and apply executable permission with chmod +x.

  1. Explain usage and environment overrides

Document CLI options (-l, -t, -r, -g, -h) and environment variable overrides (JMETER_LOOPS, JMETER_THREADS, JMETER_RAMP_UP).

Reference

For detailed guidance, examples, and constraints, see references/151-java-performance-jmeter.md.

When not to use it

  • Modifying the run-jmeter.sh template content
  • Interpreting or enhancing the template
  • When JMeter is not installed in PATH

Prerequisites

JMeter installed and accessible via jmeter --version

Limitations

  • Requires JMeter to be available in PATH
  • Template must be used exactly as provided

How it compares

This approach uses a standardized, immutable template for script generation rather than manual configuration.

Compared to similar skills

151-java-performance-jmeter side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
151-java-performance-jmeter (this skill)017dReviewBeginner
java-pro343moNo flagsAdvanced
springboot-tdd55moNo flagsIntermediate
managing-api-cache210dReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry