Incident Response

Community

korallis

incident-response

Respond to production incidents systematically with triage, investigation, resolution, and post-mortem analysis to minimize downtime and prevent recurrence. Use when handling production outages, triaging incidents, investigating critical bugs, coordinating incident response, implementing hotfixes, conducting post-mortems, or establishing incident response procedures.

Overview

Publisher	korallis
Repository	`Droidz`
Skill name	`incident-response`
Stars	89
Forks	9
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by korallis on GitHub. Read the source before you install it.

Installation

Install the Incident Response AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/korallis/Droidz/tree/main/droidz_installer/payloads/claude/default/skills/incident-response

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/korallis/Droidz.git /tmp/Droidz
mkdir -p .claude/skills
cp -r /tmp/Droidz/droidz_installer/payloads/claude/default/skills/incident-response .claude/skills/incident-response

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Incident Response in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Incident Response on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Incident Response is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Incident Response - Production Issue Management

When to use this skill

Responding to production outages
Triaging critical incidents
Investigating high-severity bugs
Coordinating incident response teams
Implementing emergency hotfixes
Conducting post-mortem analyses
Establishing incident response procedures
Communicating status during incidents
Creating runbooks for common issues
Implementing rollback strategies
Documenting incident timelines
Preventing incident recurrence

When to use this skill

Responding to outages, managing incidents, conducting postmortems.
When working on related tasks or features
During development that requires this expertise

Use when: Responding to outages, managing incidents, conducting postmortems.

Incident Response Process

1. Detect

Monitoring alerts
User reports
Automated checks

2. Triage

Assess severity (P0-P4)
Page on-call engineer
Create incident channel

3. Mitigate

Rollback to last known good
Scale resources
Apply hotfix
Communicate status

4. Resolve

Verify fix
Monitor metrics
Update status page
Close incident

5. Postmortem

Timeline of events
Root cause analysis
Action items
Follow-up tasks

Severity Levels

P0 (Critical): Complete outage, data loss
P1 (High): Major feature broken, revenue impact
P2 (Medium): Degraded performance, workaround exists
P3 (Low): Minor bug, cosmetic issue
P4 (Informational): Enhancement request

Example Runbook

```markdown

High CPU Usage Runbook

Symptoms

Server CPU > 90%
Slow response times
Request timeouts

Investigation

Check top processes: `top`
Check memory: `free -h`
Check logs: `tail -f app.log`

Mitigation

Scale horizontally: Add servers
Restart service: `systemctl restart app`
Rate limit: Enable aggressive rate limiting

Resolution

Identify root cause (N+1 query, memory leak, etc.)
Deploy fix
Monitor for 1 hour ```

Communication Template

``` [INCIDENT] Service X degraded

Status: Investigating Impact: 20% of users seeing slow load times ETA: 30 minutes

Updates:

10:00 AM: Issue detected
10:05 AM: On-call paged, investigation started
10:15 AM: Root cause identified (database bottleneck)
10:30 AM: Fix deployed, monitoring

Next update: 11:00 AM ```

Frequently asked questions

What does the Incident Response AI skill do?

Why use Incident Response on TypingMind?

Because you install it once and use it with any model. Incident Response is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Incident Response in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/korallis/Droidz/tree/main/droidz_installer/payloads/claude/default/skills/incident-response. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Incident Response?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Incident Response?

As many as you like. As long as a model supports skills, you can use Incident Response with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Incident Response AI skill free?

It is published on GitHub by korallis. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Caveman Discover

JuliusBrussee

CommunityPopular

Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.

Caveman Manage

Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.

Caveman Setup

Wire a repository through the Caveman Cloud gateway so every LLM request is measured, with no behavior change. Use for "set up caveman" or adding LLM spend observability.

Eng Runbook

An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Incident Response - Production Issue Management

When to use this skill

When to use this skill

Incident Response Process

1. Detect

2. Triage

3. Mitigate

4. Resolve

5. Postmortem

Severity Levels

Example Runbook

High CPU Usage Runbook

Symptoms

Investigation

Mitigation

Resolution

Communication Template

Resources

Frequently asked questions

Related AI Skills

Set up your own AI workspace now