Incident Commander

Classify technology incidents into SEV1-SEV4 and generate response communications.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Nuwanda04/Ballen-Fisk --skill incident-commander-nuwanda04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Incident Commander
Source: https://github.com/Nuwanda04/Ballen-Fisk/tree/main/.claude/skills/incident-commander
Command: npx skills add https://github.com/Nuwanda04/Ballen-Fisk --skill incident-commander-nuwanda04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework for managing technology incidents, ensuring swift, organized, and effective responses from detection through post-incident review.

Core Features & Use Cases

  • Automated Severity Classification: Instantly assesses incident severity based on impact and keywords.
  • Structured Response Guidance: Provides clear initial actions, team recommendations, and communication templates.
  • Use Case: When a critical service outage occurs, use this Skill to automatically classify the incident as SEV1, identify the primary response team, and generate an initial stakeholder communication draft.

Quick Start

Use the incident commander skill to classify an incident described as 'payment API returning 500 errors for 70% of requests'.

Frequently Asked Questions about Incident Commander

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

FAQPage Schema
How do I automate incident severity classification for a service outage?

Incident severity classification is automated by analyzing incident descriptions and impact metrics to instantly categorize events from SEV1 to SEV4. This provides detailed response protocols and identifies the primary response team needed for mitigation.

What is included in structured incident response guidance?

Structured incident response guidance includes initial action steps, team recommendations, and communication generation templates. It ensures organized technology incident management from detection through post-incident review based on severity assessment.

Can I generate stakeholder communication drafts automatically during an incident?

Stakeholder communication drafts are generated automatically using predefined templates based on the incident severity classification. This provides clear initial actions and structured guidance to ensure effective communication during technology incidents.

How do I manage SLA requirements during a critical incident response?

SLA management during critical incident response is supported through severity classification and structured response protocols. By assessing impact metrics and categorizing incidents from SEV1 to SEV4, the appropriate SLA-driven response is initiated.

What is the best way to structure a postmortem after resolving an incident?

A postmortem is structured by leveraging the incident classification, response planning, and communication records generated during the event. This framework ensures a comprehensive post-incident review covering severity assessment and team recommendations.

Does incident response automation work with SEV1 through SEV4 classification levels?

Incident response automation fully supports SEV1 through SEV4 classification levels by evaluating incident descriptions and impact metrics. Each severity level triggers detailed response protocols, team recommendations, and specific communication templates.