incident-commander

Name: incident-commander
Availability: InStock
Author: mitchellvandusen-cell

Classify, mitigate, and analyze incidents for InsuranceGrokBot with post-incident reporting.

Updated Dec 12, 2025

Search Tags:#root cause analysis #incident response #service health #post-incident reporting #InsuranceGrokBot

Ready to run

npx skills add https://github.com/mitchellvandusen-cell/Flask-Webhook --skill incident-commander-mitchellvandusen-cell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-commander
Source: https://github.com/mitchellvandusen-cell/Flask-Webhook/tree/main/.claude/skills/incident-commander
Command: npx skills add https://github.com/mitchellvandusen-cell/Flask-Webhook --skill incident-commander-mitchellvandusen-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Flask, Gunicorn, psycopg2, redis, Twilio, xAI, Stripe, OAuth, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive incident response system for InsuranceGrokBot, handling severity classification, immediate mitigation, root cause analysis, and post-incident reporting.

Core Features & Use Cases

Incident Classification: Quickly classify incidents into severity levels (P0, P1, P2, P3).
Immediate Mitigation: Execute immediate actions to mitigate the impact of incidents.
Root Cause Analysis: Perform detailed analysis to identify the root cause of incidents.
Service Health Checks: Use Railway MCP tools to check service health and logs.
Post-Incident Reporting: Generate detailed post-incident reports with impact assessment and lessons learned.

Quick Start

Run the incident-commander skill to classify and respond to the current incident in InsuranceGrokBot production systems.

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 response and root cause analysis for my Flask application?▼

Automate incident response by classifying severity, executing mitigations, performing root cause analysis, and generating post-incident reports. This system manages the full lifecycle for Flask applications using Railway and PostgreSQL.

What is included in post-incident reporting for production service health checks?▼

Post-incident reporting includes detailed impact assessments, root cause analysis, and lessons learned. It utilizes Railway MCP tools to execute service health checks and review logs for comprehensive documentation.

Can I use Twilio and Stripe integrations to classify and mitigate P0 incidents?▼

Yes, you can classify incidents into P0, P1, P2, and P3 severity levels and execute immediate mitigation actions. The system integrates Twilio for notifications and Stripe for payment context during response.

Do I need PostgreSQL and Redis to run incident classification and mitigation workflows?▼

Yes, PostgreSQL and Redis are required dependencies. You also need Flask, Gunicorn, Twilio, xAI, Stripe, and CRM OAuth integration to fully support incident classification, mitigation, and analysis.

What is the best way to handle incident response for InsuranceGrokBot production systems?▼

The best way to handle incident response is running a dedicated skill that classifies incidents, mitigates impact, analyzes root causes, and reports findings using Railway MCP tools and service health checks.