dots-workstation-incident

Draft and review incident reports and RCA notes for IT operations.

2|3|Updated Apr 7, 2026

Search Tags:#root cause analysis #incident management #IT operations #IT support #service disruption

Ready to run

npx skills add https://github.com/ulises-jeremias/agentic-workstation --skill dots-workstation-incident

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dots-workstation-incident
Source: https://github.com/ulises-jeremias/agentic-workstation/tree/main/home/dot_local/share/agentic-workstation/skills/dots-workstation-incident
Command: npx skills add https://github.com/ulises-jeremias/agentic-workstation --skill dots-workstation-incident

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The dots-workstation-incident Skill addresses the time-consuming and error-prone process of drafting and reviewing incident reports and root cause analysis (RCA) notes by leveraging structured guidelines.

Core Features & Use Cases

Incident Report Drafting: Provides templates and guidance for incident detection, impact assessment, timeline creation, RCA, resolution, and follow-up actions.
Root Cause Analysis: Helps in identifying the underlying issues and contributing factors to an incident, ensuring comprehensive investigation and action planning.
Use Case: Ideal for IT operations teams facing production disruptions, allowing them to efficiently create and review incident reports post-outage for continuous improvement.

Quick Start

Use the 'dots-workstation-incident' skill to draft an incident report for the recent service disruption.

Frequently Asked Questions about dots-workstation-incident

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

FAQPage Schema

How do I draft an incident report for IT operations after a service disruption?▼

Draft an incident report by following structured guidelines for incident detection, impact assessment, timeline creation, resolution, and follow-up actions. This provides templates to efficiently document production outages and ensure comprehensive post-mortem analysis.

What is root cause analysis in incident management and how does it work?▼

Root cause analysis in incident management identifies underlying issues and contributing factors to a service disruption. It works by guiding a structured investigation during post-mortem analysis to ensure comprehensive action planning and continuous improvement.

Can I use this for post-mortem analysis of production outages in IT support?▼

Yes, you can use this for post-mortem analysis of production outages in IT support. It is ideal for IT operations teams facing service disruptions, allowing them to efficiently create and review incident reports for continuous improvement.

What should be included in an incident report for a service disruption?▼

An incident report for a service disruption should include structured incident detection, impact assessment, timeline, root cause analysis, resolution, and follow-up actions. These components ensure a comprehensive investigation and post-mortem documentation.

Is structured incident management necessary for reviewing IT support post-mortems?▼

Structured incident management is necessary for reviewing IT support post-mortems because it addresses the error-prone process of drafting RCA notes. Leveraging structured guidelines ensures comprehensive investigation and effective action planning for continuous improvement.