skills.rest
jerelvelarde
jerelvelardeCOMMUNITY
Explore all skills by this author →
GitHub

create-incident-report

Create standardized incident reports with timelines, impact, severity, and root cause.

6|Updated Feb 19, 2026
Search Tags:#timeline#postmortem#root-cause#incident#incident-management#action-items
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-incident-report-jerelvelarde
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-incident-report
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/create-incident-report
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-incident-report-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates standardized incident reports to document outages, post-mortems, and real-time incident coordination, reducing confusion and speeding remediation.

Core Features & Use Cases

  • Structured timelines, impact assessment, and root cause analysis templates.
  • Supports active incident coordination and post-incident retrospectives.
  • Generates action items with owners and due dates to close gaps.

Quick Start

Create a new incident report using the current incident context and available evidence.

Frequently Asked Questions about create-incident-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a structured incident report for an outage?▼

To generate a structured incident report, you input real-time or post-incident data to populate a standardized template capturing the timeline, impact, severity, root cause, and corrective actions.

What should a postmortem report include for effective root-cause analysis?▼

A postmortem report should include a structured timeline, impact assessment, root cause analysis, trigger events, corrective actions taken, and lessons learned to prevent future outages.

Can I use this for active incident coordination or is it only for retrospectives?▼

You can use this for both active incident coordination and post-incident retrospectives, guiding real-time response while capturing necessary timeline and action items for the final report.

How do I create incident action items with owners and due dates?▼

You create incident action items by defining corrective actions within the structured report template, assigning specific owners and due dates to close identified gaps and prevent recurrence.

Do I need engineering docs to create an incident report?▼

Yes, the process relies on your project's engineering docs for context, using them alongside available evidence to accurately determine the trigger, root cause, and impact of the incident.

What is the best way to document an outage timeline during an incident?▼

The best way to document an outage timeline is to feed real-time incident data and evidence into a standardized template, which automatically structures the sequence of events and actions.

Related Skills

Explore More Software Engineering Skills→
janjaszczakjanjaszczak

mcp-grafana

Cross-reference Grafana dashboards, logs, and alerts to identify incident causes.

Community
Intermediate
HigorAlvesHigorAlves
4

postmortem

Create structured postmortem reports for production incidents with root cause analysis.

Community
Basic
ajianazajianaz
4

observability-monitor

Orchestrate end-to-end observability and monitoring for complex applications.

Community
Advanced
DoubleslashSEDoubleslashSE
4

log-analysis

Parse infrastructure logs to extract actionable insights for incident detection.

Community
Intermediate