Agent skill

152 Java Performance Gatling

by jabrena in jabrena/plinth

A skill your agent uses 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…

Apache-2.0Auto-check passedTesting & QA

Install 152 Java Performance Gatling

skills CLI
$ npx skills add jabrena/plinth --skill 152-java-performance-gatling -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jabrena/plinth 152-java-performance-gatling --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/152-java-performance-gatling .claude/skills/152-java-performance-gatling && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
152-java-performance-gatling
GitHub stars
446
Token cost
~1.1k tokens
SKILL.md length
457 words
Files
2 (incl. references)
Skills in repo
124
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses 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…

  • You need to set up Gatling performance testing for a Java Maven project — including adding Gatling dependencies and the Gatling Maven plugin
  • SKILL.md covers Constraints, When to use this skill, Workflow and Reference
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Creating Java simulations

What it does

152 Java Performance Gatling is an agent skill from jabrena/plinth. 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

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/152-java-performance-gatling.md`).

It sits in Testing & QA, covering Load testing. It works with Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

  • 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

Example prompts

  • “/152-java-performance-gatling”

What it can do on your machine

Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

152 Java Performance Gatling loads about 1.1k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 133 tokens; SKILL.md has 457 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~133
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 457 words, ~1,129 tokens.

Download SKILL.mdSave it as .claude/skills/152-java-performance-gatling/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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
metadata.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
Show full SKILL.md (180 more words)Show less

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.

  1. 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.

  1. 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.

  1. 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.

  1. Run and explain Gatling execution

Use ./mvnw gatling:test to run simulations and -Dgatling.simulationClass=<FullyQualifiedClassName> when a specific simulation must be selected.

  1. 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.

© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/152-java-performance-gatling of jabrena/plinth.

  • SKILL.md
  • references/152-java-performance-gatling.md

Open the folder on GitHubat commit dca88dc

Compare with similar skills

152 Java Performance Gatling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

152 Java Performance Gatling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
152 Java Performance Gatling this skilljabrena/plinth446—~1.1kAutomated safety check: PassApache-2.0
Afrexai Performance EngineeringLeoYeAI/openclaw-master-skills2.2k—~7.1kAutomated safety check: PassMIT
Java SDK E2E Test with Replay Snapshotgithub/copilot-sdk11k—~1.8kAutomated safety check: PassMIT
Find Untested Sourcesdotnet/skills5.6k1 repos~3.3kAutomated safety check: PassMIT
Microbenchmarkingdotnet/skills5.6k3 repos~3.3kAutomated safety check: PassMIT
Control UI E2Eopenclaw/openclaw392k—~2.9kAutomated safety check: PassMIT

Similar skills

  • Afrexai Performance Engineering

    LeoYeAI/openclaw-master-skills

    Complete performance engineering system — profiling, optimization, load testing, capacity planning, and performance culture.

    2.2k GitHub stars~7.1k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Official

    Creates a Java SDK end-to-end test for the Copilot SDK that runs against a recorded YAML snapshot through a replay proxy, so CI needs no real authentication.

    11k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed
  • Official

    Statically pairs source files with test files to list code that no test references, using Roslyn for C# or tree-sitter for many languages, with no build.

    5.6k GitHub starsUsed in 1 repo~3.3k tokens
    Testing & QAAuto-check passed
  • Microbenchmarking

    dotnet/skills

    Official

    Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks.

    5.6k GitHub starsUsed in 3 repos~3.3k tokens
    Testing & QAAuto-check passed
  • Control UI E2E

    openclaw/openclaw

    A skill your agent uses when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks…

    392k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Omnigent Load Test Runner

    omnigent-ai/omnigent

    Runs the Omnigent load test with real hosts and multi-turn sessions against a mocked LLM, then explains the latency results from summary.md.

    11k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed

More from jabrena/plinth

All 124 skills in this repo
  • A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    446 GitHub stars~874 tokensUpdated today
    Auto-check passed
  • A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…

    446 GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…

    446 GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • A skill your agent uses 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…

    446 GitHub stars~842 tokensUpdated today
    Auto-check passed
  • A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…

    446 GitHub stars~903 tokensUpdated today
    Auto-check passed
  • A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…

    446 GitHub stars~697 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about 152 Java Performance Gatling

What does 152 Java Performance Gatling do?

A skill your agent uses 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…. 152 Java Performance Gatling is an agent skill from jabrena/plinth. 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.

When should I use 152 Java Performance Gatling?

152 Java Performance Gatling fits situations like: 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.

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`. Or copy the skill folder (skills/152-java-performance-gatling in jabrena/plinth) into .claude/skills/152-java-performance-gatling in your project. Claude Code loads it when a task matches its description.

How do I install 152 Java Performance Gatling in Codex?

Run `npx skills add jabrena/plinth --skill 152-java-performance-gatling -a codex`. Or copy the skill folder (skills/152-java-performance-gatling in jabrena/plinth) into .agents/skills/152-java-performance-gatling in your project. Codex loads it when a task matches its description.

Can I use 152 Java Performance Gatling in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 152-java-performance-gatling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/152-java-performance-gatling, .gemini/skills/152-java-performance-gatling, .github/skills/152-java-performance-gatling and .opencode/skills/152-java-performance-gatling in your project.

What does 152 Java Performance Gatling need to run?

SKILL.md names no scripts, command-line tools or credentials: 152 Java Performance Gatling is instructions for the agent only.

Does 152 Java Performance Gatling access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is 152 Java Performance Gatling safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does 152 Java Performance Gatling use?

152 Java Performance Gatling is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 152 Java Performance Gatling use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to 152 Java Performance Gatling?

Skills that share tags, products or a category with 152 Java Performance Gatling: Afrexai Performance Engineering (LeoYeAI/openclaw-master-skills, 2.2k stars), Java SDK E2E Test with Replay Snapshot (github/copilot-sdk, 11k stars), Find Untested Sources (dotnet/skills, 5.6k stars) and Microbenchmarking (dotnet/skills, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 152 Java Performance Gatling?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 446 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.