Individual skill
chaos
Chaos engineering. failure injection, circuit breakers, game day, disaster recovery, resilience test, network failures.
skills/chaos/SKILL.md
Source commit 18bfc31d669804856ba232f04cdbd172afbdc379
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 6, 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)
- 28
- Repository last updated
- Aug 28, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-skills Repository topic
- autonomous-coding Repository topic
- autoresearch Repository topic
- claude-code Repository topic
- code-review Repository topic
- cursor Repository topic
- development-tools Repository topic
- gemini-cli Repository topic
- karpathy Repository topic
- engineering Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Chaos — Chaos Engineering
## Activate When
- User invokes `/godmode:chaos`
- User says "chaos test", "resilience test", "failure injection", "break it on purpose"
- User asks "what happens when X fails?" or "is this resilient?"
- User wants to plan a game day or disaster recovery drill
- Ship skill needs resilience validation before production deployment
- After a production incident, to prevent recurrence
## Workflow
### Step 1: Define Steady State
Before injecting failures, establish what "healthy" looks like: