Skip to content
cccskills
FreePublished on GitHub

incident-response

Respond to production incidents systematically with triage, investigation, resolution, and post-mortem analysis to minimize downtime and prevent recurrence. Use when handling production outages, triaging incidents, investigating critical bugs, coordinating incident response, implementing hotfixes, conducting post-mortems, or establishing incident response procedures.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Incident Response - Production Issue Management

When to use this skill

  • Responding to production outages
  • Triaging critical incidents
  • Investigating high-severity bugs
  • Coordinating incident response teams
  • Implementing emergency hotfixes
  • Conducting post-mortem analyses
  • Establishing incident response procedures
  • Communicating status during incidents
  • Creating runbooks for common issues
  • Implementing rollback strategies
  • Documenting incident timelines
  • Preventing incident recurrence

When to use this skill

  • Responding to outages, managing incidents, conducting postmortems.
  • When working on related tasks or features
  • During development that requires this expertise

Use when: Responding to outages, managing incidents, conducting postmortems.

Incident Response Process

1. Detect

  • Monitoring alerts
  • User reports
  • Automated checks

2. Triage

  • Assess severity (P0-P4)
  • Page on-call engineer
  • Create incident channel

3. Mitigate

  • Rollback to last known good
  • Scale resources
  • Apply hotfix
  • Communicate status

4. Resolve

  • Verify fix
  • Monitor metrics
  • Update status page
  • Close incident

5. Postmortem

  • Timeline of events
  • Root cause analysis
  • Action items
  • Follow-up tasks

Severity Levels

  • P0 (Critical): Complete outage, data loss
  • P1 (High): Major feature broken, revenue impact
  • P2 (Medium): Degraded performance, workaround exists
  • P3 (Low): Minor bug, cosmetic issue
  • P4 (Informational): Enhancement request

Example Runbook

```markdown

High CPU Usage Runbook

Symptoms

  • Server CPU > 90%
  • Slow response times
  • Request timeouts

Investigation

  1. Check top processes: `top`
  2. Check memory: `free -h`
  3. Check logs: `tail -f app.log`

Mitigation

  1. Scale horizontally: Add servers
  2. Restart service: `systemctl restart app`
  3. Rate limit: Enable aggressive rate limiting

Resolution

  1. Identify root cause (N+1 query, memory leak, etc.)
  2. Deploy fix
  3. Monitor for 1 hour ```

Communication Template

``` [INCIDENT] Service X degraded

Status: Investigating Impact: 20% of users seeing slow load times ETA: 30 minutes

Updates:

  • 10:00 AM: Issue detected
  • 10:05 AM: On-call paged, investigation started
  • 10:15 AM: Root cause identified (database bottleneck)
  • 10:30 AM: Fix deployed, monitoring

Next update: 11:00 AM ```

Resources

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities.

The English summary is being prepared. Showing the original description.

Fabric-Pro/fabric-oss3Updated Oct 23, 2026

Guide for adding new OAuth-based integrations to Fabric. Use when implementing OAuth providers like Microsoft Teams, GitHub, Google Drive, Slack, or similar services that need OAuth 2.0 authentication for user data access.

The English summary is being prepared. Showing the original description.

Fabric-Pro/fabric-oss3Updated Oct 23, 2026

Design clean, scalable, and maintainable REST and GraphQL APIs following industry best practices. Use when designing public or internal APIs, planning endpoint structures, defining request/response contracts, establishing versioning strategies, implementing authentication patterns, designing data models, creating API documentation, ensuring consistent error handling, optimizing for performance, or establishing service contracts between microservices.

The English summary is being prepared. Showing the original description.

Fabric-Pro/fabric-oss3Updated Oct 23, 2026

Create professional, dark-themed architecture diagrams as standalone HTML files with SVG graphics. Use when the user asks for system architecture diagrams, infrastructure diagrams, cloud architecture visualizations, security diagrams, network topology diagrams, or any technical diagram showing system components and their relationships.

The English summary is being prepared. Showing the original description.

Fabric-Pro/fabric-oss3Updated Oct 23, 2026

Create interactive, self-contained artifacts like mini-apps, visualizations, calculators, and tools that can be embedded or used standalone. Use when building interactive calculators, creating data visualizations, making mini web apps, building embeddable widgets, creating interactive demos, making tools for specific tasks, or generating standalone HTML/JS applications.

The English summary is being prepared. Showing the original description.

Fabric-Pro/fabric-oss3Updated Oct 23, 2026

Set up something that runs on a schedule (a weekly report, a daily digest) as a scheduled workflow, change, pause or debug one, and build interactive pages (project artifacts and workspaces) that read live Fabric data. Use when the user asks for a recurring job, a status page, a dashboard or a page with buttons, or asks why one did not run.

The English summary is being prepared. Showing the original description.

Fabric-Pro/fabric-oss3Updated Oct 23, 2026

See all skills by Fabric-Pro

Report a problem with this skill