Organize incident facts into an evidence-based root cause analysis document.
npx skills add https://github.com/Arafly/sre-playbooks --skill rca-arafly
Please help me install this Agent Skill. Skill: rca Source: https://github.com/Arafly/sre-playbooks/tree/main/rca Command: npx skills add https://github.com/Arafly/sre-playbooks --skill rca-arafly
This Skill helps teams turn a restored incident into a rigorous, evidence-based root cause analysis instead of a blame-focused or speculative postmortem. It is designed to reduce narrative bias, separate facts from inference, and produce a document that can stand up to technical and leadership review.
Use the rca skill to analyze this incident timeline and supporting evidence, then draft a defensible root cause analysis with facts, causal chain, and corrective actions.
High-intent search queries and answers about installing and using this skill.
To write an evidence-based root cause analysis, build an incident timeline from logs and metrics, separate verified facts from inference, and challenge competing explanations to produce a defensible postmortem document.
The best way to structure an incident review is to enforce a workflow that builds an evidence inventory, develops a causal chain, and uses fresh-reviewer checks to challenge assumptions before publication.
You distinguish verified facts from inference by organizing artifacts like chat transcripts and deployment history into a structured evidence inventory before developing causal chains.
Yes, you can validate operational readiness before publishing an RCA by applying independent review checks to challenge assumptions, surface gaps, and confirm corrective actions meet success criteria.
An incident timeline for a defensible root cause analysis should include facts extracted from logs, metrics, traces, deployment history, and chat transcripts organized chronologically.
To identify contributing factors and systemic root causes, analyze the evidence timeline to map causality, determine impact, and define corrective actions with assigned owners and success criteria.
bordenetReconstruct incident timelines from distributed traces, logs, deployments, and metrics.
timequityCreate blameless postmortems documenting root-cause analyses with structured markdown templates.
timequitySet up Prometheus, Grafana, Loki, and Jaeger for Kubernetes observability.
wshobsonGenerate blameless postmortem documents from structured incident details.
