skills.rest
paymog
paymogCOMMUNITY
Explore all skills by this author →
GitHub

incidentio-cli

Drive the incident.io API through the incidentio CLI for incidents, alerts, catalog, and status pages.

Updated Jul 7, 2026
Search Tags:#api#cli#alerting#on-call#incident management#incident.io#status pages
One-click install
npx skills add https://github.com/paymog/incidentio-cli --skill incidentio-cli-paymog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incidentio-cli
Source: https://github.com/paymog/incidentio-cli/tree/main/skills/incidentio-cli
Command: npx skills add https://github.com/paymog/incidentio-cli --skill incidentio-cli-paymog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing incident.io resources through the web dashboard is slow and hard to automate. This Skill lets you operate the full incident.io API surface from the terminal — incidents, alerts, on-call schedules, catalog entries, status pages, workflows, and internal dashboard endpoints — using a single CLI with Bearer-key or browser-session auth. ## Core Features & Use Cases - Full API coverage: ~324 commands generated from incident.io's official OpenAPI specs, covering incidents, actions, follow-ups, alerts, alert routes, escalations, schedules, catalog types/entries, custom fields, severities, status pages, workflows, users, teams, secrets, and maintenance windows. - Internal dashboard endpoints: Cookie-authenticated commands (marked 🍪) unlock capabilities the public API lacks, such as creating status pages and components, catalog-backed custom fields, alert-route custom-field bindings, policies, insights, and AI incident suggestions. - Raw escape hatch: incidentio raw <METHOD> </path> probes any un-codified endpoint with stored credentials, with auth mode inferred from the path. - Use Case: Declare an incident, page the on-call schedule, publish a status-page update, and create follow-up actions — all scripted in one shell session without opening the dashboard. ## Quick Start Ask the assistant to list your open incidents by running incidentio incidents list with a live status filter after storing your API key with incidentio auth set.

Frequently Asked Questions about incidentio-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate the incidentio CLI with the incident.io API?▼

Create an API key at Settings → API keys in app.incident.io, then run incidentio auth set <api-key> to store it. Alternatively pass --api-key per command or export INCIDENT_API_KEY; scopes are fixed at key creation.

How do I list and filter incidents from the command line?▼

Run incidentio incidents list with bracket-style query filters, for example --query 'status_category[one_of]=live' or --query 'created_at[date_range]=2026-06-01~2026-06-30'. Output is JSON you can pipe to jq, and pagination uses the after cursor from pagination_meta.

Can the incident.io public API create status pages and components?▼

No. Creating status pages, components, and layout structures is internal-only and requires a browser session imported via incidentio auth import from a Copy-as-cURL request. The public Bearer API can only list pages and publish incidents or maintenance.

Why do dashboard commands return 401 No authorization material?▼

Internal app.incident.io/api endpoints reject API keys and need a valid browser session cookie. Re-import a fresh Copy-as-cURL from a logged-in tab with incidentio auth import, and set the org id via auth set-org or --org.

What does HTTP 403 mean when calling incident.io endpoints?▼

A 403 means your API key lacks the scope the endpoint requires, such as calling incidents create with a read-only key. Scopes are fixed at key creation, so rotate or create a new key with the needed scopes in the dashboard.

How do I call an incident.io endpoint that has no CLI command?▼

Use incidentio raw <METHOD> </path>, which sends any request with your stored credentials and infers cookie versus bearer auth from the path. Probe with an empty body to learn required fields from the 422 validation error.

Related Skills

Explore More Software Engineering Skills→
sunzcdevsunzcdev

test-release

Verify released Archon binaries via brew or curl install paths.

Community
Advanced
allthingslinuxallthingslinux
1

alert-management

Route alerts and coordinate incidents across PagerDuty, Alertmanager, and Slack.

Official
Advanced
acedergrenacedergren

api-audit

Catalog Fastify API routes, plugins and shared type definitions to detect mismatches and generate a cross-reference report.

Community
Advanced
john-data-chenjohn-data-chen
2

github-issues

Create, triage, label, and assign GitHub issues via gh or REST API.

Community
Advanced