agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/151-java-performance-jmeter/SKILL.md

151-java-performance-jmeter

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

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

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create run-jmeter.sh in project root from the exact template (no modifications)

    line 15
  2. Distinctive:

    Verify JMeter is installed and available before proceeding

    line 19
  3. Very specific:

    PREREQUISITE: Verify JMeter is installed and accessible via jmeter --version before creating the script

    line 27
  4. Distinctive:

    BEFORE APPLYING: Read the reference for the exact script template and usage instructions

    line 30
  5. Distinctive:

    EDGE CASE: If request scope is ambiguous, stop and ask a clarifying question before applying changes

    line 31
  6. Distinctive:

    EDGE CASE: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance

    line 32
  7. Distinctive:

    Create a JMeter test plan for a Java service

    line 40
  8. Very specific:

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

    line 46
  9. Very specific:

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

    line 50
  10. Very specific:

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

    line 54
  11. Very specific:

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

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free