> artillery
When the user wants to perform load testing or performance testing using Artillery with YAML-based scenario definitions. Also use when the user mentions "artillery," "YAML load test," "WebSocket testing," "Socket.io load test," "scenario-based load testing," or "artillery run." For JavaScript-based load testing, see k6.
curl "https://skillshub.wtf/TerminalSkills/skills/artillery?format=md"Artillery
Overview
You are an expert in Artillery, the modern load testing toolkit. You help users define test scenarios in YAML, configure phases for ramping traffic, test HTTP APIs and WebSocket/Socket.io services, write custom JavaScript functions for complex flows, and generate HTML reports. You understand Artillery's plugin ecosystem and CI integration.
Instructions
Initial Assessment
Before creating a test scenario:
- Protocol — HTTP, WebSocket, Socket.io, or gRPC?
- Flow — Single endpoint or multi-step user journey?
- Load profile — Constant rate, ramp-up, or phased?
- Success criteria — Acceptable latency, error rate?
Basic HTTP Load Test
# load-test.yml — Artillery scenario testing an HTTP API.
# Ramps from 5 to 50 requests per second over 3 phases.
config:
target: "https://api.example.com"
phases:
- duration: 60
arrivalRate: 5
name: "Warm up"
- duration: 120
arrivalRate: 25
name: "Ramp up"
- duration: 60
arrivalRate: 50
name: "Peak load"
defaults:
headers:
Content-Type: "application/json"
scenarios:
- name: "Browse and purchase"
flow:
- get:
url: "/products"
capture:
- json: "$.products[0].id"
as: "productId"
- think: 2
- get:
url: "/products/{{ productId }}"
- think: 1
- post:
url: "/cart"
json:
productId: "{{ productId }}"
quantity: 1
WebSocket Testing
# websocket-test.yml — Artillery scenario testing a WebSocket server.
# Connects, sends messages, and validates responses.
config:
target: "wss://ws.example.com"
phases:
- duration: 60
arrivalRate: 10
engines:
ws: {}
scenarios:
- engine: "ws"
flow:
- send:
payload: '{"type": "subscribe", "channel": "updates"}'
- think: 1
- send:
payload: '{"type": "message", "text": "hello"}'
- think: 5
Socket.io Testing
# socketio-test.yml — Artillery scenario for Socket.io real-time apps.
# Simulates users joining rooms and exchanging messages.
config:
target: "http://localhost:3000"
phases:
- duration: 60
arrivalRate: 20
engines:
socketio:
transports: ["websocket"]
scenarios:
- engine: "socketio"
flow:
- emit:
channel: "join"
data:
room: "general"
username: "user_{{ $randomNumber(1, 1000) }}"
- think: 2
- emit:
channel: "message"
data:
text: "Hello from Artillery"
- think: 3
Custom JavaScript Functions
# custom-flow.yml — Artillery scenario with custom JS processing.
# Uses beforeRequest and afterResponse hooks for dynamic data.
config:
target: "https://api.example.com"
phases:
- duration: 120
arrivalRate: 10
processor: "./helpers.js"
scenarios:
- flow:
- function: "generateUser"
- post:
url: "/users"
json:
name: "{{ name }}"
email: "{{ email }}"
beforeRequest: "addAuthToken"
afterResponse: "logResponse"
// helpers.js — Custom Artillery processor functions.
// Generates dynamic data and handles auth tokens.
module.exports = {
generateUser(context, events, done) {
context.vars.name = `user_${Date.now()}`;
context.vars.email = `user_${Date.now()}@test.com`;
return done();
},
addAuthToken(req, context, events, done) {
req.headers = req.headers || {};
req.headers['Authorization'] = `Bearer ${context.vars.token || 'test-token'}`;
return done();
},
logResponse(req, res, context, events, done) {
if (res.statusCode !== 200) {
console.log(`Error: ${res.statusCode} on ${req.url}`);
}
return done();
},
};
Running Artillery
# run-artillery.sh — Common Artillery commands.
# Install, run tests, and generate reports.
# Install
npm install -g artillery
# Run a test
artillery run load-test.yml
# Generate HTML report
artillery run --output results.json load-test.yml
artillery report results.json --output report.html
# Quick test (no YAML needed)
artillery quick --count 100 --num 10 https://api.example.com/health
CI Integration
# .github/workflows/artillery.yml — Run Artillery in GitHub Actions.
# Posts HTML report as an artifact.
name: Load Test
on:
push:
branches: [main]
jobs:
artillery:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 20
- run: npm install -g artillery
- run: artillery run --output results.json tests/load-test.yml
- run: artillery report results.json --output report.html
- uses: actions/upload-artifact@v4
if: always()
with:
name: artillery-report
path: report.html
> related_skills --same-repo
> zustand
You are an expert in Zustand, the small, fast, and scalable state management library for React. You help developers manage global state without boilerplate using Zustand's hook-based stores, selectors for performance, middleware (persist, devtools, immer), computed values, and async actions — replacing Redux complexity with a simple, un-opinionated API in under 1KB.
> zoho
Integrate and automate Zoho products. Use when a user asks to work with Zoho CRM, Zoho Books, Zoho Desk, Zoho Projects, Zoho Mail, or Zoho Creator, build custom integrations via Zoho APIs, automate workflows with Deluge scripting, sync data between Zoho apps and external systems, manage leads and deals, automate invoicing, build custom Zoho Creator apps, set up webhooks, or manage Zoho organization settings. Covers Zoho CRM, Books, Desk, Projects, Creator, and cross-product integrations.
> zod
You are an expert in Zod, the TypeScript-first schema declaration and validation library. You help developers define schemas that validate data at runtime AND infer TypeScript types at compile time — eliminating the need to write types and validators separately. Used for API input validation, form validation, environment variables, config files, and any data boundary.
> zipkin
Deploy and configure Zipkin for distributed tracing and request flow visualization. Use when a user needs to set up trace collection, instrument Java/Spring or other services with Zipkin, analyze service dependencies, or configure storage backends for trace data.