/run-load-test
Run load and stress tests against API endpoints or web pages.
$ npx -y skills add rohitg00/awesome-claude-code-toolkit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/run-load-test
Context preview
What this command does when you run it.
Run load and stress tests against API endpoints or web pages.
Command definition
run-load-test.md/run-load-test - Execute Load Test
Run load and stress tests against API endpoints or web pages.
Steps
1. Ask the user for the target URL or endpoint to test 2. Determine load testing parameters: concurrent users (default 50), duration (default 60s), ramp-up period (default 10s) 3. Check if a load testing tool is installed (k6, Artillery, or autocannon); recommend k6 if none found 4. Create or locate the load test script for the target endpoint 5. Configure request headers, authentication tokens, and payload if needed 6. Execute the load test with the specified parameters 7. Monitor real-time metrics: requests/sec, latency percentiles (p50, p95, p99), error rate 8. Capture the full results including response time distribution 9. Identify performance bottlenecks: slow endpoints, high error rates, timeout patterns 10. Present results in a formatted table with pass/fail thresholds 11. Save the results to a timestamped report file
Rules
- Never run load tests against production without explicit user confirmation
- Default to a conservative load profile (50 VUs, 60s duration) unless specified
- Always include a ramp-up period to avoid sudden spikes
- Monitor system resources if testing locally (CPU, memory)
- Stop the test immediately if error rate exceeds 50%
- Include response time percentiles, not just averages
- Warn if the target appears to be a third-party service
Read more
/run-load-test - Execute Load Test
Run load and stress tests against API endpoints or web pages.
Steps
1. Ask the user for the target URL or endpoint to test 2. Determine load testing parameters: concurrent users (default 50), duration (default 60s), ramp-up period (default 10s) 3. Check if a load testing tool is installed (k6, Artillery, or autocannon); recommend k6 if none found 4. Create or locate the load test script for the target endpoint 5. Configure request headers, authentication tokens, and payload if needed 6. Execute the load test with the specified parameters 7. Monitor real-time metrics: requests/sec, latency percentiles (p50, p95, p99), error rate 8. Capture the full results including response time distribution 9. Identify performance bottlenecks: slow endpoints, high error rates, timeout patterns 10. Present results in a formatted table with pass/fail thresholds 11. Save the results to a timestamped report file
Rules
- Never run load tests against production without explicit user confirmation
- Default to a conservative load profile (50 VUs, 60s duration) unless specified
- Always include a ramp-up period to avoid sudden spikes
- Monitor system resources if testing locally (CPU, memory)
- Stop the test immediately if error rate exceeds 50%
- Include response time percentiles, not just averages
- Warn if the target appears to be a third-party service
The most comprehensive toolkit for Claude Code -- 135 agents, 35 curated skills (+400,000 via SkillKit), 42 commands, 176+ plugins, 20 hooks, 15 rules, 7 templates, 15 MCP configs, 26 companion apps, 53 ecosystem entries, and more.
Repo: rohitg00/awesome-claude-code-toolkit
Other commands on rohitg00-claude-code-toolkit.
- /adr
Write an Architecture Decision Record documenting a significant technical decision.
Open command - /design-review
Conduct a structured design review of a module, feature, or system component.
Open command - /diagram
Generate Mermaid diagrams from codebase analysis or description.
Open command - /migrate
Plan and execute a framework or library migration incrementally.
Open command - /plan
Create a structured implementation plan for the requested feature or change.
Open command - /refactor
Perform a systematic refactoring of the specified code area.
Open command

