agentsclimarketplace
Sign in

Load test planning

Skill shinzoxD/knackbox/skills/coding/load-test-planning

Plan and interpret load tests with clear goals, scenarios, and pass/fail criteria. Use whenever the user asks for k6, Locust, JMeter, Gatling, soak tests, stress tests, capacity tests, or how to read p95 latency and error rates under load.From its SKILL.md

Install
npx -y skills add shinzoxD/knackbox --skill load-test-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, 367 tokens by cl100k_base, as published. Nobody here has run it

Load Test Planning

Load tests answer a decision: can we hit this SLO under this traffic model? Vanity RPS without scenarios is noise.

Workflow

  1. Goal: launch readiness, regression, capacity, soak, or breakpoint.
  2. Model traffic: users, RPS, mix of endpoints, think time, geo if relevant.
  3. Define SLOs as pass/fail (e.g. p95 < 300ms, error rate < 0.1%).
  4. Environment: prod-like data size, caching, auth; never surprise prod without approval.
  5. Ramp plan: warm-up → steady → (optional) stress → cool-down.
  6. Observability: app metrics, infra, DB; correlate with test timeline.
  7. Interpret: bottlenecks, saturation, not only green/red.

Output format

## Load test plan: <system>

**Goal:** …
**Traffic model:** …
**Pass/fail:** …

### Scenarios
1. …

### Ramp
…

### Tooling notes
k6/Locust/…

### Observability checklist
…

### Risks / ethics
prod impact, data safety

Rules

  1. Never recommend unannounced prod stress without explicit approval.
  2. Pass criteria must match product SLOs when they exist.
  3. Distinguish average vs tail latency.
  4. Include auth and realistic payloads; GETs-only is usually wrong.
  5. Document data setup and teardown.
  6. Do not invent tool syntax you are unsure of — describe intent.

Edge cases

  • Soak: memory leaks, connection pool exhaustion over hours.
  • Spike: sudden 10x; autoscaling lag.
  • Write-heavy: idempotency and cleanup.

What ships with it: 1 file

1.3 KB alongside SKILL.md

benchmarks/

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.