Triage incident

Skill contextosai/skills/skills/triage-incident

A collection of Agent Skills — self-contained folders that teach AI agents to perform specialized tasks. Includes a production-readiness harness-audit skill, a plugin marketplace, a SKILL.md spec, and CI validation.

Install

npx -y skills add contextosai/skills --skill triage-incident

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Triage an active or recent software production incident by establishing impact, stabilizing the system, preserving evidence, building a timestamped timeline, coordinating hypotheses, and choosing reversible mitigations. Use when users report an outage, severe degradation, security or data-integrity event, broken deployment, elevated errors, or ask for incident command, status assessment, mitigation, or investigation support. Prioritize user harm reduction over root-cause completeness and require explicit authority for production mutations.

SKILL.md

3.0 KB, as published. Nobody here has run it

Triage an Incident

Reduce harm first, preserve the ability to learn why, and keep facts distinct from hypotheses.

Protocol

Establish whether the event is active. Record start/detection time, affected users/regions/intents, symptom, severity signals, and current owner. Use absolute timestamps with timezone.
Define impact in user and business terms. Separate confirmed impact from suspected blast radius and monitoring artifacts.
Freeze unnecessary changes and preserve volatile evidence: deploy/version identifiers, flags/config, traces, logs, metrics, queue depth, resource state, and recent changes. Redact sensitive data.
Identify the failing boundary and healthy comparison: region, tenant, version, route, dependency, data partition, or time window.
Choose the safest reversible mitigation that reduces harm fastest: disable a feature, shed load, fail closed/open according to risk, route traffic, rollback code/config, pause writes, or degrade functionality. State expected signal, abort threshold, and recovery path before acting.
Do not mutate production without explicit authority. When authorized, make one controlled change at a time and timestamp the observation window.
Maintain competing hypotheses and discriminating evidence. Do not let the most senior or most recent theory become fact by repetition.
Reassess impact after mitigation. Watch for silent corruption, backlog, retries, secondary saturation, or delayed consumers after headline metrics recover.
Declare stabilization only when user-impact and system-health signals remain within stated bounds for an appropriate window. Hand off residual recovery, root-cause investigation, and evidence retention explicitly.

Communication discipline

Use references/incident-record.md as the shared source of truth.
Publish facts, actions, owners, timestamps, and next update time. Avoid raw speculation in stakeholder updates.
Mark decisions with rationale and the evidence expected to confirm or reverse them.
Never expose credentials, exploit details, private user data, or sensitive internal identifiers in broad updates.

Exit conditions

End triage with current severity, confirmed impact, mitigation state, residual risk, recovery owner, next checkpoint, and whether root-cause work is separate. Do not declare resolution merely because alert volume dropped.