incident-template

Generate standardized incident report templates in Markdown and JSON.

17|45|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/XSpoonAi/spoon-awesome-skill --skill incident-template
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-template
Source: https://github.com/XSpoonAi/spoon-awesome-skill/tree/main/enterprise-skills/incident-template
Command: npx skills add https://github.com/XSpoonAi/spoon-awesome-skill --skill incident-template

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill simplifies the creation of structured incident reports and post-incident documentation by providing templates and formatted outputs, reducing manual writing time.

Core Features & Use Cases

  • Generates incident report templates with sections for timeline, impact, root cause, and actions.
  • Supports Markdown and JSON structured output for human and programmatic use.
  • Useful for postmortems, incident response runbooks, and shareable stakeholder updates.

Quick Start

Give a sample incident input to generate a ready-to-use incident report template.

Frequently Asked Questions about incident-template

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

FAQPage Schema
How do I generate a standardized incident report template from structured data?

To generate an incident report template, input structured data covering title, severity, impact, timeline, root cause, and resolution steps to produce formatted Markdown and JSON outputs for stakeholders.

What is the best way to create a postmortem report in both Markdown and JSON formats?

Creating a postmortem report in Markdown and JSON requires feeding incident details like affected systems and action items into a template generator, yielding human-readable documentation and machine-readable data simultaneously.

Can I use incident report templates for stakeholder communications and runbooks?

Yes, incident report templates can be used for stakeholder communications and runbooks by structuring impact, timeline, and resolution data into shareable formats for IT operations and security teams.

What structured inputs do I need to provide for automated incident report generation?

Automated incident report generation requires structured inputs including title, severity, type, impact, affected systems, timeline, assigned team, root cause, resolution steps, and action items to output valid reports.

Does the incident report generator support outputting machine-readable JSON for postmortems?

Yes, the incident report generator supports outputting machine-readable JSON for postmortems by processing structured incident data, enabling programmatic integration for IT operations and platform teams.