SRE Engineer
Jeffallan/claude-skills
Defines SLIs, SLOs and error budgets, and sets up golden-signal monitoring, blameless postmortems, toil automation and chaos experiments for production systems.
Production incident response. An agent skill from borghei/Claude-Skills.
Install Incident Commander
$ npx skills add borghei/Claude-Skills --skill incident-commander -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills incident-commander --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/incident-commander .claude/skills/incident-commander && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "incident-commander" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/incident-commander into .claude/skills/incident-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-commander", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/engineering/incident-commanderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill incident-commander -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills incident-commander --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering/incident-commander .agents/skills/incident-commander && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "incident-commander" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/incident-commander into .agents/skills/incident-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-commander", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill incident-commander -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills incident-commander --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering/incident-commander .cursor/skills/incident-commander && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "incident-commander" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/incident-commander into .cursor/skills/incident-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-commander", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path engineering/incident-commander--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill incident-commander -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills incident-commander --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering/incident-commander .gemini/skills/incident-commander && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "incident-commander" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/incident-commander into .gemini/skills/incident-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-commander", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills incident-commanderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill incident-commander -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering/incident-commander .github/skills/incident-commander && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "incident-commander" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/incident-commander into .github/skills/incident-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-commander", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill incident-commander -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills incident-commander --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering/incident-commander .opencode/skills/incident-commander && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "incident-commander" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/incident-commander into .opencode/skills/incident-commander/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-commander", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
incident-commander- GitHub stars
- 881
- Token cost
- ~1.8k tokens
- SKILL.md length
- 638 words
- Files
- 27 (incl. scripts, references, assets)
- Skills in repo
- 349
- Repo updated
- First seen
- Licence
- MIT
At a glance
Production incident response. An agent skill from borghei/Claude-Skills.
- Handling incidents
- SKILL.md covers Core Capabilities, When to Use, Clarify First and Tools, plus 3 more sections
- Calls python
- Classifying severity
What it does
Incident Commander is an agent skill from borghei/Claude-Skills. Production incident response. Use when handling incidents, classifying severity, reconstructing timelines, writing postmortems, generating comms templates, or building response playbooks with severity scoring and RCA frameworks.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 29 other files, including scripts, reference files and assets (for example `README.md`, `assets/incident_report_template.md` and `assets/runbook_template.md`).
It sits in DevOps & Cloud, covering Incident response, Runbooks and postmortems and Site reliability engineering. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Handling incidents
- Classifying severity
- Reconstructing timelines
- Writing postmortems
Example prompts
- “/incident-commander”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Incident Commander loads about 1.8k tokens when it runs, and up to ~26k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 638 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 638 words, ~1,783 tokens.
Download SKILL.mdSave it as
.claude/skills/incident-commander/SKILL.md (or your agent's skills folder). This skill also uses 26 other files; get the full folder from GitHub.- name
- incident-commander
- description
- Production incident response. Use when handling incidents, classifying severity, reconstructing timelines, writing postmortems, generating comms templates, or building response playbooks with severity scoring and RCA frameworks.
- license
- MIT + Commons Clause
- metadata.version
- 1.2.0
- metadata.author
- borghei
- metadata.category
- engineering
- metadata.domain
- incident-response
- metadata.tier
- POWERFUL
- metadata.updated
- 2026-06-17
- metadata.tags
- incident-response, severity-classification, rca, postmortem
- metadata.python-tools
- incident_classifier.py, severity_classifier.py, timeline_reconstructor.py, incident_timeline_builder.py, pir_generator.py, postmortem_generator.py
- metadata.tech-stack
- python, json, markdown
Incident Commander
Classify incident severity, reconstruct timelines from heterogeneous event sources, and generate structured post-incident reviews with root cause analysis and action items. Codifies PagerDuty, Google SRE, and Atlassian incident-management practices into severity scoring, escalation matrices, communication templates, RCA frameworks, and SLA/error-budget tracking.
Core Capabilities
- Severity classification — multi-dimensional scoring (revenue, user scope, data/security risk, service criticality, blast radius) into SEV-1 to SEV-4 with confidence and escalation paths.
- Timeline reconstruction — chronological timelines from logs, alerts, Slack, and deploy events with phase detection and gap analysis.
- Post-incident review — PIRs with 5 Whys, Fishbone, Timeline, or Bow Tie RCA plus categorized action items (owner, priority, deadline).
- Postmortem quality — coverage-gap detection, action-item quality scoring, MTTD/MTTR benchmarking.
- Communication & escalation — severity-specific internal/executive/customer/status-page templates; technical (L1-L4) and business escalation matrices with time-based triggers.
- SLA / error-budget tracking — SLI/SLO/SLA hierarchy, error budgets, burn-rate alerting, and breach handling.
When to Use
- Handling an active incident — classify severity, establish command, mitigate, communicate.
- Running a post-incident review — reconstruct timeline, perform RCA, assign action items.
- Managing escalation — apply technical and business escalation paths by severity and elapsed time.
- Building or auditing response playbooks, comms templates, or SLA/error-budget policy.
Clarify First
Before producing the artifact, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Task & deliverable — classify severity, reconstruct a timeline, or generate a PIR/postmortem (selects
severity_classifier.pyvstimeline_reconstructor.pyvspir_generator.py/postmortem_generator.py) - Incident input data — the incident/events JSON with severity dimensions (revenue, user scope, data/security risk, blast radius) (the input the scripts parse)
- RCA method — 5 Whys, Fishbone, Timeline, or Bow Tie (sets
pir_generator.py --rca-methodand the postmortem structure)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Tools
| Tool | Purpose | Command |
|---|---|---|
incident_classifier.py | Classify severity, recommend response teams and comms templates | python scripts/incident_classifier.py --input incident.json --format text |
severity_classifier.py | Multi-dimensional severity score with escalation path | python scripts/severity_classifier.py incident.json --format markdown |
timeline_reconstructor.py | Reconstruct timeline from timestamped events with phase + gap analysis | python scripts/timeline_reconstructor.py --input events.json --detect-phases --gap-analysis --format markdown |
incident_timeline_builder.py | Build structured timeline with MTTD/MTTR and comms templates | python scripts/incident_timeline_builder.py incident_data.json --format markdown |
pir_generator.py | Generate Post-Incident Review with RCA and action items | python scripts/pir_generator.py --incident incident.json --rca-method fishbone --action-items |
postmortem_generator.py | Generate postmortem with 5-Whys, benchmarks, coverage gaps | python scripts/postmortem_generator.py incident_data.json --format markdown |
Show full SKILL.md (259 more words)Show less
References
Load the reference that matches the task — keep this file lean and pull detail on demand:
- references/response-playbooks.md — quick-start commands, the detection-to-resolution and post-incident-review workflows, escalation management, anti-patterns, and tool troubleshooting. Read when running an incident end-to-end or using the scripts.
- references/incident-response-framework.md — PagerDuty/Google SRE/Atlassian framework comparison, role definitions (IC, Comms, Ops, Scribe, SME, Liaison), communication protocols, escalation matrix, and the 7-phase incident lifecycle. Read when designing the response process or assigning roles.
- references/incident_severity_matrix.md — full SEV-1 to SEV-4 impact criteria, response requirements, escalation paths, classification guidelines, decision tree, and examples. Read when classifying or calibrating severity.
- references/communication_templates.md — ready-to-use internal, executive, customer, status-page, escalation, and resolution templates by severity. Read when drafting any incident communication.
- references/rca_frameworks_guide.md — step-by-step 5 Whys, Fishbone, Timeline, and Bow Tie frameworks with templates, selection guidance, and anti-patterns. Read when performing root cause analysis.
- references/sla-management-guide.md — SLI/SLO/SLA hierarchy, error-budget policy, burn-rate alerting, breach handling, and incident-to-SLA mapping with worked examples. Read when assessing or communicating SLA impact.
Scope & Limitations
Covers: severity classification, timeline reconstruction, PIR/postmortem generation, RCA frameworks, escalation matrices, communication templates, and SLA/error-budget tracking. Tools are deterministic stdlib Python (no ML/LLM calls), accepting JSON input and emitting text/JSON/markdown.
Does NOT cover: live monitoring/alerting infrastructure (feeds in from senior-devops), security forensics (see senior-secops), or deployment/rollback execution (see release-orchestrator).
Integration Points
| Skill | Integration |
|---|---|
senior-devops | Monitoring alerts feed timeline; runbook templates inform playbooks |
senior-secops | Security incidents auto-escalate to SEV-1; breach indicators trigger SecOps response |
release-orchestrator | Deployment events feed timeline; rollback data informs release gates |
senior-architect | Architectural root causes escalate to architecture review |
code-reviewer | PIR action items route to code review workflows |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 26 other files (scripts, references, assets) in engineering/incident-commander of borghei/Claude-Skills.
- SKILL.md
- README.md
- assets/incident_report_template.md
- assets/runbook_template.md
- assets/sample_incident_classification.json
- assets/sample_incident_data.json
- assets/sample_incident_pir_data.json
- assets/sample_timeline_events.json
- assets/simple_incident.json
- assets/simple_timeline_events.json
- expected_outputs/incident_classification_text_output.txt
- expected_outputs/pir_markdown_output.md
- expected_outputs/simple_incident_classification.txt
- expected_outputs/timeline_reconstruction_text_output.txt
- references/communication_templates.md
- references/incident-response-framework.md
- references/incident_severity_matrix.md
- references/rca_frameworks_guide.md
- … and 9 more
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Incident Commander next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Incident Commander this skillborghei/Claude-Skills | 881 | — | ~1.8k | Automated safety check: Pass | MIT | |
| SRE EngineerJeffallan/claude-skills | 12k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Incident ResponderDokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI | 507 | — | ~706 | Automated safety check: Pass | Custom licence | |
| Eng Runbooksanqiufong/slides-from-anything | 132 | 1 repos | ~380 | Automated safety check: Pass | Apache-2.0 | |
| Incident Slo Runbookmajiayu000/spellbook | 286 | — | ~460 | Automated safety check: Pass | MIT | |
| Langchain Incident Runbookjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
Incident Responder
Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Expert SRE incident responder specializing in rapid problem resolution.
Eng Runbook
sanqiufong/slides-from-anything
An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist.
Incident Slo Runbook
majiayu000/spellbook
Create or audit SLOs, SLIs, alert rules, incident response steps, escalation paths, postmortems, operational runbooks, and customer-impact communication.
Langchain Incident Runbook
jeremylongshore/tons-of-skills-marketplace
Triage LangChain 1.0 / LangGraph 1.0 production incidents — LLM-specific SLOs, provider outage runbook, latency spike decision tree, cost-overrun response, agent loop containment.
Observability And Reliability
cbrock84/headcount
Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure.
More from borghei/Claude-Skills
All 349 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Incident Commander
What does Incident Commander do?
Production incident response. An agent skill from borghei/Claude-Skills. Incident Commander is an agent skill from borghei/Claude-Skills. Production incident response.
When should I use Incident Commander?
Incident Commander fits situations like: handling incidents; classifying severity; reconstructing timelines; writing postmortems.
How do I install Incident Commander in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill incident-commander -a claude-code`. Or copy the skill folder (engineering/incident-commander in borghei/Claude-Skills) into .claude/skills/incident-commander in your project. Claude Code loads it when a task matches its description.
How do I install Incident Commander in Codex?
Run `npx skills add borghei/Claude-Skills --skill incident-commander -a codex`. Or copy the skill folder (engineering/incident-commander in borghei/Claude-Skills) into .agents/skills/incident-commander in your project. Codex loads it when a task matches its description.
Can I use Incident Commander in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill incident-commander -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/incident-commander, .gemini/skills/incident-commander, .github/skills/incident-commander and .opencode/skills/incident-commander in your project.
What does Incident Commander need to run?
Going by SKILL.md and its folder, Incident Commander needs the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Incident Commander access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Incident Commander safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Incident Commander use?
Incident Commander is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Incident Commander use?
About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 24k tokens, read only when the agent opens those files.
What are the alternatives to Incident Commander?
Skills that share tags, products or a category with Incident Commander: SRE Engineer (Jeffallan/claude-skills, 12k stars), Incident Responder (Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI, 507 stars), Eng Runbook (sanqiufong/slides-from-anything, 132 stars) and Incident Slo Runbook (majiayu000/spellbook, 286 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Incident Commander?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.