← ClaudeAtlas

chaos-experimentlisted

Design and document chaos engineering experiments. Guide steady state baseline, hypothesis formation, failure injection plans, and results analysis. Use when you say "design a chaos experiment", "plan a game day", "failure injection", "test resilience", or "chaos engineering". Do NOT use for security threat analysis (use threat-modeling) or pre-launch project risk identification (use pre-mortem).
rjmurillo/ai-agents · ★ 34 · AI & Automation · score 79
Install: claude install-skill rjmurillo/ai-agents
# Chaos Experiment Designer Design rigorous chaos engineering experiments that build confidence in system resilience. ## Quick Start ```text # Describe what you want to test: "Design a chaos experiment for our API gateway failover" "Plan a game day for database resilience" "Test whether our circuit breakers work under load" ``` The skill guides you through 6 phases: Scope, Baseline, Hypothesis, Injection, Execute, Analyze. ## Triggers - `chaos experiment` - `failure injection` - `game day` - `test resilience` - `chaos engineering` ## Quick Reference | Phase | Purpose | Output | |-------|---------|--------| | 1. Scope | Define system boundaries and objectives | System under test, success criteria | | 2. Baseline | Establish steady state metrics | Quantified normal behavior | | 3. Hypothesis | Form falsifiable hypothesis | Clear prediction statement | | 4. Injection | Design failure scenarios | Injection plan with blast radius | | 5. Execute | Run controlled experiment | Observation log | | 6. Analyze | Compare actual vs expected | Findings and action items | ## When to Use Use this skill when: - Planning a game day or failure injection exercise - Building confidence in system resilience before production launch - Investigating whether auto-scaling, circuit breakers, or failover mechanisms work as designed - After a real incident, to validate that fixes prevent recurrence Use [threat-modeling](../threat-modeling/SKILL.md) instead when: - Identifying security threat