skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
naodeng/awesome-qa-skills77 installs

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.

How do I install this agent skill?

npx skills add https://github.com/naodeng/awesome-qa-skills --skill performance-test-gatling
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is a well-structured performance testing framework for Gatling. It follows security best practices by instructing the agent to use placeholders for sensitive information and uses trusted sources for its external dependencies.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

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.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/naodeng/awesome-qa-skills/performance-test-gatling">View performance-test-gatling on skillZs</a>