playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / artillery-config-generator

artillery-config-generator skill

/skills/10-performance-testing/artillery-config-generator

This skill helps you generate production-ready artillery config and validation for performance testing, following best practices and industry standards.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill artillery-config-generator

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.2 KB
---
name: "artillery-config-generator"
description: |
  Generate artillery config generator operations. Auto-activating skill for Performance Testing.
  Triggers on: artillery config generator, artillery config generator
  Part of the Performance Testing skill category. Use when configuring systems or services. Trigger with phrases like "artillery config generator", "artillery generator", "artillery".
allowed-tools: "Read, Write, Edit, Bash(cmd:*)"
version: 1.0.0
license: MIT
author: "Jeremy Longshore <[email protected]>"
---

# Artillery Config Generator

## Overview

This skill provides automated assistance for artillery config generator tasks within the Performance Testing domain.

## When to Use

This skill activates automatically when you:
- Mention "artillery config generator" in your request
- Ask about artillery config generator patterns or best practices
- Need help with performance testing skills covering load testing, stress testing, benchmarking, and performance monitoring.

## Instructions

1. Provides step-by-step guidance for artillery config generator
2. Follows industry best practices and patterns
3. Generates production-ready code and configurations
4. Validates outputs against common standards

## Examples

**Example: Basic Usage**
Request: "Help me with artillery config generator"
Result: Provides step-by-step guidance and generates appropriate configurations


## Prerequisites

- Relevant development environment configured
- Access to necessary tools and services
- Basic understanding of performance testing concepts


## Output

- Generated configurations and code
- Best practice recommendations
- Validation results


## Error Handling

| Error | Cause | Solution |
|-------|-------|----------|
| Configuration invalid | Missing required fields | Check documentation for required parameters |
| Tool not found | Dependency not installed | Install required tools per prerequisites |
| Permission denied | Insufficient access | Verify credentials and permissions |


## Resources

- Official documentation for related tools
- Best practices guides
- Community examples and tutorials

## Related Skills

Part of the **Performance Testing** skill category.
Tags: performance, load-testing, k6, jmeter, benchmarking

Overview

This skill automates generation of Artillery configuration files and provides step-by-step guidance for performance testing. It produces production-ready YAML/JSON scenarios, validates required fields, and recommends sensible defaults for ramp, duration, and virtual users. Use it to accelerate load, stress, and benchmarking test creation for services and APIs.

How this skill works

You give the target endpoint, workload profile, and goals (requests/sec, concurrency, duration, ramp strategy). The skill generates an Artillery config with phases, payloads, flows, and hooks, applies common validation rules, and outputs runnable configuration and commands. It also suggests environment variables, tooling commands, and minimal infrastructure considerations for distributed runs.

When to use it

  • Creating a new load test for an API or web service
  • Converting performance goals into a reproducible Artillery scenario
  • Standardizing load test configs across teams or CI pipelines
  • Validating existing Artillery configs for missing or inconsistent fields
  • Generating ramp, steady-state, and soak phases for stress tests

Best practices

  • Define clear performance goals (RPS, latency percentiles, error thresholds) before generating configs
  • Use phased workloads: ramp-up, steady-state, ramp-down to mimic real traffic
  • Parameterize sensitive data with environment variables and secrets management
  • Start small in CI, then scale tests in dedicated environments to avoid collateral impact
  • Validate generated config locally with a short smoke run before full execution

Example use cases

  • Generate a 5-phase Artillery YAML for endpoint /api/v1/orders targeting 100 RPS with 5m steady state
  • Produce a distributed run config and launch commands for running tests across multiple load agents
  • Convert a CSV of test payloads into an Artillery payload file and reference it in the scenario
  • Validate and fix a broken Artillery config that misses target or flow definitions
  • Create CI-friendly commands to run lightweight performance checks on each PR

FAQ

What inputs do I need to provide?

Provide target URL(s), desired workload (concurrency or RPS), duration and ramp strategy, authentication details, and any payload templates.

Can it generate distributed test configs?

Yes. It can output recommended agent counts, coordination settings, and example commands for running Artillery in a distributed mode.

How does it validate configs?

It checks for required fields, consistent phase definitions, valid JSON/YAML structure, and common misconfigurations like missing flows or payload references.