On Call
by incident-ioc8e50a4a7a06No license2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today
Who is on call in incident.io and how they get paged: schedules, rotas and shifts, overrides, cover requests, escalation paths, and pages (escalations). Use whenever you're working with any of these in any way, including plain reads ("who's on call tonight?", "when am I next on?") and paging ("page Ava", "ack my page", "has anyone acked?"). Load it before the first schedule, escalation or cover-request tool call: the tools return raw shifts and levels, and this skill says how to read them.
- c8e50a4a7a06Currentcommit c8e50a4Published Oct 8, 2026
Source and attribution
Source:incident-io/skillsinplugins/incident-io/skills/on-callat commitc8e50a4
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from incident-io/skills
Talking To The User
incident-io
How the incident.io skills speak to the person in the session: what the user hears and what goes in the record, ending each reply with one next step, keeping a fixed milestone list through a multi-step job, and using the user's words instead of the skills' own vocabulary. Load it before you reply to the user while running any other incident.io skill.
Architecture Author
incident-io
Writes and maintains architecture documentation describing systems, their locations, dependencies and real resource names.
Skill Authoring
incident-io
Create and improve the skills in your own plugins — the ones incident.io's agents and your coding agents load. Use whenever you're writing, editing, or reviewing a skill in any way: creating one, improving one from usage feedback or a review brief, or asking what makes a good skill.
Extensions Review
incident-io
Review what your extensions did over a period: the skill loads that made a real difference, told through the incident or conversation each one happened in, and the incidents no skill or runbook covered. Use whenever anyone wants a review, digest, or pulse of extension or skill usage over a window — "how did our skills do this week", "post yesterday's extensions review to our channel" — one-off or on a schedule. Whether the estate is healthy (sync state, funnels, issues to fix) is the doctor skill, not this one.
Extensions
incident-io
Understand the extensions so that you can help a user configure and manage their incident.io agent estate. Use whenever you're working with incident.io plugins, skills, connectors or MCPs in any way ("I want to set up an incident plugin"), when someone new wants to give incident.io's agents their own knowledge and doesn't yet know the pieces, or when you need to understand the user's existing configuration before editing a plugin or skill.
Doctor
incident-io
Reviews the health of an incident.io agent estate — plugins, skills and connections — and routes each finding to whatever fixes it.
More in DevOps & Cloud
Playwright Devops
microsoft
DevOps workflows for Playwright: analyze GitHub Actions failures for the last commit on main and fetch failed job logs.
M5 Onboard
anthropics
Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.
Yeet
openai
Stages, commits, pushes, and opens or updates a GitHub pull request in one flow using the GitHub CLI.
Runbook
anthropics
Creates or updates step-by-step operational runbooks for recurring tasks, including troubleshooting, rollback and escalation.
Incident Response
anthropics
Guides an incident response workflow: severity triage, status updates, mitigation tracking, and blameless postmortems.
Deploy Checklist
anthropics
Generates a pre-deployment readiness checklist covering pre-deploy, deploy, post-deploy and rollback triggers.