Skip to main content
NeVibeCode · 17 items

Skills and MCP tagged “incident-response”

17 items
memory-forensics Dávid Balatoni skill This skill covers RAM capture and memory-dump analysis, including process review, injection checks, network traces, and malware artifacts. Claude Code CX Codex Cursor 11,027installs incident-runbook-templates Seth Hobson skill This skill builds step-by-step incident runbooks for detection, triage, mitigation, recovery, escalation, and status updates. Claude Code CX Codex Cursor 10,900installs postmortem-writing Seth Hobson skill This skill turns incident reviews into blameless postmortems with timelines, root-cause analysis, and concrete follow-up actions. Claude Code CX Codex Cursor 10,800installs on-call-handoff-patterns Seth Hobson skill This skill structures on-call handoffs around incidents, investigations, and recent changes. Use it for shift changes, incident takeovers, and onboarding. Claude Code CX Codex Cursor 10,300installs secops-investigate official Google LLC skill This skill supports deep incident and entity investigations in Google SecOps. Use it for UDM searches, asset and user timelines, and lateral movement analysis. Claude Code Gemini CLI CX Codex 1,900installs connectivity-triage Seth Hobson skill Diagnoses active macOS network failures without modifying system settings. Helps isolate API timeouts, MCP disconnects, and DNS lookup issues. Claude Code CX Codex Cursor 743installs incident-response Alireza Rezvani skill Triage and classify active security incidents in Claude Code. The skill scores events from SEV1 to SEV4, filters false positives, and routes escalations. Claude Code 634installs ciso-advisor Alireza Rezvani skill Turns security risks into financial estimates and helps plan compliance work. Use it to shape a security program, assess vendors, or coordinate incident response. Claude Code 623installs sre-engineer VoltAgent Community subagent This subagent reviews service reliability, SLI and SLO practices, and incident response. Use it when you need to find operational toil or plan reliability work. Claude Code 354installs chaos-engineer VoltAgent Community subagent This subagent plans controlled failure experiments and checks how a system recovers. Use it to prepare for incidents or run a game day. Claude Code 267installs incident-responder VoltAgent Community subagent This subagent handles active service outages and security breaches. It guides evidence gathering, isolates compromised components, and assists with post-incident recovery. Claude Code 265installs incident-responder Seth Hobson subagent Guides on-call engineers through outage triage and production stabilization following SRE protocols. Activates incident command and structure during downtime. Claude Code CX Codex Cursor 265installs devops-incident-responder VoltAgent Community subagent Assists with active production incidents, root-cause investigations, and blameless postmortems. Built for teams handling live service outages. Claude Code 206installs incident-postmortem official github skill This skill guides a blameless incident post-mortem: rebuild the timeline, measure impact, find systemic causes, and assign follow-up actions. GitHub Copilot 81installs Dynatrace Expert official github subagent Integrates Dynatrace observability and security directly into repository workflows. It investigates incidents, verifies deployments, and identifies vulnerabilities via traces and logs. GitHub Copilot ★ 40,369repo stars AWS Incident Triage official github subagent Drives structured AWS incident investigations from CloudWatch alarms to root-cause hypotheses using metrics, logs, and traces without touching live infrastructure. GitHub Copilot ★ 40,369repo stars devops-oncall official Awesome Copilot Community plugin A GitHub Copilot plugin with prompts, commands, and an agent for incident triage and Azure diagnostics. Helpful for on-call engineers managing cloud infrastructure. GitHub Copilot ★ 40,369repo stars

More in NeVibeCode

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor