incident-summary

Summarizes local log excerpts into a concise incident postmortem draft.

2.4k|292|Updated Feb 7, 2026

Search Tags:#Python #postmortem #sre #incident #summarize #Log Analysis #Timeline

One-click install

npx skills add https://github.com/The-Vibe-Company/companion --skill incident-summary

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: incident-summary
Source: https://github.com/The-Vibe-Company/companion/tree/main/examples/skills/incident-summary
Command: npx skills add https://github.com/The-Vibe-Company/companion --skill incident-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

After an incident, engineers must manually sift through scattered log excerpts to reconstruct what happened, which delays postmortem writing and risks missing key timeline events.

Core Features & Use Cases

Timeline Reconstruction: Reads a directory of *.log excerpts and organizes events into a coherent incident timeline.
Postmortem Drafting: Produces a terse summary covering timeline, impact, suspected cause, and follow-up actions.
Offline Operation: Works entirely on local files with no network access, keeping sensitive incident data on your machine.
Use Case: After a production outage, point the Skill at a folder of exported log excerpts and receive a structured postmortem draft to refine with your team.

Quick Start

Ask the assistant to summarize the incident from the log excerpts in your local logs folder covering the outage window.

Frequently Asked Questions about incident-summary

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

FAQPage Schema

How do I summarize incident logs into a postmortem?▼

Point the Skill at a folder of .log excerpts along with a short prompt describing the incident window. It reads the files and produces a draft covering timeline, impact, suspected cause, and follow-ups.

What log formats does incident summarization support?▼

The Skill operates on plain-text .log excerpt files placed in a local directory. It reads them with file-reading tools and does not require a specific structured log schema.

Does incident-summary send my logs to an external service?▼

No. The Skill explicitly states it has no network access and operates on local files only, so log data stays on your machine during summarization.

What are the limitations of automated incident summarization?▼

The included summarize.py script is a toy illustrative example that only counts log excerpts. Real timeline extraction depends on the agent's reasoning over the log content, so results should be reviewed before publishing a postmortem.