메뉴
Load testing: k6, Artillery, Locust. Use when setting up load tests, auditing smoke/stress/spike/soak coverage, or adding CI performance regression detection.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/laurigates/claude-plugins --skill configure-load-tests명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
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.
SKILL.md 표시 중
SOC 직업 분류 기준
| 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 |
Check and configure load and performance testing infrastructure for stress testing, benchmarking, and capacity planning.
| 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 |
pwdfind . -maxdepth 3 \( -name '*.k6.js' -o -name '*.k6.ts' \)find . -maxdepth 2 -type d -name 'load'find . -maxdepth 2 -name 'artillery.yml' -o -name 'artillery.yaml'find . -maxdepth 2 -name 'locustfile.py'find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' \)find . -path '*/.github/workflows/*' -maxdepth 3 -name '*load*' -o -name '*perf*'k6 versionParse from $ARGUMENTS:
--check-only: Report load testing compliance status without modifications--fix: Apply all fixes automatically without prompting--framework <k6|artillery|locust>: Override framework detectionFramework preferences:
| Framework | Best For |
|---|
| k6 (recommended) | Complex scenarios, CI/CD integration, TypeScript support |
| Artillery | Quick YAML configs, simple API testing |
| Locust | Python teams, distributed testing, custom behavior |
Execute this load testing configuration check:
Read the context values above and identify:
| Indicator | Component | Status |
|---|---|---|
k6 binary or @grafana/k6 | k6 | Installed |
*.k6.js or load-tests/ | k6 tests | Present |
artillery.yml | Artillery config | Present |
locustfile.py | Locust tests | Present |
.github/workflows/*load* | CI integration | Configured |
If --framework flag is set, use that framework regardless of detection.
Check for complete setup coverage:
Installation: k6 installed (binary or npm), TypeScript support if applicable.
Test Scenarios: Check which test types exist:
Configuration: Thresholds, environment-specific configs, data files.
Reporting: Console output, JSON/HTML reports, trend tracking.
CI/CD: GitHub Actions workflow, scheduled runs, PR gate.
Print a compliance report covering:
End with overall issue count and recommendations.
If --check-only is set, stop here.
Apply configuration using templates from REFERENCE.md:
tests/load/{config,scenarios,helpers,data}.github/workflows/load-tests.yml with:
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
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.
| Context | Command |
|---|---|
| Quick compliance check | /configure:load-tests --check-only |
| Auto-fix all issues | /configure:load-tests --fix |
| Run smoke test quickly | k6 run --vus 1 --duration 10s tests/load/scenarios/smoke.k6.js |
| Run with JSON output | k6 run --out json=results.json tests/load/scenarios/load.k6.js |
| Check k6 version | k6 version |
| List test scenarios | find tests/load -name '*.k6.js' -type f |
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply all fixes automatically without prompting |
--framework <framework> | Override framework (k6, artillery, locust) |
# Check compliance and offer fixes
/configure:load-tests
# Check only, no modifications
/configure:load-tests --check-only
# Auto-fix all issues
/configure:load-tests --fix
# Force specific framework
/configure:load-tests --fix --framework artillery
/configure:tests - Unit testing configuration/configure:integration-tests - Integration testing/configure:api-tests - API contract testing/configure:all - Run all compliance checks