Skip to main content
configure-load-tests Load testing: k6, Artillery, Locust. Use when setting up load tests, auditing smoke/stress/spike/soak coverage, or adding CI performance regression detection.
Jump to install Skills Marketplace Discover and explore AI skills built by the community.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Show prompt details A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/laurigates/claude-plugins --skill configure-load-testsThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Download Zip Downloading... Related occupations SOC
Based on SOC occupation classification
created "2025-12-16T00:00:00.000Z" modified "2026-06-18T00:00:00.000Z" reviewed "2026-04-29T00:00:00.000Z" description Load testing: k6, Artillery, Locust. Use when setting up load tests, auditing smoke/stress/spike/soak coverage, or adding CI performance regression detection. allowed-tools Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite args [--check-only] [--fix] [--framework <k6|artillery|locust>] argument-hint [--check-only] [--fix] [--framework <k6|artillery|locust>] name configure-load-tests
/configure:load-tests
Check and configure load and performance testing infrastructure for stress testing, benchmarking, and capacity planning.
When to Use This Skill
Use this skill when... Use another approach when... Setting up load testing infrastructure from scratch (k6, Artillery, Locust) Running existing load tests — use k6 run or artillery run directly Auditing current load testing coverage (smoke, stress, spike, soak) Writing unit or integration tests — use /configure:tests Adding CI/CD pipelines for performance regression detection Profiling application memory usage — use /configure:memory-profiling Migrating between load testing frameworks Benchmarking individual functions — use language-specific benchmark tools Ensuring load test thresholds and reporting are properly configured Testing API contracts — use /configure:api-tests
Context
Project root: !pwd
k6 tests: !find . -maxdepth 3 \( -name '*.k6.js' -o -name '*.k6.ts' \)
Load test directory: !find . -maxdepth 2 -type d -name 'load'
Artillery config: !find . -maxdepth 2 -name 'artillery.yml' -o -name 'artillery.yaml'
Locust files: !find . -maxdepth 2 -name 'locustfile.py'
Package files: !find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' \)
CI workflows: !find . -path '*/.github/workflows/*' -maxdepth 3 -name '*load*' -o -name '*perf*'
k6 binary: !k6 version
Parameters
Parse from $ARGUMENTS:
--check-only: Report load testing compliance status without modifications--fix: Apply all fixes automatically without prompting--framework <k6|artillery|locust>: Override framework detection
Framework preferences:
k6 (recommended) Complex scenarios, CI/CD integration, TypeScript support
Artillery Quick YAML configs, simple API testing
Locust Python teams, distributed testing, custom behavior
Execution Execute this load testing configuration check:
Step 1: Detect existing load testing infrastructure Read the context values above and identify:
Indicator Component Status k6 binary or @grafana/k6k6 Installed *.k6.js or load-tests/k6 tests Present artillery.ymlArtillery config Present locustfile.pyLocust tests Present .github/workflows/*load*CI integration Configured
If --framework flag is set, use that framework regardless of detection.
Step 2: Analyze current load testing setup Check for complete setup coverage:
Installation: k6 installed (binary or npm), TypeScript support if applicable.
Test Scenarios: Check which test types exist:
Smoke tests (minimal load validation)
Load tests (normal load)
Stress tests (peak load)
Spike tests (burst traffic)
Soak tests (endurance)
Configuration: Thresholds, environment-specific configs, data files.
Reporting: Console output, JSON/HTML reports, trend tracking.
CI/CD: GitHub Actions workflow, scheduled runs, PR gate.
Step 3: Generate compliance report Print a compliance report covering:
Framework installation status and version
Test scenario coverage (smoke, load, stress, spike, soak)
Threshold configuration (response time, error rate)
Environment configuration (staging, production)
CI/CD integration (workflow, schedule, PR gate)
Reporting setup (console, JSON, HTML, Grafana Cloud)
End with overall issue count and recommendations.
If --check-only is set, stop here.
Step 4: Configure load testing framework (if --fix or user confirms)
Install k6 (or chosen framework)
Create directory structure: tests/load/{config,scenarios,helpers,data}
Create base configuration with shared thresholds and headers
Create test scenarios (smoke, load, stress, spike)
Add npm/package scripts for running tests
Step 5: Configure CI/CD integration
Create .github/workflows/load-tests.yml with:
Smoke tests on PRs
Full load tests via workflow_dispatch
Scheduled weekly runs
Results artifact upload
Add HTML reporting via k6-reporter
Use templates from REFERENCE.md
Step 6: Update standards tracking Update .project-standards.yaml:
components:
load_tests: "2025.1"
load_tests_framework: "k6"
load_tests_scenarios: ["smoke" , "load" , "stress" ]
load_tests_ci: true
load_tests_thresholds: true
Step 7: Print final compliance report Print a summary of framework installed, scenarios created, scripts added, CI/CD configured, thresholds set, and next steps for the user.
For detailed k6 test scripts, CI workflow templates, and reporting configuration, see REFERENCE.md .
Agentic Optimizations Context Command Quick compliance check /configure:load-tests --check-onlyAuto-fix all issues /configure:load-tests --fixRun smoke test quickly k6 run --vus 1 --duration 10s tests/load/scenarios/smoke.k6.jsRun with JSON output k6 run --out json=results.json tests/load/scenarios/load.k6.jsCheck k6 version k6 versionList test scenarios find tests/load -name '*.k6.js' -type f
Flags Flag Description --check-onlyReport status without offering fixes --fixApply all fixes automatically without prompting --framework <framework>Override framework (k6, artillery, locust)
Examples
/configure:load-tests
/configure:load-tests --check-only
/configure:load-tests --fix
/configure:load-tests --fix --framework artillery
Error Handling
k6 not installed : Provide installation instructions for platformNo target URL : Prompt for BASE_URL configurationDocker not available : Suggest local app startupCI secrets missing : Provide setup instructions for k6 Cloud
See Also More from this repository Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.
