AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

chaos-engineering

Use 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.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--chaos-engineering at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 7

assets/postmortem_template.md

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>