Guides engineers and QA professionals in interpreting performance test results, identifying bottlenecks, and producing two types of reports: a technical report (for engineers and QA) and a business report (for stakeholders and executives). Use this skill whenever the user shares load test results, CSV stats, HTML reports, percentile data, or test output from k6, Gatling, Locust, JMeter, Artillery, or any other tool — and wants to understand what the numbers mean, diagnose problems, or communicate findings. Trigger on phrases like "analyze my test results", "what do these numbers mean", "my p95 is high", "error rate under load", "write a performance report", "explain the results to my manager", "how do I present this to stakeholders", or "I found a bottleneck".
Guides developers and testers in writing, fixing, and structuring Locust load test scripts in Python. Use this skill whenever the user mentions Locust, locustfile, HttpUser, TaskSet, load testing with Python, virtual users, spawn rate, wait_time, catch_response, LoadTestShape, ramp-up stages, or wants to benchmark an API or service using Locust — even if they do not explicitly say "Locust" or "load test".
Guides developers and testers in writing, fixing, and structuring k6 load test scripts using JavaScript or TypeScript. Use this skill whenever the user mentions k6, Grafana k6, load testing with JavaScript, virtual users, VUs, scenarios, executors, thresholds, checks, SharedArray, ramp-up stages, arrival rate, open/closed workload model, or wants to benchmark an API, WebSocket, or gRPC service using k6 — even if they do not explicitly say "k6" or "load test".
Guides QA engineers and performance testers in designing a complete performance testing strategy by asking the right questions and applying best practices. Use this skill whenever the user asks how to plan performance tests, which test types to run (Smoke, Load, Stress, Spike, Endurance/Soak), how to define SLAs, what metrics to collect, how to size their test, or how to sequence test execution. Trigger on phrases like "performance test plan", "load test strategy", "how many users should I use", "what kind of performance test do I need", "where do I start with performance testing", or "help me design my perf tests".
Guides developers and testers in writing, fixing, and structuring Gatling load test scenarios. Use this skill whenever the user mentions load testing, performance testing, stress testing, Gatling, virtual users, VUs, ramp-up, injection profiles, simulations, JMeter migration, k6 migration, throughput, response time SLAs, or wants to benchmark an API or service — even if they don't explicitly say 'Gatling' or 'performance test'.