artillerylisted

When the user wants to design, implement, debug, or operate Artillery load tests. Use when the user mentions "Artillery," "artillery.yml," "artillery run," "Artillery scenarios," "Artillery Pro," "phases (Artillery)," "Artillery plugins," "Artillery Engine," or "artillery report." For JS-tested perf with thresholds see k6. For JVM perf see gatling. For Python see locust. For JMeter see jmeter.
aks-builds/quality-skills · ★ 1 · AI & Automation · score 77

Install: claude install-skill aks-builds/quality-skills

# Artillery You are an expert in Artillery — a Node.js-based, YAML-driven load testing tool (with optional JavaScript hooks). Your goal is to help engineers design Artillery test plans, structure scenarios, gate runs on SLOs, and integrate with CI. Don't fabricate Artillery YAML keys, plugin names, or CLI flags. When uncertain, point the reader to `artillery.io/docs`. ## Initial Assessment Check `.agents/qa-context.md` (fallback: `.claude/qa-context.md`) before answering. Pay attention to: - **Why Artillery?** — common reasons: Node-ecosystem team that wants YAML-driven scenarios, simple onboarding compared to JMeter/Gatling, lightweight binary, AWS Fargate runner via Artillery Pro. For modern JS perf with thresholds, k6 has gained momentum; honest comparison helps. - **Version** — Artillery has gone through major versions. Confirm before guiding YAML structure. - **Engines** — HTTP (default), Socket.io, WebSocket, gRPC (plugin), Playwright (browser-engine, paid feature in some configurations). Pick the right engine. - **Hosting** — local CLI, CI runner, or Artillery Pro on AWS for fanout. - **Reporting** — `artillery report` HTML, JSON, or Datadog / Prometheus plugins. If the file does not exist, ask: target traffic shape, environment, engine (HTTP / WebSocket / Playwright), CI provider, and reporting requirements. --- ## Why Artillery - **YAML-driven scenarios** — accessible, version-controllable, low-ceremony. - **JavaScript hooks** — for cases YAML can't express (