Skip to content
Get packs

Chaos Engineer

Plan and run controlled failure experiments on distributed systems, with safety limits and rollback steps

Source Download skill
Repository
Jeffallan/claude-skills
Stars
12,176
Licence
MIT
Files
6 files

What it does

Once installed, the agent can help you design chaos engineering experiments: deliberately breaking parts of a system (killing pods, adding network latency, taking down servers) in a controlled way to see whether it stays resilient. It guides you through writing a hypothesis, defining steady-state metrics, limiting blast radius, planning rollback, running game day exercises, and writing post-mortem templates. It also includes example commands for tools such as Litmus Chaos, toxiproxy and Chaos Monkey.

Great for

  • Site reliability and DevOps engineers planning resilience tests for production-like services
  • Teams preparing their first game day exercise and needing runbooks and post-mortem templates
  • Engineers setting up fault injection in a staging Kubernetes cluster

Skip it if

  • Running experiments directly against production without reviewing the generated commands first, since the skill's example manifests target a 'production' namespace and a wrong target could cause a real outage
  • Small single-server apps with no redundancy, where injected failures mostly show nothing useful and add risk
  • Non-technical users looking for a general test-writing tool; the content assumes Kubernetes, distributed systems and CLI experience

Try asking

  • “Design a chaos experiment to test how my checkout service handles the loss of one database replica, including hypothesis, metrics and rollback steps”
  • “Write a Litmus ChaosEngine manifest that deletes at most a third of my API pods in staging”
  • “Plan a game day for our on-call team covering a region failure scenario”
  • “Create a post-mortem template and learning summary after a failed resilience test”
Step-by-step guide: how to use Chaos EngineerInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 6 original files, the MIT licence and an attribution note.

    chaos-engineer.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip chaos-engineer.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip chaos-engineer.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Verify steady state and confirm the automated rollback path works in staging before any experiment, as the skill's safety checklist requires.
  • Keep the blast radius small and change one failure variable at a time, then expand only after results are understood.
  • Review every generated kubectl, patch or chaos command yourself, especially namespace and label selectors, before running it against a live cluster.

What's inside

  • references/chaos-tools.md
  • references/experiment-design.md
  • references/game-days.md
  • references/infrastructure-chaos.md
  • references/kubernetes-chaos.md
  • SKILL.md

Redistributed unmodified from Jeffallan/claude-skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.