AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

incident-commander

Use when declaring or running a production incident or outage, or writing its post-incident review. Classifies severity with incident_classifier.py, rebuilds the timeline with timeline_reconstructor.py and drafts the PIR with pir_generator.py. Security incidents: incident-response.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--incident-commander at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 14

expected_outputs/incident_classification_text_output.txt

============================================================ INCIDENT CLASSIFICATION REPORT

CLASSIFICATION: Severity: SEV1 Confidence: 100.0% Reasoning: Classified as SEV1 based on: keywords: timeout, 500 error; user impact: 80% Timestamp: 2026-02-16T12:41:46.644096+00:00

RECOMMENDED RESPONSE: Primary Team: Analytics Team Supporting Teams: SRE, API Team, Backend Engineering, Finance Engineering, Payments Team, DevOps, Compliance Team, Database Team, Platform Team, Data Engineering Response Time: 5 minutes

INITIAL ACTIONS:

  1. Establish incident command (Priority 1) Timeout: 5 minutes Page incident commander and establish war room

  2. Create incident ticket (Priority 1) Timeout: 2 minutes Create tracking ticket with all known details

  3. Update status page (Priority 2) Timeout: 15 minutes Post initial status page update acknowledging incident

  4. Notify executives (Priority 2) Timeout: 15 minutes Alert executive team of customer-impacting outage

  5. Engage subject matter experts (Priority 3) Timeout: 10 minutes Page relevant SMEs based on affected systems

COMMUNICATION: Subject: 🚨 [SEV1] payment-api - Database connection timeouts causing 500 errors fo... Urgency: SEV1 Recipients: on-call, engineering-leadership, executives, customer-success Channels: pager, phone, slack, email, status-page Update Frequency: Every 15 minutes

============================================================