Chaos Engineering
Use when planning, running, or learning from chaos engineering experiments.
Before & after
Same prompt, same agent — the only difference is the skill.
Chaos engineering is a discipline for testing system resilience by intentionally injecting failures. For a payment service, testing database disconnection would be valuable. You'd want to define what success looks like—how quickly the system recovers, whether it gracefully degrades, etc. What's your current infrastructure? Are you using Kubernetes? Do you have monitoring in place? Understanding your setup would help me suggest specific tools and experiment design.
CHAOS EXPERIMENT: Payment Service Database Failover HYPOTHESIS Payment service maintains transaction integrity and recovers to healthy state within 30 seconds when primary database connection is severed. STEADY STATE BASELINE → Payment API processing 1,000 requests per minute → 99.5% success rate on transaction completion → P95 latency at 200ms BLAST RADIUS → Scope: Production payment API pods only (not admin dashboard) → Blast duration: 120 seconds maximum → Automatic rollback: kill switch if success rate drops below 95% EXPERIMENT SEQUENCE Step 1: Kill 30% of database connections Step 2: Observe error handling, request routing to replica Step 3: Measure recovery time and transaction retry behavior Step 4: Inject gradual connection delay (500ms to 5sec) SUCCESS CRITERIA → Zero corrupted transactions during outage → Automatic failover to replica within 10 seconds → No customer-facing errors (client receives retry directive) → Recovery to baseline throughput within 45 seconds ABORT TRIGGERS (stop experiment immediately) → Any transaction data corruption detected → Success rate below 94% for 15 consecutive seconds → P99 latency exceeds 5 seconds POSTMORTEM CHECKLIST → Did failover happen automatically? → Were alerts fired correctly? → Time to detect → time to mitigate → Any manual intervention needed?
About this skill
name: chaos-engineering description: Use when Use when planning, running, or learning from chaos engineering experiments.
Chaos Engineering
Use when planning, running, or learning from chaos engineering experiments. Triggers on "chaos experiment", "fault injection", "gameday", "resilience test", "blast radius", "steady state", "abort criteria", "Chaos Toolkit", "Chaos Mesh", "Litmus", "Gremlin", "AWS FIS", or any deliberate failure-injection question. Ships experiment designer, blast-radius calculator, and postmortem generator (all stdlib Python), 4 references on chaos principles + experiment design + attack taxonomy + tooling landscape, and a /chaos-experiment slash command. Composes with feature-flags-architect (kill switches as abort triggers) and kubernetes-operator (common chaos targets).
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the chaos-engineering skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Chaos Engineering; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: chaos-engineering
description: Use this skill when planning, running, or learning from chaos engineering experiments such as fault injection, gamedays, or resilience tests.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Chaos Engineering
Runs the full chaos engineering lifecycle: designing the experiment, calculating blast radius, executing the injection, and turning the result into a postmortem the team will act on.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.