incidentio-integration

Query Incident.io incidents and compute MTTR and alert fatigue analytics.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill incidentio-integration-erwinv2k-tkg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incidentio-integration
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/incidentfox/sre-agent/.claude/skills/incident-incidentio
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill incidentio-integration-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, and includes scripts (resource) components.

What problem does it solve? SRE teams need quick access to incident history, resolution metrics, and alert noise patterns without manually navigating the Incident.io dashboard. This Skill provides scripted access to the Incident.io API for incident investigation and reliability analytics. ## Core Features & Use Cases - Incident Investigation: List, filter, and inspect incidents by status, severity, or date range, including timeline updates and role assignments. - MTTR Analytics: Calculate average, median, and P95 mean-time-to-resolution across incidents, optionally filtered by severity. - Alert Fatigue Detection: Analyze alert routes to identify noisy sources with high fire counts and low acknowledgment rates, including off-hours distribution. - Use Case: During a post-incident review, pull the full timeline of a specific incident, then compute 30-day MTTR by severity to assess whether response times are improving. ## Quick Start Ask the agent to list all active Incident.io incidents and calculate the MTTR for the last 30 days.

Frequently Asked Questions about incidentio-integration

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

FAQPage Schema
How do I list active incidents from Incident.io?

Run the list_incidents.py script with the --status active flag to retrieve all active incidents. You can also filter by severity ID or limit results with --max-results, and add --json for machine-readable output.

How to calculate MTTR from Incident.io incident data?

Use the calculate_mttr.py script with an optional --days parameter (default 30) and --severity-id filter. It computes average, median, P95, fastest, and slowest resolution times from closed incidents in the period.

How do I detect alert fatigue in Incident.io alert routes?

Run get_alert_analytics.py with --since and --until ISO date parameters. It reports fire counts, acknowledgment rates, and off-hours rates per route, flagging routes with more than 10 fires and under 50% acknowledgment as noisy.

Does the Incident.io integration require an API key in environment variables?

No, credentials are injected automatically by a proxy layer in production, so INCIDENTIO_API_KEY will not be visible. For direct testing mode, the client falls back to Bearer auth with INCIDENTIO_API_KEY against api.incident.io.

Why does incident listing stop before reaching my max-results value?

Pagination stops when the API returns no further cursor in pagination_meta or when no incidents remain. The scripts page through results in batches of 100 until the limit or end of data is reached.