菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guidance for using the Gatling MCP server's tools (tests, runs, packages, source repositories, locations, teams) to inspect and drive Gatling Enterprise. Use whenever calling those tools, before assuming an ID, role, or format that isn't spelled out in the tool's own description.
Guide to generate or update the .gatling/package.conf package descriptor file for Gatling Enterprise deployment. Use this skill when the user wants to configure, set up, or modify their package descriptor file, stop criteria, or load generator settings using Configuration as Code.
Guide for converting Apache JMeter tests to Gatling. Use this skill whenever the user mentions JMeter, .jmx files, JMeter test plans, or asks to convert or migrate a JMeter test to Gatling.
Guide for converting HP/Micro Focus/OpenText LoadRunner scripts to Gatling. Use this skill whenever the user mentions LoadRunner, VuGen, LR scripts, .c action files, vuser_init, web_url, web_submit_data, or any LoadRunner-specific functions. Trigger on phrases like "convert this action", "convert this LoadRunner test to Gatling", "migrate from LoadRunner", or when the user shares .c/.h files that look like LoadRunner scripts.
Bootstrap/set up a Gatling project to get started with Gatling load tests.
Find an existing Gatling project, detect language and build tool used
| name | gatling-build-tools |
| description | 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. |
| license | Apache-2.0 |
| mcp-server | gatling |
Inspect the project root and identify the build tool by looking for these files, in this order:
pom.xmlpackage.jsonbuild.gradle, or build.gradle.ktsbuild.sbtOnce the build tool is identified, read the corresponding file and follow its instructions:
These checks apply regardless of build tools:
.gatling/package.conf exists and is not empty.
If missing or empty, help the user create it using the Configuration as Code skill.GATLING_ENTERPRISE_API_TOKEN is set.Follow the instructions from the file loaded in Step 2 for:
The output logs package and test IDs.
Suggest updating .gatling/package.conf with these IDs for consistent future deployments.
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.
If the build tool deploy/start fails, see the /Gatling:gatling-mcp skill's Troubleshooting section for authentication checks.