메뉴
Incident.io incident management and analytics. Use for listing, searching, and analyzing incidents. Supports MTTR calculations, severity analysis, and alert fatigue detection via alert route analytics.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Pull incident context from alerting platforms (PagerDuty). Use when investigating who's on-call, incident history, alert patterns, or MTTR metrics.
Opsgenie alert management and on-call scheduling. Use for listing alerts, checking on-call, computing MTTA/MTTR, and alert fatigue analysis. Supports team and priority filtering.
Amplitude product analytics. Use when querying user events, funnels, retention, or product usage data. Provides event segmentation, user activity lookup, and annotation queries.
Google BigQuery data warehouse queries and schema inspection. Use when running SQL queries, listing datasets/tables, or inspecting table schemas in BigQuery.
MySQL/MariaDB database inspection and queries. Use when investigating table schemas, running queries, checking processlist, replication status, InnoDB engine status, or lock contention.
PostgreSQL database inspection and queries. Use when investigating table schemas, running queries, checking locks, replication status, or long-running queries.
| name | incident-incidentio |
| description | Incident.io incident management and analytics. Use for listing, searching, and analyzing incidents. Supports MTTR calculations, severity analysis, and alert fatigue detection via alert route analytics. |
| allowed-tools | Bash(python *) |
IMPORTANT: Credentials are injected automatically by a proxy layer. Do NOT check for INCIDENTIO_API_KEY in environment variables - they won't be visible to you. Just run the scripts directly; authentication is handled transparently.
Configuration environment variables you CAN check (non-secret):
INCIDENTIO_BASE_URL - Proxy base URL (set automatically in production)All scripts are in .claude/skills/incident-incidentio/scripts/
python .claude/skills/incident-incidentio/scripts/list_incidents.py [--status STATUS] [--severity-id ID] [--max-results N]
# Examples:
python .claude/skills/incident-incidentio/scripts/list_incidents.py --status active
python .claude/skills/incident-incidentio/scripts/list_incidents.py --status resolved --max-results 20
python .claude/skills/incident-incidentio/scripts/get_incident.py --incident-id INCIDENT_ID
python .claude/skills/incident-incidentio/scripts/get_incident_updates.py --incident-id INCIDENT_ID [--max-results 50]
python .claude/skills/incident-incidentio/scripts/list_incidents_by_date_range.py --since "2024-01-01T00:00:00Z" --until "2024-01-31T23:59:59Z" [--status STATUS] [--max-results N]
python .claude/skills/incident-incidentio/scripts/list_severities.py
python .claude/skills/incident-incidentio/scripts/list_incident_types.py
python .claude/skills/incident-incidentio/scripts/get_alert_analytics.py --since "2024-01-01T00:00:00Z" --until "2024-01-31T23:59:59Z"
python .claude/skills/incident-incidentio/scripts/calculate_mttr.py [--severity-id ID] [--days 30]
1. List recent incidents:
list_incidents.py --status active
2. Get incident details:
get_incident.py --incident-id <id>
3. Review timeline:
get_incident_updates.py --incident-id <id>
4. Compute MTTR for severity assessment:
calculate_mttr.py --days 30
1. Get alert analytics for the period:
get_alert_analytics.py --since "2024-01-01T00:00:00Z" --until "2024-01-31T23:59:59Z"
2. Review noisy routes (high fire count, low ack rate)
3. Check historical MTTR by severity:
calculate_mttr.py --severity-id <sev_id>