performance-test-gatling
Provide Gatling performance scope, reusable simulations, and runnable entry points.
Best use case
performance-test-gatling is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Provide Gatling performance scope, reusable simulations, and runnable entry points.
Teams using performance-test-gatling should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/performance-test-gatling/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How performance-test-gatling Compares
| Feature / Agent | performance-test-gatling | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Provide Gatling performance scope, reusable simulations, and runnable entry points.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# performance-test-gatling (EN) **中文版：** 见对应中文技能。 ## When to Use - Need performance outputs that should land in Gatling structure. - The project already uses Gatling or wants Gatling-ready scenarios. ## Output Format Options Markdown by default unless the request explicitly asks for another format. ## How to Use 1. Open `prompts/performance-test-gatling.md` and use it as the main prompt. 2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable. 3. If the input is incomplete, return a usable first version and mark missing information and assumptions. ## Reference Files - `prompts/performance-test-gatling.md`: main prompt for this skill. - `references/`: supporting notes loaded only when needed. - `examples/`: sample inputs or outputs. - `scripts/`: helper scripts or converters for this skill. ## Common Pitfalls - Do not use it with vague scope and no context. - Do not treat every area as equally important. - Do not skip assumptions and missing information. ## Best Practices - Start from the prompt file, then add only the context that matters. - Keep the output risk-driven and executable. - If the request is incomplete, return a usable first version and mark gaps.
Related Skills
sprint-testing-workflow
Use this skill when you need a sprint-based QA workflow from planning through review and retrospective; triggers include sprint testing workflow and sprint QA flow.
release-testing-workflow
Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and release readiness testing.
discover-testing
Use this skill when you need to quickly route a request to the best testing-type or testing-workflow skill.
daily-testing-workflow
Use this skill when you need a day-by-day QA routine including planning, execution, bug reporting, and end-of-day wrap-up; triggers include daily testing workflow and daily QA routine.
testcase-writer-plus
Parse requirement and analysis files, then generate high-quality test cases.
test-strategy
Use this skill when you need to define a test strategy covering scope, methods, resources, risks, and quality gates; triggers include test strategy and QA planning.
test-strategy-plus
Generate a structured test strategy from requirement, analysis, technical, and plan documents.
test-reporting
Use this skill when you need to generate test reports with summary, metrics, defect analysis, and risk assessment; triggers include test reporting and QA status report.
test-case-writing
Use this skill when you need to create high-quality test cases with normal, exception, and boundary scenarios; triggers include test case writing and test design.
test-case-reviewer
Use this skill when you need to review test cases for completeness, clarity, maintainability, and missing scenarios; triggers include test case review and test case QA.
test-case-reviewer-plus
Review test cases using requirement, strategy, and supporting documents, then output structured findings.
security-testing
Use this skill when you need to design security testing around OWASP risks, vulnerability scanning, and penetration scenarios; triggers include security testing and vulnerability testing.