What problem does it solve? Turning raw outage data, error logs, and verbal summaries into consistent, objective incident reports is time-consuming and error-prone. This Skill standardizes the process by enforcing a fixed report structure, severity classification, and UTC-normalized timelines. ## Core Features & Use Cases - Structured Report Generation: Produces incident reports with summary tables, executive summaries, impact metrics, chronological timelines, root cause analysis, and corrective actions. - Severity Classification: Assigns SEV-1 through SEV-4 levels based on defined impact thresholds covering outages, data loss, and degraded features. - File Output: Saves each finalized report as a Markdown file under the skill's resources directory using an incident ID filename. - Use Case: After a production API outage, paste the alert timestamps, error rates, and remediation notes, and receive a complete post-mortem document saved as INC-2026-8941.md. ## Quick Start Generate an incident report from these outage details and save it as INC-2026-8941: the payment API returned 500 errors from 14:05 to 15:20 UTC due to a bad deployment, affecting 30 percent of users.