Gatling Build Tools
Guide for deploying and starting Gatling tests on Gatling Enterprise. Use this skill when the user wants to deploy, push, or start tests on Gatling Enterprise using Gatling build tools (aka plugins) and Configuration as Code.
Install
$ agentstack add skill-gatling-gatling-ai-extensions-gatling-build-tools ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-gatling-gatling-ai-extensions-gatling-build-tools) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Gatling Enterprise - Build Tools
Instructions
Step 1: Detect the build tool
Inspect the project root and identify the build tool by looking for these files, in this order:
- Maven:
pom.xml - JavaScript CLI:
package.json - Gradle:
build.gradle, orbuild.gradle.kts - sbt:
build.sbt
Step 2: Load build-tool-specific instructions
Once the build tool is identified, read the corresponding file and follow its instructions:
- Maven: ./references/maven-plugin.md
- JavaScript CLI: ./references/javascript-cli.md
- Gradle: ./references/gradle-plugin.md
- sbt: ./references/sbt-plugin.md
Step 3: Common pre-flight checks
These checks apply regardless of build tools:
- Verify
.gatling/package.confexists and is not empty.
If missing or empty, help the user create it using the Configuration as Code skill.
- Verify API token: check if
GATLING_ENTERPRISE_API_TOKENis set. - Verify tests referenced matches actual test classes in the source tree.
Step 4: Build-tool-specific steps
Follow the instructions from the file loaded in Step 2 for:
- Verifying the project compiles.
- Running the deploy command.
Step 5: Post-deploy
The output logs package and test IDs. Suggest updating .gatling/package.conf with these IDs for consistent future deployments.
Step 6: Starting a test
Ask the user if they want to start the test on Gatling Enterprise. If so, follow the instructions from the file loaded in Step 2 for running the start command.
Troubleshooting
Build tool deploy/start or MCP tool call fails
If the build tool deploy/start or any MCP tool call fails, check authentication first:
- Verify
GATLING_ENTERPRISE_API_TOKENis set in the environment. - If missing, warn the user, suggest using
direnv, and offer to create a.envrcfile. - Never print the actual token value in the terminal or logs.
- The token needs at least the Configure role on Gatling Enterprise.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: gatling
- Source: gatling/gatling-ai-extensions
- License: Apache-2.0
- Homepage: https://gatling.io
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.