152-java-performance-gatling — Claude Code skill: how to install
152-java-performance-gatling sets up Gatling load testing in a Java Maven project: dependencies, the Maven plugin, simulations, and runs via ./mvnw gatling:test.
Apache-2.0 219 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 152-java-performance-gatling -a claude-codeWhat 152-java-performance-gatling does
The skill edits pom.xml to add Gatling test-scope dependencies and io.gatling:gatling-maven-plugin, then writes Java simulations under src/test/java. Extras such as gatling.conf, feeders, request-body templates or logback-test.xml go into src/test/resources, and only when the project needs them.
Runs go through ./mvnw gatling:test. With several simulations in the project, it passes -Dgatling.simulationClass=<FullyQualifiedClassName> so the run needs no prompt. When the run ends, it points to the report path printed in the command output and summarizes failed assertions.
Maven is a hard requirement. On a Gradle or sbt project the skill stops and says so before offering anything else. If the build has no Gatling versions yet, it asks which ones to pin or leaves placeholders you have to replace.
What it helps with
- add Gatling and
gatling-maven-plugintopom.xml - write a Java simulation with explicit scenarios, injection profile and assertions
- pick one simulation out of several and run it non-interactively
- wire up feeders and request-body templates from
src/test/resources - locate the report after a run and read the failed assertions
Example prompts for the agent
- Add Gatling performance testing to this Maven project
- Create a Gatling simulation in
src/test/javafor this service - Run only one simulation with
-Dgatling.simulationClass=<FullyQualifiedClassName>
How to install 152-java-performance-gatling
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 152-java-performance-gatling -a claude-code2Manually: put the files in place
~/.claude/skills/152-java-performance-gatling/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/152-java-performance-gatling/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 152-java-performance-gatling -a codex2Manually: put the files in place
.agents/skills/152-java-performance-gatling/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 152-java-performance-gatling -a cursor2Manually: put the files in place
.cursor/skills/152-java-performance-gatling/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/152-java-performance-gatling2Manually: put the files in place
.github/skills/152-java-performance-gatling/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 152-java-performance-gatling -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/152-java-performance-gatlingManually: put the files in place
.devin/skills/152-java-performance-gatling/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 152-java-performance-gatling -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 152-java-performance-gatling
How do I install 152-java-performance-gatling in Claude Code?
Run npx skills add jabrena/plinth --skill 152-java-performance-gatling -a claude-code. The skill file ends up at ~/.claude/skills/152-java-performance-gatling/SKILL.md.
What does 152-java-performance-gatling do?
It wires Gatling into a Maven project: adds the dependencies and plugin to pom.xml, creates Java simulations, runs them with ./mvnw gatling:test and helps you read the report.
Does the skill work with Gradle projects?
No, it targets Maven. On any other build it stops and explains that before suggesting alternatives.
Source text
SKILL.md · Apache-2.0
--- name: 152-java-performance-gatling description: Use when you need to set up Gatling performance testing for a Java Maven project — including adding Gatling dependencies and the Gatling Maven plugin, creating Java simulations, running gatling:test, configuring a simulation class, and reviewing generated reports. This should trigger for requests such as Add Gatling performance testing; Apply Gatling performance testing; Create a Gatling simulation; Add Gatling support; Review Gatling performance test assertions and feeders. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Run performance tests based on Gatling Provide a complete Gatling performance testing setup for Java Maven projects by adding the required test dependencies and Gatling Maven plugin configuration, creating or guiding Java simulation placement, and explaining how to run simulations and inspect reports. **What is covered in this Skill?** - Add Gatling dependencies and the `gatling-maven-plugin` to `pom.xml` - Project structure: `src/test/java` for Java simulations and `src/test/resources` for Gatling configuration, feeders, templates, and logging - Run simulations with `./mvnw gatling:test` - Select a simulation with `-Dgatling.simulationClass=<FullyQualifiedClassName>` when multiple simulations exist - Use `./mvnw gatling:help -Ddetail=true -Dgoal=test` to inspect available plugin options - Review generated Gatling run output and reports under the build output directory **Scope:** Use Gatling through the Maven plugin for Java simulations. Prefer project-local Maven wrapper commands when available. ## Constraints Gatling setup must be Maven-based, reproducible, and compatible with Java project conventions. Prefer official Gatling Maven plugin behavior and avoid inventing unsupported command-line options. - **PREREQUISITE**: Verify the project is Maven-based and prefer `./mvnw` when the Maven wrapper exists - **BUILD CONFIGURATION**: Add Gatling dependencies with test scope and configure `io.gatling:gatling-maven-plugin` in `pom.xml` - **VERSION SELECTION**: Use the project's existing dependency/version-management pattern; if no Gatling versions are present, ask before pinning versions or use placeholders that require replacement - **SIMULATION LOCATION**: Place Java simulations under `src/test/java` using an appropriate package name - **RESOURCE LOCATION**: Place Gatling resources such as `gatling.conf`, feeders, request-body templates, and Logback test configuration under `src/test/resources` - **BEFORE APPLYING**: Read the reference for setup, execution, and verification guidance - **EDGE CASE**: If the project is not Maven-based, stop and explain that this skill targets Maven projects before suggesting Gradle or sbt alternatives - **EDGE CASE**: If multiple simulations exist, configure or pass `-Dgatling.simulationClass=<FullyQualifiedClassName>` for non-interactive execution ## When to use this skill - Add Gatling performance testing - Apply Gatling performance testing - Create a Gatling simulation - Add Gatling support - Review Gatling performance test assertions and feeders ## Workflow 1. **Inspect the Maven project** Check for `pom.xml`, the Maven wrapper, existing test dependencies, dependency management, plugin management, and any existing Gatling configuration. 2. **Add Gatling build configuration** Add the Gatling test dependency and `io.gatling:gatling-maven-plugin` using the project's existing version and plugin configuration style. 3. **Create or adapt Java simulations** Create Java simulation classes under `src/test/java` or adapt existing simulations, keeping scenario names, base URLs, injection profiles, and assertions explicit. 4. **Configure resources** Add optional Gatling resources under `src/test/resources`, including `gatling.conf`, feeders, request body templates, and `logback-test.xml` only when the project needs them. 5. **Run and explain Gatling execution** Use `./mvnw gatling:test` to run simulations and `-Dgatling.simulationClass=<FullyQualifiedClassName>` when a specific simulation must be selected. 6. **Verify reports and next steps** Confirm the Gatling run completed, point to the generated report location from the command output, and summarize any failed assertions or performance findings. ## Reference For detailed guidance, examples, and constraints, see [references/152-java-performance-gatling.md](references/152-java-performance-gatling.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth