Load-tests a staging service against its contract SLO before launch with an open-loop, fixed-arrival-rate generator (Python standard library, no k6 or Locust install) – weighted scenarios, warm-up excluded, latency measured from the scheduled send time so stalls are not hidden (no coordinated omission), p50/p95/p99.
Load-tests a staging service against its contract SLO before launch with an open-loop, fixed-arrival-rate generator (Python standard library, no k6 or Locust install) - weighted scenarios, warm-up excluded, latency measured from the scheduled send time so stalls are not hidden (no coordinated omission), p50/p95/p99, error rate by kind, sustained throughput, a per-second timeline, and a PASS/FAIL against p95, p99 and error-rate targets; refuses any host not explicitly allowlisted. Use when someone asks "will this hold up at launch traffic", "load test staging before we ship", "does the API meet its latency SLO", "how many requests per second can this take", or as the seventh step of a production readiness review. Do NOT use against production, for soak tests longer than 15 minutes or rates above 500 rps (use k6, Locust or Gatling), or for frontend page-speed audits.This is the skill's description: the text your AI reads to decide when the skill applies.
This is the skill's header. The step-by-step instructions are paid content and aren't shown here.
staging-load-test/SKILL.md
---
name: staging-load-test
description: Load-tests a staging service against its contract SLO before launch with an open-loop, fixed-arrival-rate generator (Python standard library, no k6 or Locust install) - weighted scenarios, warm-up excluded, latency measured from the scheduled send time so stalls are not hidden (no coordinated omission), p50/p95/p99, error rate by kind, sustained throughput, a per-second timeline, and a PASS/FAIL against p95, p99 and error-rate targets; refuses any host not explicitly allowlisted. Use when someone asks "will this hold up at launch traffic", "load test staging before we ship", "does the API meet its latency SLO", "how many requests per second can this take", or as the seventh step of a production readiness review. Do NOT use against production, for soak tests longer than 15 minutes or rates above 500 rps (use k6, Locust or Gatling), or for frontend page-speed audits.
---
… the full instructions are part of a premium pack and load in your AI once you have access.