Paymahn Moghadasian

You can manage incidents, actions, follow-ups, alerts, alert sources and routes, escalations, on-call schedules, catalog types and entries, custom fields, severities, incident types, roles, statuses, status pages with subscribers and templates, users, teams, API keys, heartbeats, maintenance windows, and settings.

It targets site reliability engineers, incident responders, and platform teams who administer incident.io. Anyone needing terminal access to incident data, on-call schedules, status page management, or dashboard settings benefits from its generated and hand-curated commands.

It uses the public Bearer API through OpenAPI-generated commands for documented endpoints, plus cookie-based authentication for internal dashboard commands generated from captured HAR files. A raw escape hatch command handles any path not yet codified.

Yes. It supports creating and managing public status pages, including components, layout, subscribers, and templates. You can list status page subscribers and configure page structure directly from the command line using the dedicated status page commands.

The skill includes a raw escape hatch command that lets you hit any un-codified incident.io path directly. This covers internal dashboard endpoints or newly released API routes not yet represented by the generated or hand-curated command set.