원클릭으로 Manus에서 모든 스킬 실행

gatling-build-tools

스타5

포크1

업데이트2026년 7월 24일 12:09

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 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

gatling

gatling/gatling-ai-extensions

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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, or build.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.conf exists 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_TOKEN is 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

If the build tool deploy/start fails, see the /Gatling:gatling-mcp skill's Troubleshooting section for authentication checks.

이 저장소의 다른 Skills

같은 저장소

gatling-mcp

gatling/gatling-ai-extensions

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.

2026-07-245

gatling-configuration-as-code

gatling/gatling-ai-extensions

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.

2026-07-245

gatling-convert-from-jmeter

gatling/gatling-ai-extensions

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.

2026-07-245

gatling-convert-from-loadrunner

gatling/gatling-ai-extensions

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.

2026-07-245

gatling-bootstrap-project

gatling/gatling-ai-extensions

Bootstrap/set up a Gatling project to get started with Gatling load tests.

2026-07-105

gatling-detect-existing-project

gatling/gatling-ai-extensions

Find an existing Gatling project, detect language and build tool used

2026-03-275

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

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, or build.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.conf exists 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_TOKEN is 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

If the build tool deploy/start fails, see the /Gatling:gatling-mcp skill's Troubleshooting section for authentication checks.