Talking To The User

On Call

incident-io

Explains incident.io on-call schedules, overrides, cover requests and escalation paths, and how to read and change them.

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.