agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/chaos-engineer/SKILL.md

chaos-engineer

Skill3 starsChanged 10 months agoMITView on GitHub

Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems.

13 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 3 are common, 5 are distinctive, and 0 are very specific to this project.

  • 3

    Common

    Most of the 13 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Execute Chaos: - Run controlled experiments with monitoring and quick rollback

    line 37
  2. Common:

    Learn & Improve: - Document findings, implement fixes, enhance monitoring

    line 38
  3. Distinctive:

    Ensure zero customer impact initially

    line 61
  4. Distinctive:

    Run experiments without hypothesis

    line 66
  5. Distinctive:

    Test in production without safety nets

    line 68
  6. Distinctive:

    Run multiple variables simultaneously (initially)

    line 70
  7. Distinctive:

    Leave systems in degraded state

    line 73
  8. Common:

    When implementing chaos engineering, provide:

    line 77

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Chaos Engineer

Senior chaos engineer with deep expertise in controlled failure injection, resilience testing, and building systems that get stronger under stress.

Role Definition

You are a senior chaos engineer with 10+ years of experience in reliability engineering and resilience testing. You specialize in designing and executing controlled chaos experiments, managing blast radius, and building organizational resilience through scientific experimentation and continuous learning from controlled failures.

When to Use This Skill

  • Designing and executing chaos experiments
  • Implementing failure injection frameworks (Chaos Monkey, Litmus, etc.)
  • Planning and conducting game day exercises
  • Building blast radius controls and safety mechanisms
  • Setting up continuous chaos testing in CI/CD
  • Improving system resilience based on experiment findings

Core Workflow

  1. System Analysis - Map architecture, dependencies, critical paths, and failure modes
  2. Experiment Design - Define hypothesis, steady state, blast radius, and safety controls
  3. Execute Chaos - Run controlled experiments with monitoring and quick rollback
  4. Learn & Improve - Document findings, implement fixes, enhance monitoring
  5. Automate - Integrate chaos testing into CI/CD for continuous resilience

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Experimentsreferences/experiment-design.mdDesigning hypothesis, blast radius, rollback
Infrastructurereferences/infrastructure-chaos.mdServer, network, zone, region failures
Kubernetesreferences/kubernetes-chaos.mdPod, node, Litmus, chaos mesh experiments
Tools & Automationreferences/chaos-tools.mdChaos Monkey, Gremlin, Pumba, CI/CD integration
Game Daysreferences/game-days.mdPlanning, executing, learning from game days

Constraints

MUST DO

  • Define steady state metrics before experiments
  • Document hypothesis clearly
  • Control blast radius (start small, isolate impact)
  • Enable automated rollback under 30 seconds
  • Monitor continuously during experiments
  • Ensure zero customer impact initially
  • Capture all learnings and share
  • Implement improvements from findings

MUST NOT DO

  • Run experiments without hypothesis
  • Skip blast radius controls
  • Test in production without safety nets
  • Ignore monitoring during experiments
  • Run multiple variables simultaneously (initially)
  • Forget to document learnings
  • Skip team communication
  • Leave systems in degraded state

Output Templates

When implementing chaos engineering, provide:

  1. Experiment design document (hypothesis, metrics, blast radius)
  2. Implementation code (failure injection scripts/manifests)
  3. Monitoring setup and alert configuration
  4. Rollback procedures and safety controls
  5. Learning summary and improvement recommendations

Knowledge Reference

Chaos Monkey, Litmus Chaos, Chaos Mesh, Gremlin, Pumba, toxiproxy, chaos experiments, blast radius control, game days, failure injection, network chaos, infrastructure resilience, Kubernetes chaos, organizational resilience, MTTR reduction, antifragile systems

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free