alirezarezvani/claude-skills / engineering/skills/chaos-engineering
chaos-engineering
VerifiedUse before running a chaos experiment, gameday or fault injection, or after one to write it up. Designs it with steady state and abort criteria in experiment_designer.py, sizes the blast radius with blast_radius_calculator.py and drafts the postmortem.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.1 KB |
| assets/experiment_template.md | markdown | 2.4 KB |
| assets/postmortem_template.md | markdown | 1.5 KB |
| references/attack_taxonomy.md | markdown | 5.7 KB |
| references/chaos_principles.md | markdown | 5.3 KB |
| references/experiment_design.md | markdown | 5.6 KB |
| references/tooling_landscape.md | markdown | 6.1 KB |
| scripts/blast_radius_calculator.pyexecutable | script | 4.9 KB |
| scripts/experiment_designer.pyexecutable | script | 6.3 KB |
| scripts/experiment_postmortem.pyexecutable | script | 5.1 KB |
assets/postmortem_template.md
View on GitHub# Chaos Experiment Postmortem
## Identity
- **Experiment:** `<experiment_id>`
- **Date:** `<YYYY-MM-DD>`
- **Target:** `<service>`
- **Owner:** `<handle@team>`
- **Postmortem facilitator:** `<handle@team>`
## Hypothesis
> `<hypothesis from the plan>`
## Outcome
- [ ] **Held** — hypothesis confirmed
- [ ] **Refuted** — hypothesis disproven
- [ ] **Inconclusive** — could not tell
## Timeline
| Time | Event |
|---|---|
| T-5min | Started baseline measurement |
| T+0 | Attack injected |
| T+? | `<observation>` |
| T+? | `<observation>` |
| T+N | Attack ended (or aborted) |
| T+N+2 | Steady state recovered |
## What we learned
`<at least one concrete learning — required>`
## What surprised us
`<unexpected observations; "nothing surprised us" is a signal that you didn't push hard enough>`
## What failed
`<things that broke during the experiment that shouldn't have>`
## What held
`<things that worked as expected — confidence-building data points>`
## Root causes (if any failures)
`<technical analysis without blame>`
## Follow-up actions
| Action | Owner | Due | Status |
|---|---|---|---|
| `<concrete action>` | `<@owner>` | `<date>` | `[ ]` |
| `<concrete action>` | `<@owner>` | `<date>` | `[ ]` |
> Every experiment should produce ≥1 follow-up. If none — re-examine whether you tested anything new.
## Next experiment
`<what's the next experiment that builds on this learning?>`
## Stakeholder summary (1-2 sentences)
`<for the team channel; describe outcome and biggest learning>`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |