Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Stress Testing

  • 443 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

stress-testing is an aj-geddes/useful-ai-prompts agent skill that designs k6 and JMeter load tests for developers finding API breaking points under extreme concurrent traffic.

About

stress-testing is an aj-geddes/useful-ai-prompts Claude Code skill for capacity validation from a library of 260+ skills. It pushes systems beyond normal operating load to identify breaking points, failure modes, auto-scaling behavior, and recovery after stress. The quick-start k6 script defines progressive stages ramping from 100 to 400 virtual users over timed sustain periods with p99 latency and 5% error-rate thresholds. Six reference guides cover k6 stress testing, spike testing, soak/endurance testing, JMeter stress tests, auto-scaling validation, and breaking-point analysis. Best practices require production-like environments, gradual load increases, resource monitoring, recovery testing, and documenting limits while warning against unsafeguarded production tests. Developers reach for stress-testing before release when APIs or web services need validated saturation limits and graceful degradation plans under burst traffic.

  • Load scenario design
  • Concurrency and burst modeling
  • Breaking-point identification
  • SLO and capacity checks
  • Pre-release hardening focus

Stress Testing by the numbers

  • 443 all-time installs (skills.sh)
  • Ranked #632 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill stress-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs443
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you stress test APIs for breaking points?

Design load and stress tests before release to find breaking points, saturation limits, and failure modes under concurrent users or burst traffic on APIs and web services.

Who is it for?

Backend developers validating API capacity limits and failure modes with k6 or JMeter before a high-traffic release.

Skip if: Unit test suites or teams needing only baseline smoke tests at nominal traffic without progressive overload stages.

When should I use this skill?

APIs or web services need pre-release load tests to find saturation limits, spike handling, and recovery behavior.

What you get

k6 or JMeter stress scripts, load-stage configs, breaking-point reports, and auto-scaling validation notes

  • k6 stress scripts
  • Load stage configuration
  • Breaking-point analysis report

By the numbers

  • Includes 6 reference guides for k6, spike, soak, JMeter, auto-scaling, and breaking-point analysis
  • Quick-start k6 script ramps virtual users from 100 to 400 across staged durations
  • From useful-ai-prompts library with 260+ Claude Code skills

Files

SKILL.mdMarkdownGitHub ↗

Stress Testing

Table of Contents

Overview

Stress testing pushes systems beyond normal operating capacity to identify breaking points, failure modes, and recovery behavior. It validates system stability under extreme conditions and helps determine maximum capacity before degradation or failure.

When to Use

  • Finding system capacity limits
  • Identifying breaking points
  • Testing auto-scaling behavior
  • Validating error handling under load
  • Testing recovery after failures
  • Planning capacity requirements
  • Verifying graceful degradation
  • Testing spike traffic handling

Quick Start

Minimal working example:

// stress-test.js
import http from "k6/http";
import { check, sleep } from "k6";
import { Rate } from "k6/metrics";

const errorRate = new Rate("errors");

export const options = {
  stages: [
    // Stress testing: Progressive load increase
    { duration: "2m", target: 100 }, // Normal load
    { duration: "5m", target: 100 }, // Sustain normal
    { duration: "2m", target: 200 }, // Above normal
    { duration: "5m", target: 200 }, // Sustain above normal
    { duration: "2m", target: 300 }, // Breaking point approaching
    { duration: "5m", target: 300 }, // Sustain high load
    { duration: "2m", target: 400 }, // Beyond capacity
    { duration: "5m", target: 400 }, // System under stress
    { duration: "5m", target: 0 }, // Gradual recovery
  ],
  thresholds: {
    http_req_duration: ["p(99)<1000"], // 99% under 1s during stress
    http_req_failed: ["rate<0.05"], // Allow 5% error rate under stress
    errors: ["rate<0.1"],
  },
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
k6 Stress Testingk6 Stress Testing
Spike TestingSpike Testing
Soak/Endurance TestingSoak/Endurance Testing
JMeter Stress TestJMeter Stress Test
Auto-Scaling ValidationAuto-Scaling Validation
Breaking Point AnalysisBreaking Point Analysis

Best Practices

✅ DO

  • Test in production-like environment
  • Monitor all system resources
  • Gradually increase load to find limits
  • Test recovery after stress
  • Document breaking points
  • Test auto-scaling behavior
  • Plan for graceful degradation
  • Monitor for memory leaks

❌ DON'T

  • Test in production without safeguards
  • Skip recovery testing
  • Ignore warning signs (CPU, memory)
  • Test only success scenarios
  • Assume linear scalability
  • Forget database capacity
  • Skip monitoring third-party dependencies
  • Test without proper cleanup

Related skills

How it compares

Pick stress-testing when you need progressive overload to find breaking points, not baseline functional or unit test coverage.

FAQ

Which load tools does stress-testing document?

stress-testing documents k6 and JMeter stress scripts plus spike, soak/endurance, auto-scaling validation, and breaking-point analysis across six reference guides.

What k6 thresholds does stress-testing recommend?

stress-testing sets k6 thresholds including p99 http_req_duration under 1000ms, http_req_failed rate under 0.05, and custom error rates under 0.1 during progressive overload.

Should stress-testing run in production?

stress-testing recommends production-like staging environments with safeguards; it explicitly warns against running unsafeguarded stress tests directly against live production traffic.

Testing & QAtestingbackend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.