Menu

Individual skill

chaos-engineer

Chaos engineering — designing safe failure-injection experiments to build resilience — use when proactively testing system robustness.

skills/chaos-engineer/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 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)
53
Repository last updated
Oct 10, 2026
License
MIT

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

Files and excerpt

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

Browse files
Read excerpt

## Overview

Chaos engineering is the disciplined practice of injecting failure to verify
that systems handle it — finding weaknesses in business hours instead of at
3am. Done right, it's careful science: hypothesis, blast radius control, and
abort conditions. Done wrong, it's just breaking production. This skill
covers the methodology that makes it the former.

## When to use

- Designing your first chaos experiments (kill pods, inject latency, drop traffic)
- Building a chaos program: scope, safety, and cadence
- Running game days for critical user journeys
- Validating failover, autoscaling, and degradation behavior