Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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 te
.claude/skills/jabrena-151-java-performance-jmeter/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | -31% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 33% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 61% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 18% | 0% |
| case-10 | ✗→✓ | ▲ Improved | -8% | 0% |
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.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 14,164 | 20,368 | +44% | 1 | 1 | 0% | 2,895 | 964 | -67% | 0 | 0 | — |
case-06 | fail→pass | 12,139 | 5,335 | -56% | 1 | 1 | 0% | 2,490 | 1,716 | -31% | 0 | 0 | — |
case-02 | fail→fail | 18,817 | 6,920 | -63% | 1 | 1 | 0% | 3,672 | 1,017 | -72% | 0 | 0 | — |
case-03 | fail→fail | 20,982 | 7,970 | -62% | 1 | 1 | 0% | 4,259 | 1,234 | -71% | 0 | 0 | — |
case-04 | fail→pass | 14,313 | 14,036 | -2% | 1 | 1 | 0% | 3,055 | 4,064 | +33% | 0 | 0 | — |
case-05 | fail→fail | 12,680 | 6,047 | -52% | 1 | 1 | 0% | 2,317 | 970 | -58% | 0 | 0 | — |
case-07 | fail→pass | 12,271 | 15,379 | +25% | 1 | 1 | 0% | 2,261 | 3,635 | +61% | 0 | 0 | — |
case-08 | fail→pass | 19,112 | 4,150 | -78% | 1 | 1 | 0% | 1,220 | 1,441 | +18% | 0 | 0 | — |
case-09 | pass→pass | 6,779 | 8,386 | +24% | 1 | 1 | 0% | 1,161 | 2,034 | +75% | 0 | 0 | — |
case-10 | fail→pass | 13,768 | 3,260 | -76% | 1 | 1 | 0% | 1,306 | 1,200 | -8% | 0 | 0 | — |
case-20 | pass→pass | 13,924 | 20,268 | +46% | 1 | 1 | 0% | 2,718 | 3,639 | +34% | 0 | 0 | — |
case-11 | pass→fail | 9,425 | 3,792 | -60% | 1 | 1 | 0% | 1,540 | 999 | -35% | 0 | 0 | — |
case-12 | fail→pass | 12,614 | 5,258 | -58% | 1 | 1 | 0% | 2,399 | 1,710 | -29% | 0 | 0 | — |
case-13 | fail→pass | 9,005 | 2,597 | -71% | 1 | 1 | 0% | 1,493 | 922 | -38% | 0 | 0 | — |
case-14 | pass→pass | 10,111 | 4,349 | -57% | 1 | 1 | 0% | 1,745 | 1,465 | -16% | 0 | 0 | — |
case-15 | fail→pass | 6,393 | 3,505 | -45% | 1 | 1 | 0% | 1,065 | 1,269 | +19% | 0 | 0 | — |
case-16 | pass→pass | 3,134 | 3,078 | -2% | 1 | 1 | 0% | 434 | 956 | +120% | 0 | 0 | — |
case-17 | fail→pass | 17,856 | 6,678 | -63% | 1 | 1 | 0% | 3,559 | 1,709 | -52% | 0 | 0 | — |
case-18 | fail→fail | 13,094 | 6,881 | -47% | 1 | 1 | 0% | 2,049 | 997 | -51% | 0 | 0 | — |
case-19 | pass→pass | 5,875 | 3,468 | -41% | 1 | 1 | 0% | 883 | 902 | +2% | 0 | 0 | — |
case-21 | pass→pass | 13,884 | 12,584 | -9% | 1 | 1 | 0% | 2,349 | 2,824 | +20% | 0 | 0 | — |
case-22 | pass→pass | 12,800 | 12,789 | -0% | 1 | 1 | 0% | 2,466 | 3,173 | +29% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 15 counted toward the lift figure. The other 7 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +36 percentage points is the difference between those two pass rates over the 15 comparable cases. 4 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.