chaos-engineer

An agent skill by Jeffallan, from Jeffallan/claude-skills. Tags: automation, devops, multi-agent, performance, research, security.

What it does

Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. 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, fault injection, Chaos Monkey, Litmus Chaos.

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add Jeffallan/claude-skills --skill chaos-engineer

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/Jeffallan/claude-skills
cp -r claude-skills/skills/chaos-engineer ~/.claude/skills/chaos-engineer

Safety box score

Grade F, high risk: 72 of 100 risk points, rated 2026-10-21. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.

This skill is for running chaos experiments against Kubernetes, AWS, containers, DNS, and network paths, so it intentionally performs disruptive infrastructure actions. The main risks are service interruption, root-level host changes, outbound calls to cloud/observability services, and reliance on remote manifests and credentials.

Category levels, from 0 (none) to 3 (high)
Category	Level	Why
Code & shell execution	3 (high)	It ships runnable Bash, Python, and Groovy automation that executes commands and API calls (`#!/bin/bash`, `subprocess.run`, `pipeline { ... sh 'kubectl apply ...' }`).
Network access	3 (high)	It both downloads remote artifacts and sends data to external services, including `kubectl apply -f https://litmuschaos.github.io/...`, Gremlin API calls, Prometheus queries, and Slack notifications.
Filesystem reach	2 (moderate)	It edits host files and targets service data paths outside the workspace, such as appending to `/etc/hosts` and referencing `/var/lib/postgresql/data`.
Secrets & credentials	2 (moderate)	The CI examples consume `secrets.AWS_ACCESS_KEY_ID`, `secrets.AWS_SECRET_ACCESS_KEY`, and `SLACK_WEBHOOK_URL`, so it is designed to operate with live credentials.
Privilege & persistence	3 (high)	It requires elevated privileges for system changes like `sudo apt-get install -y stress-ng` and `sudo ... >> /etc/hosts`, and it also suggests installing tools globally (`brew install toxiproxy`).
Instruction hijack surface	0 (none)	I found no prompt-hijack or instruction-bypassing content; the secrecy around surprise scenarios is operational game-day planning, not a request to ignore user or system instructions.
Irreversible actions	3 (high)	The skill can directly disrupt or delete infrastructure and services, including `aws ec2 terminate-instances`, `aws rds reboot-db-instance --force-failover`, and `kubectl delete chaosengine --all`.
Transparency	2 (moderate)	Some executed content is fetched or tagged externally rather than shipped in-repo, such as the Litmus operator URL and floating image tags like `bitnami/kubectl:latest`.

Before installing

Read `references/chaos-tools.md` and `references/infrastructure-chaos.md` for `terminate-instances`, `sudo`, and `/etc/hosts` edits.
Pin and inspect the remote Litmus manifest before any `kubectl apply -f https://...`.
Use a disposable staging account/cluster with no production AWS, Slack, or Gremlin secrets.
Test the rollback commands and kill switches on a scratch target first.

Rated 2026-10-21 by an automated review of 6 files from the skill's repository.

Source

Repository: Jeffallan/claude-skills (all skills from this repository)
Path: skills/chaos-engineer/SKILL.md
Branch: main
Updated: 2026-09-19

cloud-architect — Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure.
kubernetes-specialist — Use when deploying or managing Kubernetes workloads.
monitoring-expert — Configures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules.
app-platform-sandbox — Create and manage isolated container sandboxes for AI agent code execution.
setup — Set up the AWS DevOps Agent and AWS Security Agent connections. Use when the user says "set up", "configure", "connect", or when MCP tools are missing.
swarm — Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.