load-testing

Generates k6 load, stress, spike, and soak test scripts with thresholds derived from spec NFR targets.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill load-testing-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: load-testing
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/load-testing
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill load-testing-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Performance NFRs in a spec are unverified claims until a load test enforces them. This Skill turns latency, throughput, and availability targets into executable k6 tests with CI gates, so a p99 or error-rate breach fails the pipeline instead of reaching production. ## Core Features & Use Cases - NFR-aligned k6 script generation: Produces smoke, load, stress, spike, and soak test templates whose thresholds are pulled directly from the spec NFR table and SLO documents. - CI performance gates: Adds GitHub Actions jobs that run smoke tests on every PR and full load tests against staging after deployment, with non-zero exit on threshold breach. - Baseline reporting and review: Generates a performance baseline report comparing NFR targets to measured p95/p99 results, then dispatches a load-test-reviewer agent before committing. - Use Case: A spec states "p99 < 200ms at 500 RPS with 99.9% availability." Use this Skill to generate a k6 suite that runs at 500 RPS, fails CI when p99 exceeds 200ms, and adds a 2-hour soak test for the availability target. ## Quick Start Ask the AI to generate k6 load tests with thresholds matching the NFR targets in the current feature spec and wire them into the CI pipeline.

Frequently Asked Questions about load-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a k6 load test with thresholds?

Define an options object with scenarios (constant-vus or ramping-vus) and a thresholds block mapping metrics to SLO conditions, such as 'http_req_duration': ['p(99)<200']. k6 exits non-zero when a threshold is breached, which fails the CI job.

k6 vs Locust vs Gatling for API load testing?

k6 is JavaScript-based, CLI-first, and Docker-friendly with native threshold gates, making it the default for CI pipelines. Locust suits Python teams needing custom protocols, and Gatling fits Scala/Java teams wanting stakeholder-readable HTML reports.

How do I run k6 load tests in GitHub Actions?

Install k6 via the official apt repository in a job that runs after the staging deploy step, then execute k6 run with BASE_URL pointing at staging. Run a fast smoke scenario on every PR and the full load scenario only after deployment.

When should I use a soak test instead of a load test?

Use a soak test when the spec has availability NFRs of 99.9% or higher. It holds target load for 2-8 hours to reveal memory leaks, connection pool exhaustion, and thread drift that short load tests cannot detect.

When should I skip load testing for a feature?

Skip load testing when the spec has no NFR section, the change is internal-only, a bug fix, or a utility function with no user-facing load. Confirm the skip explicitly in case an NFR was overlooked.