Devops Chaos Engineering

Use when the user asks about chaos engineering, chaos experiments, GameDays, Chaos Mesh, LitmusChaos, AWS Fault Injection Service, Azure Chaos Studio, steady-state hypotheses, or chaos in CI. Produces experiment designs, tool choice and a chaos program. Not for load testing (use quality-load-testing) or backup restore drills (use backup-dr).

45 stars 6 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill devops-chaos-engineering
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/devops/chaos-engineering ~/.claude/skills/devops-chaos-engineering

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Chaos Engineering

## Purpose
Build confidence that the system withstands turbulent conditions by running controlled experiments: state a steady-state hypothesis, inject a realistic fault with a bounded blast radius, observe, and fix the weaknesses found. The goal is learning and hardening, not breaking things for show.

## Agent Protocol

### Trigger
"chaos engineering", "chaos experiment", "gameday", "chaos mesh", "litmus", "AWS FIS", "resilience testing", "chaos in CI", "steady state", "chaos program".

### Input Context
- Architecture and known failure modes (dependencies, AZs, queues, caches).
- SLIs/SLOs and dashboards available; maturity (never done chaos vs routine).
- Platform (Kubernetes, AWS/Azure/GCP VMs, serverless).

### Output Artifact
Experiment plan(s), tool manifests, GameDay runbook. No file unless requested.

### Response Format
```
Hypothesis: When {fault}, {SLI} stays within {threshold}
Fault + tool: {e.g. pod-kill via Chaos Mesh PodChaos}
Blast radius: {env, % targets, duration}
Abort: {SLI condition / alarm}
Observations to record: {metrics, alerts fired, recovery time}
Follow-up: {tickets}
```

### Completion Criteria
- [ ] Hypothesis expressed in terms of user-facing SLIs.
- [ ] Blast radius, duration, abort conditions, and rollback defined before running.
- [ ] Stakeholders/on-call informed; results recorded with action items.

## Principles (principlesofchaos.org)
Read the full skill on GitHub

Details

Skill name
devops-chaos-engineering
Path
skills/devops/chaos-engineering/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Devops Chaos Engineering skill do?

Use when the user asks about chaos engineering, chaos experiments, GameDays, Chaos Mesh, LitmusChaos, AWS Fault Injection Service, Azure Chaos Studio, steady-state hypotheses, or chaos in CI. Produces experiment designs, tool choice and a chaos program. Not for load testing (use quality-load-testing) or backup restore drills (use backup-dr).

How do I install the Devops Chaos Engineering skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill devops-chaos-engineering. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Devops Chaos Engineering popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Devops Dataops

45

j4flmao/agent-skills

Use when the user asks about DataOps, CI/CD for data pipelines, dbt slim CI with state:modified, SQLFluff, Great Expectations in CI, data environment management, or data contract checks in CI. Produces data pipeline CI/CD workflows and quality gates. Not for pipeline design (use data-etl-pipeline) or application CI/CD (use cicd-pipeline).

DevOps & Cloud

Devops Azure

45

j4flmao/agent-skills

Use when the user asks about Azure, AKS, App Service, Bicep or ARM templates, Entra ID (Azure AD), managed identity, Azure Policy, Key Vault, Azure Monitor, Front Door, or a CAF landing zone. Produces Azure architectures and Bicep/CLI configs. Not for Azure Functions and Durable Functions (use cloud-native-azure-functions) or AWS (use aws).

DevOps & Cloud

Devops Finops

45

j4flmao/agent-skills

Use when the user asks why the AWS bill doubled, to find cloud savings, FinOps, cost allocation and tagging, Savings Plans or reserved instances, rightsizing, budgets and cost anomaly alerts, or unit economics. Produces a cost analysis with prioritized savings. Not for enterprise cost policy (use enterprise-cost-governance) or Kubernetes autoscaling (use devops-kubernetes-autoscaling).

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.