load-testing
/load-testing
Load testing with k6: script with stages (ramp-up/hold/ramp-down), thresholds (p99<500ms, errors<1%), spike test for finding breaking point, k6 in CI with failure on thresholds, soak testing, Locust for Python teams, common bottleneck patterns. Use when verifying performance, finding capacity limits, load testing before launch.
- Author
- rnavarych ↗
- Repository
- alpha-engineer ↗
- Licence
- MIT
- Last repository change
- 24.07.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/quick-load-test.sh
What it does and when to use it
Load testing with k6: script with stages (ramp-up/hold/ramp-down), thresholds (p99<500ms, errors<1%), spike test for finding breaking point, k6 in CI with failure on thresholds, soak testing, Locust for Python teams, common bottleneck patterns. Use when verifying performance, finding capacity limits, load testing before launch.
Original author description
Load testing with k6: script with stages (ramp-up/hold/ramp-down), thresholds (p99<500ms, errors<1%), spike test for finding breaking point, k6 in CI with failure on thresholds, soak testing, Locust for Python teams, common bottleneck patterns. Use when verifying performance, finding capacity limits, load testing before launch.
How it works
- When to use
- Core principles
- References available
SKILL.md preview
--- name: load-testing description: | Load testing with k6: script with stages (ramp-up/hold/ramp-down), thresholds (p99<500ms, errors<1%), spike test for finding breaking point, k6 in CI with failure on thresholds, soak testing, Locust for Python teams, common bottleneck patterns. Use when verifying performance, finding capacity limits, load testing before launch. allowed-tools: Read, Grep, Glob --- # Load Testing ## When to use - Verifying performance before a product launch - Finding capacity limits and breaking points - Setting up performance regression in CI - Diagnosing under which load specific endpoints degrade - Comparing performance before and after optimization ## Core principles 1. **Test in production-like environment** — load test results from dev are meaningless 2. **Warm up before measuring** — cold start skews results 3. **Define thresholds before running** — not after seeing results 4. **Soak testing finds leaks** — sustained load reveals memory leaks and connection exhaustion 5. **Watch the database, not just the app** — DB is usually the bottleneck ## References available - `references/k6-script.md` — stages config, custom metrics, thresholds, setup function, think time - `references/spike-test.md` — sudden VU spike pattern, relaxed thresholds, recovery measurement - `references/ci-integration.md` — GitHub Actions k6-action, nightly schedule, threshold exit codes - `references/observing-load.md` — pg_stat_statements during test, DB connection monitoring, Grafana RED - `references/threshold-reference.md` — p95/p99 targets by endpoint type, error rate budgets by load level
Files in this package (5)
- SKILL.md 2 KB
- references/artillery-patterns.md 3 KB
- references/k6-patterns.md 3 KB
- references/performance-baselines.md 2 KB
- scripts/quick-load-test.sh 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · rnavarych/alpha-engineer | 100 | MIT |
| claude-dev-suite/claude-dev-suite | 100 | MIT |
| SkillMedev/skills | 100 | MIT |
| ajyadav013/claude-kit | 100 | MIT |
| ajyadav013/claude-kit | 100 | MIT |
| VilnaCRM-Org/rust-service-template | 96 | CC0-1.0 |
| OKHP3/skillz | 90 | MIT |
| Amey-Thakur/AI-SKILLS | 90 | MIT |
| arjunprabhulal/devops-skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version 4edc43ddeb89 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100load-test
Load testing setup, execution, and analysis with k6, Artillery, or Locust. Generates test scripts, defines VU ramp-up scenarios, interprets p99 latency and error rate results, and suggests infrastructure fixes. Use when user wants to load test an API, check throughput limits,… - 100capacity-planning-and-load-testing
Guides demand forecasting and load/stress/soak testing methodology (using tools such as k6, Locust, or JMeter) to find a system's real bottleneck — CPU, memory, a connection pool, or a downstream dependency — before production traffic finds it, and to set autoscaling/capacity… - 100performance-testing
Use when load testing a system. Covers workload modeling, ramp profiles, what to measure, finding the breaking point, and distinguishing a real bottleneck from a badly configured test. Trigger on "load test this api", "how many users can we handle", "write a k6 script", "find… - 100k6-and-locust-load-testing
Production-grade load, stress, spike, and endurance testing using Grafana k6 and Python Locust. Use when designing performance test suites, defining SLAs/SLOs, simulating distributed user traffic, and automating performance regression gates in CI/CD pipelines. - 90backend-load-testing
Use this skill when the user says 'load test', 'stress test', 'soak test', 'spike test', 'k6', 'Locust', 'Artillery', 'performance test', 'benchmark', 'throughput', 'RPS', 'latency p99', 'CI performance', 'regression test', 'load test results', or when planning performance… - 100performance-testing
Use when load testing a service before launch or after a significant traffic change — writing k6 or Locust scripts, setting SLO-based pass/fail thresholds, diagnosing bottlenecks under load, or integrating performance tests into CI.