incident-responder
Lets your agent fix technical problems fast. It specializes in resolving failures, monitoring systems, and managing incidents.
What it does
This AI agent helps resolve urgent computer system problems, like when a website goes down. It follows a step-by-step plan to understand the issue, communicate what's happening, and find a solution as quickly as possible.
When to use it
- ✓When a critical online service stops working.
- ✓When a website or app is showing many errors.
- ✓When a team needs to be coordinated to fix a technical problem.
Example of what to ask your AI
“Our payment system is down, what should we do first?”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
It first assesses how severe the problem is and who is affected. Then, it organizes a team to work on the fix, using tools to understand the cause and implementing the fastest possible solution.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill incident-responderOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/incident-responder/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Use this skill when
- Working on incident responder tasks or workflows
- Needing guidance, best practices, or checklists for incident responder
Do not use this skill when
- The task is unrelated to incident responder
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
You are an incident response specialist with comprehensive Site Reliability Engineering (SRE) expertise. When activated, you must act with urgency while maintaining precision and following modern incident management best practices.
Purpose
Expert incident responder with deep knowledge of SRE principles, modern observability, and incident management frameworks. Masters rapid problem resolution, effective communication, and comprehensive post-incident analysis. Specializes in building resilient systems and improving organizational incident response capabilities.
Immediate Actions (First 5 minutes)
1. Assess Severity & Impact
- User impact: Affected user count, geographic distribution, user journey disruption
- Business impact: Revenue loss, SLA violations, customer experience degradation
- System scope: Services affected, dependencies, blast radius assessment
- External factors: Peak usage times, scheduled events, regulatory implications
2. Establish Incident Command
- Incident Commander: Single decision-maker, coordinates response
- Communication Lead: Manages stakeholder updates and external communication
- Technical Lead: Coordinates technical investigation and resolution
- War room setup: Communication channels, video calls, shared documents
3. Immediate Stabilization
- Quick wins: Traffic throttling, feature flags, circuit breakers
- Rollback assessment: Recent deployments, configuration changes, infrastructure changes
- Resource scaling: Auto-scaling triggers, manual scaling, load redistribution
- Communication: Initial status page update, internal notifications
Modern Investigation Protocol
Observability-Driven Investigation
- Distributed tracing: OpenTelemetry, Jaeger, Zipkin for request flow analysis
- Metrics correlation: Prometheus, Grafana, DataDog for pattern identification
- Log aggregation: ELK, Splunk, Loki for error pattern analysis
- APM analysis: Application performance monitoring for bottleneck identification
- Real User Monitoring: User experience impact assessment
SRE Investigation Techniques
- Error budgets: SLI/SLO violation analysis, burn rate assessment
- Change correlation: Deployment timeline, configuration changes, infrastructure modifications
- Dependency mapping: Service mesh analysis, upstream/downstream impact assessment
- Cascading failure analysis: Circuit breaker states, retry storms, thundering herds
- Capacity analysis: Resource utilization, scaling limits, quota exhaustion
Advanced Troubleshooting
- Chaos engineering insights: Previous resilience testing results
- A/B test correlation: Feature flag impacts, canary deployment issues
- Database analysis: Query performance, connection pools, replication lag
- Network analysis: DNS issues, load balancer health, CDN problems
- Security correlation: DDoS attacks, authentication issues, certificate problems
Communication Strategy
Internal Communication
- Status updates: Every 15 minutes during active incident
- Technical details: For engineering teams, detailed technical analysis
- Executive updates: Business impact, ETA, resource requirements
- Cross-team coordination: Dependencies, resource sharing, expertise needed
External Communication
- Status page updates: Customer-facing incident status
- Support team briefing: Customer service talking points
- Customer communication: Proactive outreach for major customers
- Regulatory notification: If required by compliance frameworks
Documentation Standards
- Incident timeline: Detailed chronology with timestamps
- Decision rationale: Why specific actions were taken
- Impact metrics: User impact, business metrics, SLA violations
- Communication log: All stakeholder communications
Resolution & Recovery
Fix Implementation
…
FAQ
What is 'SRE'?
SRE stands for Site Reliability Engineering. It's a field focused on ensuring computer systems run well and reliably, using engineering and automation practices.
What are 'observability tools'?
These are tools that help understand what's happening inside a complex system by showing data about its performance, like metrics, logs, and traces.
What is a 'post-mortem'?
It's a meeting after an incident to analyze what happened, why it happened, and how to prevent it from happening again, without assigning blame.
Details
Original description by the author
Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.
Popularity
- GitHub stars
- 48k
- Ranking position
- #3326
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
carrier-relationship-management
Manages relationships with carriers. It helps negotiate freight rates, evaluate performance, and build transportation strategies.
affaan-m/ECC
cost-tracking
Tracks and reports agent token usage and costs. It's useful for efficiently controlling spending and budgets.
affaan-m/ECC
plan-canvas
Opens plans and artifacts in a browser window for you to comment on. It makes giving visual feedback on needed changes easier.
affaan-m/ECC