Individual skill

chaos-experiment-designer

Designs chaos engineering experiments like network latency injection and node termination to validate resilience.

skills/testing/chaos-experiment-designer/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 27
Repository last updated: Aug 20, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
ai-skill Repository topic
ai-skill-enhancement Repository topic
ai-skills Repository topic
ai-skills-analysis Repository topic
ai-skills-fest Repository topic
ai-skills-manager Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 597 bytes
SKILL.mdcore · 1,710 bytes
SKILL.mdcore · 1,710 bytes
examples/example.mddoc · 928 bytes

Read excerpt


## Purpose

Formulate structured chaos engineering experiments to empirically test system resilience against infrastructure disruptions (network latency, pod crashes, database failovers, DNS outages).

## When to Use

- Validating high-availability claims prior to peak shopping events (Black Friday) or major launches.
- Verifying circuit breakers, retries, and fallback caches actually work under real network turbulence.
- Testing alerting thresholds and on-call paging during automated failure simulations.

## What to Analyze

1. **Steady State Hypothesis**: Measurable baseline metric representing normal operation (e.g., 99.9% 2xx responses, latency p95 < 250ms).
2. **Turbulence Variable**: Specific failure injected (e.g., 500ms latency to payment gateway, killing random Redis replicas).