Agent skill

Load Testing Patterns

by vibeeval in vibeeval/vibecosystem

k6 script templates, load profiles, response time thresholds, SLO validation, and performance testing strategies.

MITAuto-check passedTesting & QA

Install Load Testing Patterns

skills CLI
$ npx skills add vibeeval/vibecosystem --skill load-testing-patterns -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vibeeval/vibecosystem load-testing-patterns --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/load-testing-patterns .claude/skills/load-testing-patterns && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
load-testing-patterns
GitHub stars
531
Token cost
~1.6k tokens
SKILL.md length
148 words
Files
1
Skills in repo
144
Repo updated
First seen
Licence
MIT

At a glance

k6 script templates, load profiles, response time thresholds, SLO validation, and performance testing strategies.

  • Tasks that involve Load testing
  • SKILL.md covers Basic k6 Script Template, Load Profiles, Realistic User Scenarios and SLO Validation, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Site reliability engineering

What it does

Load Testing Patterns is an agent skill from vibeeval/vibecosystem. k6 script templates, load profiles, response time thresholds, SLO validation, and performance testing strategies.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Load testing and Site reliability engineering. The repository describes itself as: AI software team for Claude Code - 138 agents, 295 skills, 73 hooks. Self-learning, multi-agent swarm, autonomous skill evolution. The licence is MIT.

When your agent uses it

  • Tasks that involve Load testing
  • Tasks that involve Site reliability engineering

Example prompts

  • “/load-testing-patterns”

What it can do on your machine

Read from SKILL.md and the folder at commit 3b763b1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Load Testing Patterns loads about 1.6k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 148 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~34
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vibeeval/vibecosystem at commit 3b763b1, republished under its MIT licence (© vibeeval). 148 words, ~1,644 tokens.

Download SKILL.mdSave it as .claude/skills/load-testing-patterns/SKILL.md (or your agent's skills folder).
name
load-testing-patterns
description
k6 script templates, load profiles, response time thresholds, SLO validation, and performance testing strategies.

Load Testing Patterns

Performance validation with k6 for SLO-driven load testing.

Basic k6 Script Template

javascript
import http from 'k6/http'
import { check, sleep } from 'k6'
import { Rate, Trend } from 'k6/metrics'

// Custom metrics
const errorRate = new Rate('errors')
const loginDuration = new Trend('login_duration')

// Thresholds define pass/fail criteria
export const options = {
  thresholds: {
    http_req_duration: ['p(95)<500', 'p(99)<1000'],  // 95th < 500ms, 99th < 1s
    http_req_failed: ['rate<0.01'],                    // Error rate < 1%
    errors: ['rate<0.05'],                             // Custom error rate < 5%
  },
  scenarios: {
    smoke: {
      executor: 'constant-vus',
      vus: 5,
      duration: '1m',
    }
  }
}

export default function () {
  const res = http.get('https://api.example.com/health')

  check(res, {
    'status is 200': (r) => r.status === 200,
    'response time < 500ms': (r) => r.timings.duration < 500,
    'body has status': (r) => JSON.parse(r.body).status === 'ok',
  }) || errorRate.add(1)

  sleep(1)
}

Load Profiles

javascript
export const options = {
  scenarios: {
    // 1. Smoke Test: verify system works under minimal load
    smoke: {
      executor: 'constant-vus',
      vus: 3,
      duration: '1m',
    },

    // 2. Load Test: normal expected traffic
    load: {
      executor: 'ramping-vus',
      startVUs: 0,
      stages: [
        { duration: '2m', target: 50 },   // Ramp up
        { duration: '5m', target: 50 },   // Steady state
        { duration: '2m', target: 0 },    // Ramp down
      ],
    },

    // 3. Stress Test: find breaking point
    stress: {
      executor: 'ramping-vus',
      startVUs: 0,
      stages: [
        { duration: '2m', target: 100 },
        { duration: '5m', target: 100 },
        { duration: '2m', target: 200 },  // Beyond normal
        { duration: '5m', target: 200 },
        { duration: '2m', target: 300 },  // Breaking point?
        { duration: '5m', target: 300 },
        { duration: '5m', target: 0 },
      ],
    },

    // 4. Spike Test: sudden traffic surge
    spike: {
      executor: 'ramping-vus',
      startVUs: 0,
      stages: [
        { duration: '30s', target: 10 },
        { duration: '10s', target: 500 },  // Instant spike
        { duration: '1m', target: 500 },
        { duration: '10s', target: 10 },   // Instant drop
        { duration: '1m', target: 10 },
      ],
    },

    // 5. Soak Test: sustained load over time (memory leaks, connection exhaustion)
    soak: {
      executor: 'constant-vus',
      vus: 50,
      duration: '2h',
    },
  }
}

Realistic User Scenarios

javascript
import http from 'k6/http'
import { check, group, sleep } from 'k6'

const BASE_URL = __ENV.BASE_URL || 'https://api.example.com'

export default function () {
  // Simulate real user journey, not isolated endpoints
  let token

  group('01_login', () => {
    const res = http.post(`${BASE_URL}/auth/login`, JSON.stringify({
      email: `user${__VU}@test.com`,
      password: 'testpass123'
    }), { headers: { 'Content-Type': 'application/json' } })

    check(res, { 'login successful': (r) => r.status === 200 })
    token = JSON.parse(res.body).token
  })

  sleep(Math.random() * 3 + 1)  // Think time: 1-4 seconds

  group('02_browse_products', () => {
    const headers = { Authorization: `Bearer ${token}` }

    const listRes = http.get(`${BASE_URL}/products?page=1&limit=20`, { headers })
    check(listRes, { 'products loaded': (r) => r.status === 200 })

    const products = JSON.parse(listRes.body).data
    if (products.length > 0) {
      const product = products[Math.floor(Math.random() * products.length)]
      const detailRes = http.get(`${BASE_URL}/products/${product.id}`, { headers })
      check(detailRes, { 'product detail loaded': (r) => r.status === 200 })
    }
  })

  sleep(Math.random() * 2 + 1)

  group('03_add_to_cart', () => {
    const res = http.post(`${BASE_URL}/cart/items`, JSON.stringify({
      productId: 'prod_001',
      quantity: 1
    }), {
      headers: {
        'Content-Type': 'application/json',
        Authorization: `Bearer ${token}`
      }
    })
    check(res, { 'item added to cart': (r) => r.status === 201 })
  })
}

SLO Validation

javascript
export const options = {
  thresholds: {
    // SLO: Availability > 99.9%
    http_req_failed: ['rate<0.001'],

    // SLO: p50 < 100ms, p95 < 500ms, p99 < 1000ms
    http_req_duration: [
      'p(50)<100',
      'p(95)<500',
      'p(99)<1000',
    ],

    // SLO per endpoint using tags
    'http_req_duration{name:login}': ['p(95)<800'],
    'http_req_duration{name:get_products}': ['p(95)<200'],
    'http_req_duration{name:checkout}': ['p(95)<2000'],

    // SLO: Throughput > 1000 RPS
    http_reqs: ['rate>1000'],
  }
}

// Tag requests for per-endpoint SLOs
export default function () {
  http.get(`${BASE_URL}/products`, { tags: { name: 'get_products' } })
  http.post(`${BASE_URL}/auth/login`, payload, { tags: { name: 'login' } })
}

CI Integration

yaml
# .github/workflows/load-test.yml
name: Load Test
on:
  pull_request:
    branches: [main]

jobs:
  load-test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: grafana/k6-action@v0.3.1
        with:
          filename: tests/load/smoke.js
        env:
          BASE_URL: ${{ secrets.STAGING_URL }}

      # k6 exits non-zero if thresholds fail → PR check fails

Checklist

  • Run smoke test on every PR (fast, catches regressions)
  • Load test weekly against staging with production-like data
  • Stress test quarterly to find breaking points
  • Soak test before major releases (2+ hours, detect memory leaks)
  • Thresholds set per endpoint, not just global p95
  • Realistic think times between requests (sleep 1-5s)
  • Use multiple VU scenarios (not everyone does the same thing)
  • Store results in Grafana/InfluxDB for trend analysis

Anti-Patterns

  • Testing only happy paths: include error scenarios (404, 429, 500)
  • No think time: unrealistic request rate, not how users behave
  • Testing against production without traffic control (use staging)
  • Single endpoint tests: real users hit multiple endpoints per session
  • Ignoring connection time: p95 duration hides DNS/TLS overhead
  • Hardcoded test data: VUs sharing same user account causes contention

© vibeeval, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/load-testing-patterns of vibeeval/vibecosystem.

Open the folder on GitHubat commit 3b763b1

Compare with similar skills

Load Testing Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Load Testing Patterns compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Load Testing Patterns this skillvibeeval/vibecosystem531—~1.6kAutomated safety check: PassMIT
Performance Testingkid-sid/claude-spellbook189—~2.5kAutomated safety check: PassMIT
Capacity PlannerFerroxLabs/wayland608—~4.4kAutomated safety check: PassApache-2.0
Performance EngineerFerroxLabs/wayland608—~5.1kAutomated safety check: PassApache-2.0
HTTP Load Profilerzebbern/claude-code-guide4.6k—~1.6kAutomated safety check: NotesMIT
Performance Engineeringancoleman/ai-design-components526—~2.9kAutomated safety check: NotesMIT

Similar skills

  • Performance Testing

    kid-sid/claude-spellbook

    A skill your agent uses when load testing a service before launch or after a significant traffic change — writing k6 or Locust scripts, setting SLO-based pass/fail thresholds, diagnosing bottlenecks…

    189 GitHub stars~2.5k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Capacity Planner

    FerroxLabs/wayland

    Capacity planning expertise covering load testing methodologies, autoscaling policies, resource forecasting, performance budgets, cost-capacity curves, bottleneck identification, queue theory…

    608 GitHub stars~4.4k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Performance Engineer

    FerroxLabs/wayland

    Becomes a senior performance engineer who identifies bottlenecks, designs optimization strategies, and conducts load testing using systematic profiling and benchmarking methodology.

    608 GitHub stars~5.1k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • HTTP Load Profiler

    zebbern/claude-code-guide

    Run stepped HTTP load tests with ab/wrk, ramping concurrency levels to collect p50/p90/p99 latency, detect performance inflection points, and recommend optimal concurrency.

    4.6k GitHub stars~1.6k tokensUpdated today
    Testing & QAAuto-check: notes
  • Performance Engineering

    ancoleman/ai-design-components

    When validating system performance under load, identifying bottlenecks through profiling, or optimizing application responsiveness.

    526 GitHub stars~2.9k tokensUpdated 10 mo ago
    Testing & QAAuto-check: notes
  • Afrexai Performance Engineering

    LeoYeAI/openclaw-master-skills

    Complete performance engineering system — profiling, optimization, load testing, capacity planning, and performance culture.

    2.2k GitHub stars~7.1k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

More from vibeeval/vibecosystem

All 144 skills in this repo
  • Agent Benchmark

    vibeeval/vibecosystem

    Framework for measuring and tracking agent response quality over time.

    531 GitHub stars~2.9k tokensUpdated 2 mo ago
    Auto-check passed
  • Differential Review

    vibeeval/vibecosystem

    Security-focused differential code review with blast radius analysis, risk-adaptive depth (DEEP/FOCUSED/SURGICAL), git history correlation, and structured finding format.

    531 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed
  • Factcheck Guard

    vibeeval/vibecosystem

    A skill your agent uses when making any factual claim about the codebase — existence, absence, or behavior.

    531 GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Fp Check

    vibeeval/vibecosystem

    Systematic false positive verification for security findings.

    531 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed
  • N8n Workflows

    vibeeval/vibecosystem

    n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.

    531 GitHub stars~3.3k tokensUpdated 2 mo ago
    Auto-check passed
  • Notepad System

    vibeeval/vibecosystem

    A skill your agent uses when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks.

    531 GitHub stars~1.7k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Load Testing Patterns

What does Load Testing Patterns do?

k6 script templates, load profiles, response time thresholds, SLO validation, and performance testing strategies. Load Testing Patterns is an agent skill from vibeeval/vibecosystem. k6 script templates, load profiles, response time thresholds, SLO validation, and performance testing strategies.

When should I use Load Testing Patterns?

Load Testing Patterns fits situations like: tasks that involve Load testing; tasks that involve Site reliability engineering.

How do I install Load Testing Patterns in Claude Code?

Run `npx skills add vibeeval/vibecosystem --skill load-testing-patterns -a claude-code`. Or copy the skill folder (skills/load-testing-patterns in vibeeval/vibecosystem) into .claude/skills/load-testing-patterns in your project. Claude Code loads it when a task matches its description.

How do I install Load Testing Patterns in Codex?

Run `npx skills add vibeeval/vibecosystem --skill load-testing-patterns -a codex`. Or copy the skill folder (skills/load-testing-patterns in vibeeval/vibecosystem) into .agents/skills/load-testing-patterns in your project. Codex loads it when a task matches its description.

Can I use Load Testing Patterns in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vibeeval/vibecosystem --skill load-testing-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/load-testing-patterns, .gemini/skills/load-testing-patterns, .github/skills/load-testing-patterns and .opencode/skills/load-testing-patterns in your project.

What does Load Testing Patterns need to run?

SKILL.md names no scripts, command-line tools or credentials: Load Testing Patterns is instructions for the agent only.

Does Load Testing Patterns access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Load Testing Patterns safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Load Testing Patterns use?

Load Testing Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Load Testing Patterns use?

About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Load Testing Patterns?

Skills that share tags, products or a category with Load Testing Patterns: Performance Testing (kid-sid/claude-spellbook, 189 stars), Capacity Planner (FerroxLabs/wayland, 608 stars), Performance Engineer (FerroxLabs/wayland, 608 stars) and HTTP Load Profiler (zebbern/claude-code-guide, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Load Testing Patterns?

vibeeval (a GitHub user) maintains it in vibeeval/vibecosystem, which has 531 GitHub stars. The repository holds 144 skills in this directory. The repository was last updated on August 8, 2026.

Source: vibeeval/vibecosystem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.