Structure evidence-first incident response and generate an incident-report artifact.
npx skills add https://github.com/vTRKA/supervibe --skill incident-response-vtrka
Please help me install this Agent Skill. Skill: incident-response Source: https://github.com/vTRKA/supervibe/tree/main/skills/incident-response Command: npx skills add https://github.com/vTRKA/supervibe --skill incident-response-vtrka
Incident Response turns chaotic, unstructured debugging during production, security, or data events into a disciplined workflow that prioritizes containment, mitigation, verification, communication, and learning capture with durable evidence.
incident-report artifact from the repo’s durable template and requires timeline, impact, mitigation evidence, rollback/forward-fix plan, root-cause status, follow-ups, residual risk, and artifact path.Use incident-response when a production outage, security concern, data integrity issue, degraded service, or alert false alarm requires a severity triage and an evidence-based incident report.
High-intent search queries and answers about installing and using this skill.
Incident response triage classifies production outages by severity and type, driving a structured decision path that prioritizes evidence-backed containment, mitigation, and verification before deeper root-cause analysis.
Stabilizing a security incident requires separating immediate containment from mitigation, enforcing reversible harm reduction early, and grounding all actions in preserved logs and traces before verifying completion.
Generating an incident report artifact requires capturing structured fields including timeline, impact, mitigation evidence, rollback or forward-fix plan, root-cause status, and residual risk directly from the incident workflow.
Incident response handles false alarms and degraded services alongside full outages by applying severity triage to classify the event type and driving the appropriate response cadence and decision path.
Managing escalation during a data integrity incident involves following severity-based communication cadences, respecting approval boundaries, and applying redaction expectations to updates to prevent sensitive data exposure.
A rollback is executed when reversible harm reduction is needed to stabilize quickly, whereas a forward-fix is chosen when the mitigation evidence supports applying a corrective update directly to resolve the incident.
valithedgeTriage Dispatcher Apache HTTP Server incidents in AMS environments using MCP evidence.
emilneuraz-aiAutomate blameless postmortems with root cause analysis, timelines, and follow-ups.
FoundationForgeManage incident response workflows for production outages and alerts.
AI-Foundry-CoreDraft blameless postmortems with root cause analysis, timelines, and action items.