incident-writer

Generate structured IT incident reports from logs, metrics, and outage details.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill incident-writer-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-writer
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/incident-writer
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill incident-writer-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about incident-writer

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

FAQPage Schema
How do I write an incident report from outage logs?

Provide the incident summary, start and end times, affected services, impact metrics, root cause, and remediation steps. The skill extracts these details, assigns a severity level, and produces a structured Markdown report saved to its resources directory.

What severity levels does an incident report use?

The skill classifies incidents into four levels: SEV-1 for critical outages or data loss, SEV-2 for major feature failures with broad impact, SEV-3 for minor failures with workarounds, and SEV-4 for low-impact internal or cosmetic issues.

What sections should a post-mortem incident report include?

The generated report includes a summary information table, executive summary, user impact metrics, a chronological UTC timeline, root cause analysis distinguishing trigger from systemic vulnerability, and immediate plus long-term corrective actions.

Where are generated incident report files saved?

Reports are written as Markdown files to the .agents/skills/incident-writer/resources/ directory, named by incident ID such as INC-2026-8941.md. File system write access is required for this output step.

Can I generate an incident report without exact timestamps?

Yes, but the report quality depends on available data. The skill normalizes all timestamps to UTC and marks unresolved items as ongoing, so partial information still produces a structured draft you can refine later.