AI Agent Skills

Install the LoadStrike AI agent skills when you want an AI coding assistant to draft, review, and refine LoadStrike scenarios in the SDK language your team already uses.

What this page helps you do

What this page helps you do

Use AI assistance without losing the documented LoadStrike scenario model, SDK language choice, runner-key setup, or reporting workflow.

Who this is for

Engineers and QA teams that already use AI coding assistants and want safer LoadStrike-specific scenario generation.

Prerequisites

  • An AI assistant that can consume local or repository-provided skill instructions
  • A supported LoadStrike SDK language selected for the generated test
  • A valid runner key supplied through normal configuration before execution

By the end

A clearer prompt and review workflow for AI-generated LoadStrike tests that stay aligned with the supported SDK surface.

Choose this path when

Use this page when you want AI help creating or reviewing LoadStrike tests, but still want the output to follow documented SDK usage, normal licensing validation, and product-supported feature boundaries.

Visual guide

Sequence diagram showing how a LoadStrike workflow moves from setup to report output.
This page fits into the same setup, run, correlate, and report flow as the rest of the public LoadStrike runtime.

Guide

What the repository provides

The repository contains LoadStrike-specific guidance for AI coding agents. It explains when to use scenarios, steps, load simulations, traffic mix, reports, portal reporting, protocol adapters, and SDK-specific examples.

How to prompt effectively

Give the assistant the target system, SDK language, expected traffic shape, report outputs, and any transaction-completion signal. Ask it to keep secrets in configuration and to call out assumptions before producing runnable code.

What to review

Review generated code for runner-key configuration, scenario names, load simulations, thresholds, report formats, plan-gated features, and whether the test is a plain endpoint check or a full transaction.

Safety boundary

The skill must not suggest bypassing licensing checks, overriding licensing URLs, or exposing private runtime internals. Generated tests should use the public SDK APIs and run through normal validation.

Getting started samples

Use this repository when your team wants an AI coding assistant to generate LoadStrike scenarios using the same SDK language, runner setup, and reporting rules documented here.

If you run these examples locally, add a valid runner key before execution starts. Set it with WithRunnerKey("...") or the config key LoadStrike:RunnerKey.

Install The AI Agent Skills

dotnet add package LoadStrike

Use the LoadStrike AI agent skills repository:
https://github.com/LoadStrike/loadstrike-ai-agent-skills

Prompt:
Create a LoadStrike performance test in C# for the orders API.
Use the runner key from configuration, generate HTML and CSV reports,
and keep the scenario aligned with the documented .NET SDK APIs.

AI-assisted workflow

Install the skill

Add the repository instructions to the AI assistant your team uses so it understands LoadStrike concepts, SDK language choices, and safe runner setup.

Describe the target

Tell the assistant the service, endpoint, browser flow, queue, or transaction path you want to test. Include the chosen SDK language and expected load shape.

Keep secrets external

Ask for runner keys, API tokens, and environment-specific values to come from configuration or environment variables instead of being hard-coded.

Review before running

Check the generated scenario, thresholds, reports, and plan-gated features before executing the test with a valid runner key.

The skill is guidance for AI-assisted authoring. LoadStrike runtime validation and licensing behavior remain unchanged.