incident

Generate prioritized triage checklists for production incidents and log findings to Obsidian.

5|2|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/thoreinstein/opencode-config --skill incident
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident
Source: https://github.com/thoreinstein/opencode-config/tree/main/skill/incident
Command: npx skills add https://github.com/thoreinstein/opencode-config --skill incident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Incident Skill helps teams quickly interpret production incidents, generate a prioritized triage checklist, and systematically log findings in Obsidian for post-incident reviews.

Core Features & Use Cases

  • Automated triage checklist generation based on problem statements and logs
  • Parallel investigation framework with External Research, Codebase Exploration, and Code Analysis tracks
  • Obsidian integration to create consistent incident logs and post-mortems
  • Supports actionable mitigations and rollback considerations for faster recovery

Quick Start

Provide a concise problem statement describing symptoms, errors, and affected systems; then run the incident skill to produce a prioritized triage checklist and append findings to Obsidian.

Frequently Asked Questions about incident

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

FAQPage Schema
How do I generate an incident triage checklist for production failures?

To generate an incident triage checklist, provide a problem statement detailing symptoms, errors, and affected systems. The incident skill analyzes this input to produce a prioritized checklist for rapid containment and recovery.

What is the best way to structure post-mortem logs for distributed service incidents?

The best way to structure post-mortem logs is to use Obsidian integration to create consistent, date-stamped incident entries. This ensures findings from distributed service investigations are systematically logged for post-incident reviews.

How do I run parallel investigations during production incident triage?

You can run parallel investigations by following a framework that splits incident triage into External Research, Codebase Exploration, and Code Analysis tracks. This approach accelerates root-cause analysis across distributed services, logs, and metrics.

Can I use this incident management skill for distributed services with complex alerts?

Yes, you can use this incident management skill for distributed services with complex alerts. It analyzes metrics, logs, and alerts to guide investigators through actionable mitigations and rollback considerations for faster recovery.

Does the incident triage skill require specific log formats to analyze root-cause?

The incident triage skill does not require rigid log formats but operates on a concise problem statement describing symptoms and errors. It processes provided logs and metrics to produce deterministic output for actionable mitigations.

What steps are needed to start automated incident triage?

To start automated incident triage, provide a concise problem statement describing the symptoms, errors, and affected systems. Running the skill then produces a prioritized triage checklist and appends findings to Obsidian.