triage-incident
Analyze incidents in Alert stage and suggest severity, business impact, affected services, communications, and response team. Use when triaging incidents, evaluating incident severity, or when the user asks to analyze incident impact.
How do I install this agent skill?
npx skills add https://github.com/revitalb-port/skills-registry-demo --skill triage-incidentIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill triages production incidents by processing external alert data and service information from the Port platform. It is susceptible to indirect prompt injection if malicious content is included in incident descriptions or alerts, which could potentially influence the suggested severity or draft public status page communications.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Triage Incident Skill
Triage production incidents using AI analysis to suggest severity, calculate business impact, and draft communications.
When to Use
- Incident is in Alert stage and needs triage
- Analyzing incident severity or impact
- Preparing incident for investigation phase
Triage Process
Step 1: Gather Context
Collect via Port MCP:
- Incident details: Title, description, alert source
- Primary service: Tier, dependencies, ownership
- Monitoring data: Error rates, affected customers
- Timing: Business hours vs off-hours
Step 2: Determine Severity
| Level | Criteria | Examples |
|---|---|---|
| Sev1 | Complete tier1 outage, >$10K/hour | Database crash, auth broken |
| Sev2 | Partial tier1 or tier2 outage | Payments failing, search down |
| Sev3 | Minor degradation, internal | Slow dashboard, export broken |
| Sev4 | Minimal impact, cosmetic | UI typo, styling bug |
Step 3: Calculate Business Impact
Provide:
- Customer impact (estimated users)
- Revenue impact ($/hour)
- SLA implications
- Reputation risk
Step 4: Recommend Response Team
Query Port for:
- Service's
on_callrelation - Service
ownerrelation - Team escalation for sev1/sev2
Step 5: Draft Communications
Internal message:
🚨 Incident: [Title]
Severity: [Level]
Impact: [Brief description]
Response: [Owner] leading, [Team] engaged
ETA: [Timeline]
Status page (customer-facing):
We're experiencing issues with [feature].
Our team is actively working on a fix.
We'll provide an update within [time].
Step 6: Submit via Port Action
Call update_incident_triage with:
ai_suggested_severitybusiness_impactinternal_comms_messagestatus_page_messageai_suggested_ownerai_suggested_response_team
Port MCP Queries
list_entities(blueprint="incident", identifiers=["incident-id"])
list_entities(blueprint="service", include=["on_call", "owner", "team"])
list_entities(blueprint="deployment", query={service: "x", deployed_at: ">1h ago"})
Quality Checklist
- Severity rationale is data-driven
- Impact includes metrics
- Found actual on-call via Port
- Messages are clear and actionable
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/revitalb-port/skills-registry-demo/triage-incident">View triage-incident on skillZs</a>