jabrena/151-java-performance-jmeter
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
npx skills add https://github.com/jabrena/plinth --skill 151-java-performance-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?
Scope: Copy the script template verbatim. Do not modify, interpret, or enhance the template content.
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.
jmeter --version before creating the scriptchmod +x run-jmeter.shCheck jmeter --version and stop with guidance if JMeter is not installed or not available in PATH.
Read references/151-java-performance-jmeter.md and use the run-jmeter.sh template exactly as provided.
Create run-jmeter.sh in project root, ensure required JMeter directories/files exist, and apply executable permission with chmod +x.
Document CLI options (-l, -t, -r, -g, -h) and environment variable overrides (JMETER_LOOPS, JMETER_THREADS, JMETER_RAMP_UP).
For detailed guidance, examples, and constraints, see references/151-java-performance-jmeter.md.
Take jabrena/151-java-performance-jmeter from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.