Claude Skill

performance-test-gatling

Use this skill when you need Gatling performance scope, simulations, or runnable entry points; triggers include Gatling, Gatling simulations, and Gatling performance testing.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download naodeng-awesome-qa-skills-skills_en_testing-types_performance-test-gatling-9df700b.zip · 27 KB

Install

skills CLI npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/performance-test-gatling
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
Git git clone https://github.com/naodeng/awesome-qa-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.

README

performance-test-gatling (EN)

Skill Overview

Need performance outputs that should land in Gatling structure; The project already uses Gatling or wants Gatling-ready scenarios.

How to Use

  1. Open SKILL.md in this folder and confirm this skill fits your task.
  2. In your AI tool, call @skill performance-test-gatling, then add your real project context and goal.
  3. If you need a specific output format (table, checklist, report), include it directly in your request.

One-Click Install Script

Run from the repository root:

macOS / Linux

bash ./scripts/install-skills-mac.sh --tool codex --lang en --skill performance-test-gatling

Windows PowerShell

powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill performance-test-gatling

Skill manifest

performance-test-gatling (EN)

Chinese version: See the corresponding Chinese skill.

When to Use

  • Need performance outputs that should land in Gatling structure.
  • The project already uses Gatling or wants Gatling-ready scenarios.

Workflow

  1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
  2. Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
  3. If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
  4. Default to Markdown; switch formats only when the user asks.

Domain Execution Essentials

  1. Read project Gatling/plugin/JDK and Java/Scala/Kotlin DSL versions, retaining its layout. Use compatible injection/assertion APIs in one DSL. Offline test-compile generated assets with the project build; uncached dependencies mean BLOCKED, not a passed compile.
  2. Open models control user arrivals; arrivals equal request RPS only for one request per user without additional loops/retries. Closed models control concurrency; verify RPS from actual request counts/windows.
  3. Calculate feeder consumption per user/loop. Queue exhaustion must visibly fail; circular reuse requires policy permission and non-conflicting identities/business keys.
  4. Use project thresholds and version-supported assertions. Missing gates yield an unconfigured skeleton, not invented 500ms/1% values. Compile, achieved load, and SLO results are distinct evidence.

Core Constraints

  • Prioritize by risk / business impact — do not treat everything equally.
  • Separate confirmed facts from current assumptions; with no SLA/traffic, label every number as Assumption and list Open Questions.
  • Do not invent endpoints, fields, environments, or root causes the user did not provide; secrets are placeholders / env vars only — never real tokens.
  • Keep output executable: concrete scenarios, clear priority, clear next steps.
  • Default to only the most critical 1–2 scenario types — do not run baseline/load/stress/spike/soak all by default.

Progressive Disclosure

  • When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.

  • Before producing output, read and follow prompts/performance-test-gatling.md (minimum coverage, output structure, quality bar).

  • When a ready-made template fits: use matching files under output-templates/.

  • When the user wants examples or alignment with existing assets: read relevant examples/.

  • For deep framework/troubleshoot/schema notes: read only the relevant file(s) under references/, do not load the whole directory.

  • For format conversion or helper checks: prefer existing scripts/ over reinventing.

  • For evaluating/regressing this skill: use evals/ with skill-up.

Pre-delivery Checklist

  • Followed the main prompt's output structure
  • Minimum coverage focus: target scenarios, load model, test data or feeder needs, ramp profile, thresholds, environment and monitoring, priority bottlenecks, reporting needs, ... (details in main prompt)
  • Covered the minimum checklist, or explained omissions
  • High-risk items have explicit priority
  • Did not invent details the user did not provide
  • Assumptions and gaps are marked

Common Pitfalls

  • Do not pretend completeness when scope/context is missing.

  • Do not treat every item as equally important.

  • Do not skip assumptions and information gaps.

  • Do not dump generic theory unrelated to the current toolchain.

  • To check DSL/JMX assets and data-consumption boundaries, read evals/fixtures/java-dsl/README.md; local examples calibrate assets and cannot establish acceptance without project gates.

Files (awesome-qa-skills)
  • agents
    • openai.yaml 501 B
      Loading…
  • evals
    • cases
      • basic-success.yaml 654 B
        Loading…
      • domain-method-regression.yaml 1.5 KB
        Loading…
      • edge-domain-boundary.yaml 637 B
        Loading…
      • edge-incomplete-input.yaml 636 B
        Loading…
    • fixtures
      • java-dsl
        • src
          • test
            • java
              • fixtures
                • CheckoutSimulation.java 1.5 KB · in bundle
            • resources
              • users.csv 17 B · in bundle
        • pom.xml 890 B · in bundle
        • README.md 1023 B
          Loading…
      • check-domain-decisions.sh 95 B
        Loading…
      • check_domain_decisions.py 3.8 KB
        Loading…
      • domain-oracle.json 159 B
        Loading…
    • eval.yaml 607 B
      Loading…
  • examples
    • ci
      • github-actions-gatling.yml 980 B
        Loading…
      • Jenkinsfile.gatling 721 B · in bundle
    • seckill-sample.env 220 B · in bundle
  • output-templates
    • template-markdown.md 83 B
      Loading…
  • prompts
    • performance-test-gatling.md 9.7 KB
      Loading…
  • references
    • local
      • performance-testing_EN.md 497 B
        Loading…
    • domain-decision-example.md 1.7 KB
      Loading…
    • framework-spec.md 1.8 KB
      Loading…
    • setup-and-ci.md 884 B
      Loading…
  • reports
    • .gitignore 87 B · in bundle
    • README.md 1.3 KB
      Loading…
  • scripts
    • simulations
      • ApiSmokeSimulation.scala 1.1 KB · in bundle
      • BaseSimulation.scala 883 B · in bundle
      • LoadSimulation.scala 637 B · in bundle
      • SoakSimulation.scala 536 B · in bundle
      • SpikeSimulation.scala 749 B · in bundle
      • StressSimulation.scala 707 B · in bundle
    • tools
      • compare_gatling.py 1.7 KB
        Loading…
      • local_mock_server.py 2 KB
        Loading…
      • summarize_gatling.py 982 B
        Loading…
    • run-local-smoke.sh 1.3 KB
      Loading…
    • run-tests.sh 1.4 KB
      Loading…
  • README.md 841 B
    # performance-test-gatling (EN)
    
    ## Skill Overview
    
    Need performance outputs that should land in Gatling structure; The project already uses Gatling or wants Gatling-ready scenarios.
    
    ## How to Use
    
    1. Open `SKILL.md` in this folder and confirm this skill fits your task.
    2. In your AI tool, call `@skill performance-test-gatling`, then add your real project context and goal.
    3. If you need a specific output format (table, checklist, report), include it directly in your request.
    
    ## One-Click Install Script
    
    Run from the repository root:
    
    ### macOS / Linux
    
    ```bash
    bash ./scripts/install-skills-mac.sh --tool codex --lang en --skill performance-test-gatling
    ```
    
    ### Windows PowerShell
    
    ```powershell
    powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill performance-test-gatling
    ```
    
  • SKILL.md 4.3 KB
    ---
    name: performance-test-gatling
    description: Use this skill when you need Gatling performance scope, simulations, or runnable entry points; triggers include Gatling, Gatling simulations, and Gatling performance testing.
    license: PolyForm-Noncommercial-1.0.0
    metadata:
      version: "1.0.0"
      compatibility: ""
      author: "Awesome QA Skills contributors"
      language: "en"
      category: "testing-types"
      source: "https://github.com/naodeng/awesome-qa-skills"
      license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0"
    ---
    
    # performance-test-gatling (EN)
    
    **Chinese version:** See the corresponding Chinese skill.
    
    ## When to Use
    
    - Need performance outputs that should land in Gatling structure.
    - The project already uses Gatling or wants Gatling-ready scenarios.
    
    ## Workflow
    
    1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
    2. Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
    3. If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
    4. Default to Markdown; switch formats only when the user asks.
    
    ## Domain Execution Essentials
    
    1. Read project Gatling/plugin/JDK and Java/Scala/Kotlin DSL versions, retaining its layout. Use compatible injection/assertion APIs in one DSL. Offline test-compile generated assets with the project build; uncached dependencies mean BLOCKED, not a passed compile.
    2. Open models control user arrivals; arrivals equal request RPS only for one request per user without additional loops/retries. Closed models control concurrency; verify RPS from actual request counts/windows.
    3. Calculate feeder consumption per user/loop. Queue exhaustion must visibly fail; circular reuse requires policy permission and non-conflicting identities/business keys.
    4. Use project thresholds and version-supported assertions. Missing gates yield an unconfigured skeleton, not invented 500ms/1% values. Compile, achieved load, and SLO results are distinct evidence.
    
    ## Core Constraints
    
    - Prioritize by risk / business impact — do not treat everything equally.
    - Separate confirmed facts from current assumptions; with no SLA/traffic, label every number as Assumption and list Open Questions.
    - Do not invent endpoints, fields, environments, or root causes the user did not provide; secrets are placeholders / env vars only — never real tokens.
    - Keep output executable: concrete scenarios, clear priority, clear next steps.
    - Default to only the most critical 1–2 scenario types — do not run baseline/load/stress/spike/soak all by default.
    
    ## Progressive Disclosure
    
    - When calibrating domain outcomes, valid controls, or evidence gaps, read [references/domain-decision-example.md](references/domain-decision-example.md) for sanitized input, per-item oracles, and reproducible calculations.
    
    - Before producing output, read and follow `prompts/performance-test-gatling.md` (minimum coverage, output structure, quality bar).
    - When a ready-made template fits: use matching files under `output-templates/`.
    - When the user wants examples or alignment with existing assets: read relevant `examples/`.
    - For deep framework/troubleshoot/schema notes: read only the relevant file(s) under `references/`, do not load the whole directory.
    - For format conversion or helper checks: prefer existing `scripts/` over reinventing.
    - For evaluating/regressing this skill: use `evals/` with skill-up.
    
    ## Pre-delivery Checklist
    
    - [ ] Followed the main prompt's output structure
    - [ ] Minimum coverage focus: target scenarios, load model, test data or feeder needs, ramp profile, thresholds, environment and monitoring, priority bottlenecks, reporting needs, ... (details in main prompt)
    - [ ] Covered the minimum checklist, or explained omissions
    - [ ] High-risk items have explicit priority
    - [ ] Did not invent details the user did not provide
    - [ ] Assumptions and gaps are marked
    
    ## Common Pitfalls
    
    - Do not pretend completeness when scope/context is missing.
    - Do not treat every item as equally important.
    - Do not skip assumptions and information gaps.
    - Do not dump generic theory unrelated to the current toolchain.
    
    - To check DSL/JMX assets and data-consumption boundaries, read [evals/fixtures/java-dsl/README.md](evals/fixtures/java-dsl/README.md); local examples calibrate assets and cannot establish acceptance without project gates.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.