incident.io agent skills for Claude Code, Cursor and RevampKey

4 ready-made playbooks that teach an AI agent how to do real incident.io work: which tools to call, what to check first, and when to stop and ask you.

Download RevampKey, free I have it: connect incident.io

Connect incident.io once and all 4 skills install themselves and stay up to date. Mac, Windows and Linux.

All 4 incident.io skills

Each skill is one job. You ask in plain words and the agent loads the skill that matches, then follows its steps.

Start hereAsks before writing22 incident.io tools

Use incident.io with AI, safely

Ground rules for working with incident.io through an AI assistant: confirm the workspace, scope searches, and ask before any change to incidents, escalations or on-call.

Use it when

You just connected incident.io and want to know what the assistant can safely do
An answer came back from the wrong workspace or account and you want to prevent it
You want to find incidents or alerts without flooding the chat with thousands of records

Tools it uses

incident_list
ask_incident
incident_create
ask
ask_telemetry
alert_list
alert_source_list
alert_stats
escalation_list
escalation_show
escalation_path_list
escalation_path_show
escalation_stats
escalation_respond
follow_up_list
follow_up_stats
follow_up_create
follow_up_update
catalog_type_list
catalog_entry_list
analysis_start
feedback

Example

Which incident.io workspace am I connected to, and how many P1 incidents did we have this quarter?

You are connected to the Acme workspace. This quarter there were 23 P1 incidents, 17 of them in the last 30 days. Shall I break those down by team next? I have not changed anything.

Use in RevampKeyRead the full skill →

Asks before writing5 incident.io tools

Track follow-ups and post-mortem actions

Reviews open follow-ups and post-incident actions across recent incidents in incident.io, finds overdue, unowned and orphaned items, and drafts a chase or closure list grouped by owner. It asks before changing any follow-up.

Use it when

Before a quarterly review, to see which post-incident actions never got done
When a team asks what is still open from last month's incidents
When you want a clean-up list of stale follow-ups grouped by owner

Tools it uses

follow_up_list
follow_up_stats
incident_list
follow_up_create
follow_up_update

Example

What follow-ups from incidents in the last 90 days are still overdue, and who owns them?

I found 14 open follow-ups from the last 90 days. 6 are overdue, 3 have no owner, and 2 belong to incidents that closed months ago. Platform has the most overdue items, so I've grouped the chase list by owner and marked the 2 orphans as closure candidates. I haven't changed anything yet; tell me which to close or reassign.

Use in RevampKeyRead the full skill →

Asks before writing2 incident.io tools

Triage and update a live incident with incident.io and AI

Pulls the current state of an active incident, then proposes status, severity and action changes for you to approve before anything is written. Keeps responders aligned without guessing what has already happened.

Use it when

An outage is live and you need the current status and last update
You want to open a new incident or record a change in severity or status
You need to log an action on an incident with a clear owner

Tools it uses

incident_list
incident_create

Example

What's the state of INC-482? The checkout errors are down but I'm not sure anyone updated the incident.

INC-482 is still marked Investigating at Sev 2, and the last update was 47 minutes ago. Checkout error rates have dropped in the recent alerts, so the status looks stale. I suggest moving it to Monitoring and adding an update that the error rate has recovered. Shall I make that change, or would you like different wording first?

Use in RevampKeyRead the full skill →

Read-only7 incident.io tools

Check on-call coverage with AI

Works out who is actually on call for a team or service, checks the escalation path for single points of failure, and reviews paging patterns. Any schedule, shift or notification change is drafted first and waits for your approval.

Use it when

Before a risky deploy, to confirm someone will be reached overnight
When a page went unanswered and you need to see where it actually went
When you want to swap a shift or set a maintenance window without leaving a gap

Tools it uses

escalation_path_list
escalation_path_show
escalation_list
escalation_show
escalation_stats
alert_stats
escalation_respond

Example

Who is on call for the payments team right now, and is there anyone covering Saturday night during the database migration?

Right now the payments primary is Priya, with Marcus as the second layer. Saturday night has no overnight rota: the path ends at 18:00, so pages after that reach no one. I haven't changed anything. Would you like me to draft a shift for Marcus from 22:00 to 06:00 Saturday, for you to approve first?

Use in RevampKeyRead the full skill →

Get all 4 without copying a file

RevampKey adds the skills when you connect incident.io, updates them for you and removes them when you disconnect.

Download RevampKey

How incident.io skills work

Connect incident.io
The incident.io MCP server gives the agent its tools.
Ask in plain words
“What follow-ups from incidents in the last 90 days are still overdue, and who owns them?” Each SKILL.md says when it applies, so only the one that fits is loaded.
Approve any change
The agent calls the tools in order, checks its work, and shows you any change before it makes it.

How to install incident.io skills

In RevampKey the skills install themselves when you connect incident.io. In other tools each skill is one folder with a SKILL.md file, and you also need the incident.io MCP server connected there.

About 1 minute · nothing to copy

Download RevampKey for Mac, Windows or Linux and sign in.
Open Connectors and connect incident.io. All 4 skills come with it and stay up to date; they go away when you remove the connector.
Ask in plain language, for example “What follow-ups from incidents in the last 90 days are still overdue, and who owns them?”
Download RevampKeyConnect incident.io · 1 click
Get RevampKey to connect incident.io
RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and incident.io is one click away with its skills already attached.
Download RevampKey
Not now? Use the skills in your current tool
for s in essentials followup-and-postmortem-tracking incident-triage-and-update oncall-coverage-check; do curl -fsSL --create-dirs -o .claude/skills/incident-io-$s/SKILL.md https://revampkey.com/marketplace/incident-io/skills/$s/SKILL.md done
Other tools

Into this project’s .claude/skills folder

Connect the incident.io MCP server in Claude Code.

Run this in your project folder to add all 4 skills:

for s in essentials followup-and-postmortem-tracking incident-triage-and-update oncall-coverage-check; do
  curl -fsSL --create-dirs -o .claude/skills/incident-io-$s/SKILL.md https://revampkey.com/marketplace/incident-io/skills/$s/SKILL.md
done

Ask in plain language, for example “What follow-ups from incidents in the last 90 days are still overdue, and who owns them?”

Into the shared .agents/skills folder

Connect the incident.io MCP server in Cursor.

Run this in your project folder to add all 4 skills:

for s in essentials followup-and-postmortem-tracking incident-triage-and-update oncall-coverage-check; do
  curl -fsSL --create-dirs -o .agents/skills/incident-io-$s/SKILL.md https://revampkey.com/marketplace/incident-io/skills/$s/SKILL.md
done

Ask in plain language, for example “What follow-ups from incidents in the last 90 days are still overdue, and who owns them?”

Into the shared .agents/skills folder

Connect the incident.io MCP server in Codex.

Run this in your project folder to add all 4 skills:

for s in essentials followup-and-postmortem-tracking incident-triage-and-update oncall-coverage-check; do
  curl -fsSL --create-dirs -o .agents/skills/incident-io-$s/SKILL.md https://revampkey.com/marketplace/incident-io/skills/$s/SKILL.md
done

Ask in plain language, for example “What follow-ups from incidents in the last 90 days are still overdue, and who owns them?”

Into the shared .agents/skills folder

Connect the incident.io MCP server in VS Code.

Run this in your project folder to add all 4 skills:

for s in essentials followup-and-postmortem-tracking incident-triage-and-update oncall-coverage-check; do
  curl -fsSL --create-dirs -o .agents/skills/incident-io-$s/SKILL.md https://revampkey.com/marketplace/incident-io/skills/$s/SKILL.md
done

Ask in plain language, for example “What follow-ups from incidents in the last 90 days are still overdue, and who owns them?”

RevampKey or copy the files?

In RevampKey

One click when you connect incident.io
Updated for you when a skill improves
Removed when you disconnect
The MCP server is set up for you
800+ other connectors, same way

Download free

Copy into your project

One command per project
Run it again to get updates
You connect the incident.io MCP server yourself
Works in Claude Code, Cursor, Codex and VS Code

See the command

incident.io skills FAQ

What is a incident.io agent skill?

A SKILL.md file: a short playbook an AI agent loads when your request matches it. Each incident.io skill describes one job, which incident.io tools to use in which order, what to check first and when to stop and ask you.

Do the incident.io skills change anything on their own?

1 of the 4 only read. The others tell the agent to show you the change and wait for a yes before it creates, edits or deletes anything in incident.io.

Which tools can use these skills?

Any agent that reads the open Agent Skills format: Claude Code, Cursor, Codex, VS Code with Copilot and RevampKey. In RevampKey they are attached when you connect incident.io; elsewhere you copy the folders into your project or skills directory.

Do I need the incident.io MCP server too?

Yes. The skills tell the agent how to do the work; the incident.io MCP server gives it the tools to do it. The incident.io MCP setup guide covers every client.

incident.io MCP server setup · This page as Markdown

Put incident.io’s best workflows in your agent

Download RevampKey, connect incident.io and ask your first question in about a minute.

Download RevampKey Connect incident.io · 1 click

All 4 incident.io skills

Use incident.io with AI, safely

Use it when

Tools it uses

Track follow-ups and post-mortem actions

Use it when

Tools it uses

Triage and update a live incident with incident.io and AI

Use it when

Tools it uses

Check on-call coverage with AI

Use it when

Tools it uses

Get all 4 without copying a file

How incident.io skills work

How to install incident.io skills

RevampKey or copy the files?

In RevampKey

Copy into your project

incident.io skills FAQ

Put incident.io’s best workflows in your agent

Skills for related tools