Afrexai Post Mortem

What This Skill Does

The Afrexai Post Mortem skill provides a standardized, rigorous framework for conducting blameless incident reviews within the OpenClaw ecosystem. Designed to turn production failures, missed deadlines, and service degradations into actionable learning opportunities, this skill structures the analysis process to move beyond simple troubleshooting. By implementing a systematic approach—including timelines, 5-Whys root cause analysis, and contributing factor scoring—it helps teams identify systemic gaps rather than blaming individuals. It ensures that every incident results in concrete, assigned action items to prevent recurrence and improve future resilience.

Installation

You can install this skill by executing the following command in your terminal: clawhub install openclaw/skills/skills/1kalin/afrexai-post-mortem

Use Cases

This skill is ideal for engineering, DevOps, and project management teams facing operational challenges. Use it immediately following any high-impact incident (SEV-1 or SEV-2), after significant project failures or missed milestones, or to conduct quarterly retrospectives of recurring technical debt. It is particularly effective for teams looking to cultivate a culture of psychological safety while maintaining high standards of system reliability and accountability.

Example Prompts

1. "OpenClaw, please trigger a new post-mortem for the authentication service outage that occurred today from 2 PM to 4 PM."
2. "Review the incident timeline for our recent API downtime and help me complete the 5-Whys section to find the root cause."
3. "Summarize the action items from our last three incidents and suggest a priority list for the next sprint based on their recurrence."

Tips & Limitations

To get the most out of this skill, ensure you document the incident as close to the event as possible while the details are fresh. Stick strictly to the 'Blameless Rules' listed in the documentation to ensure honest participation from your team. Remember that this tool is a framework; the quality of your output depends on the depth of the data you provide. It is not an automated monitoring tool, so ensure you have your observability metrics ready before beginning the analysis. The cost calculator features should be updated as soon as the financial impact of an outage is finalized to maintain accurate records.