From billy-milligan
Guides load testing with k6 (stages, thresholds, spike/soak tests, CI integration via GitHub Actions) and Locust for Python teams. Use for verifying performance, finding capacity limits before launch.
How this skill is triggered — by the user, by Claude, or both
Slash command
/billy-milligan:load-testingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Verifying performance before a product launch
references/k6-script.md — stages config, custom metrics, thresholds, setup function, think timereferences/spike-test.md — sudden VU spike pattern, relaxed thresholds, recovery measurementreferences/ci-integration.md — GitHub Actions k6-action, nightly schedule, threshold exit codesreferences/observing-load.md — pg_stat_statements during test, DB connection monitoring, Grafana REDreferences/threshold-reference.md — p95/p99 targets by endpoint type, error rate budgets by load levelnpx claudepluginhub rnavarych/alpha-engineer --plugin billy-milliganCreates and runs load tests with k6, JMeter, and Artillery for web apps and APIs. Validates performance under stress, spike, soak, scalability to detect bottlenecks.
Stress tests, capacity plans, and performance benchmarks with k6, Artillery, and Gatling. Detects existing load test infrastructure, designs scenarios, executes tests, and analyzes results against thresholds.
Checks and configures load and performance testing infrastructure with k6, Artillery, or Locust. Audits coverage for smoke/stress tests, sets up CI/CD pipelines, and supports framework migration.