[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P6R6SBXD05HX9QN83CYASD":3,"skill-same:01M6P6R6SBXD05HX9QN83CYASD":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":28,"commitSha":53,"skillDirectory":54,"forksCount":13,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6P6R6SBXD05HX9QN83CYASD","incident-management",null,"Implement incident management processes and escalation procedures. Configure on-call schedules and post-incident reviews. Use when managing production incidents.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fincident-management\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"incident management","management","incident","community","apply","incidents","reviews","controls","post","call","main","github","agent-skills","use","configure","devops-security","escalation","license","change","implement","2026-11-10 10:12:30",false,"---\nname: incident-management\ndescription: Implement incident management processes and escalation procedures. Configure\n  on-call schedules and post-incident reviews. Use when managing production incidents.\ncategory: security\nrisk: safe\nsource: https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills\nsource_repo: BagelHole\u002FDevOps-Security-Agent-Skills\nsource_type: community\ndate_added: '2026-09-20'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills\u002Fblob\u002Fmain\u002FLICENSE\ncompatibility: Checklist and framework guidance; no privileged tooling required. Apply\n  controls through your own change process.\nmetadata:\n  author: devops-skills\n  version: '1.0'\n---\n\n# Incident Management\n\nImplement effective incident management processes including severity definitions, escalation matrices, war room procedures, and blameless post-mortem templates.\n\n## When to Use\n\n- Establishing incident management processes for production systems\n- Defining severity levels and escalation procedures\n- Running war rooms and coordinating incident response\n- Conducting blameless post-incident reviews\n- Building on-call schedules and notification workflows\n- Meeting compliance requirements for incident response (SOC 2, HIPAA, PCI DSS)\n\n## Severity Levels\n\n```yaml\nseverity_definitions:\n  SEV1_critical:\n    impact: \"Complete service outage or data breach affecting all\u002Fmost customers\"\n    examples:\n      - Production site completely down\n      - Data breach confirmed or suspected\n      - Complete loss of a critical business function\n      - Security incident with active exploitation\n    response_time: \"Immediate (within 5 minutes)\"\n    update_frequency: \"Every 15-30 minutes\"\n    who_is_paged: \"On-call engineer, engineering manager, incident commander, executive on-call\"\n    communication: \"Status page update, customer email, executive notification\"\n    resolution_target: \"\u003C 1 hour to mitigate\"\n\n  SEV2_major:\n    impact: \"Major feature broken or severe degradation affecting many customers\"\n    examples:\n      - Key feature completely non-functional\n      - Significant performance degradation (>5x latency)\n      - Data processing pipeline completely stalled\n      - Partial outage affecting a region or segment\n    response_time: \"Within 15 minutes\"\n    update_frequency: \"Every 30-60 minutes\"\n    who_is_paged: \"On-call engineer, engineering manager\"\n    communication: \"Status page update if customer-facing\"\n    resolution_target: \"\u003C 4 hours to mitigate\"\n\n  SEV3_moderate:\n    impact: \"Minor feature impaired or degradation affecting some customers\"\n    examples:\n      - Non-critical feature broken\n      - Moderate performance degradation\n      - Elevated error rate (below threshold for SEV2)\n      - Single-customer impact on non-critical function\n    response_time: \"Within 1 hour during business hours\"\n    update_frequency: \"Every 2-4 hours\"\n    who_is_paged: \"On-call engineer\"\n    communication: \"Internal only unless customer inquires\"\n    resolution_target: \"\u003C 1 business day\"\n\n  SEV4_low:\n    impact: \"Cosmetic issue, minor inconvenience, or non-customer-facing problem\"\n    examples:\n      - UI cosmetic bug\n      - Non-critical monitoring gap\n      - Internal tool degradation\n      - Documentation inaccuracy in production\n    response_time: \"Next business day\"\n    update_frequency: \"As needed\"\n    who_is_paged: \"None (ticket created)\"\n    communication: \"None\"\n    resolution_target: \"Within sprint planning cycle\"\n```\n\n## Escalation Matrix\n\n```yaml\nescalation_matrix:\n  tier_1_on_call_engineer:\n    reached_via: \"PagerDuty \u002F OpsGenie alert\"\n    responsibilities:\n      - Acknowledge alert within 5 minutes\n      - Assess severity and impact\n      - Begin troubleshooting\n      - Escalate to Tier 2 if unable to resolve within 30 minutes (SEV1\u002F2)\n    escalation_trigger: \"Cannot resolve, needs additional expertise, or severity upgrade\"\n\n  tier_2_team_lead_or_sme:\n    reached_via: \"PagerDuty escalation or direct page\"\n    responsibilities:\n      - Provide subject matter expertise\n      - Assist with diagnosis and resolution\n      - Coordinate with other teams if cross-service issue\n      - Escalate to Tier 3 if broader coordination needed\n    escalation_trigger: \"Multi-service issue, needs executive decision, or customer-facing SEV1\"\n\n  tier_3_engineering_management:\n    reached_via: \"PagerDuty escalation or direct call\"\n    responsibilities:\n      - Assign incident commander (if not already)\n      - Allocate additional resources\n      - Make business decisions (feature disable, rollback, etc.)\n      - Coordinate external communication\n    escalation_trigger: \"Business impact decision, extended outage, or PR\u002Flegal concern\"\n\n  tier_4_executive:\n    reached_via: \"Direct phone call\"\n    responsibilities:\n      - Authorize extraordinary measures\n      - Manage board\u002Finvestor communication\n      - Approve public statements\n      - Engage external resources (vendors, consultants)\n    escalation_trigger: \"Major breach, extended SEV1, regulatory or legal implication\"\n\n  time_based_escalation:\n    sev1:\n      \"15 min no ack\": \"Re-page on-call + backup on-call\"\n      \"30 min unresolved\": \"Page team lead\"\n      \"1 hour unresolved\": \"Page engineering manager + executive on-call\"\n      \"2 hours unresolved\": \"All-hands engineering involvement\"\n    sev2:\n      \"30 min no ack\": \"Re-page on-call + backup on-call\"\n      \"1 hour unresolved\": \"Page team lead\"\n      \"4 hours unresolved\": \"Page engineering manager\"\n```\n\n## War Room Procedures\n\n```yaml\nwar_room:\n  activation: \"Automatically for SEV1, on-demand for SEV2\"\n\n  setup:\n    communication_channel:\n      primary: \"Dedicated Slack channel (#incident-YYYY-MM-DD-brief-name)\"\n      voice: \"Zoom\u002FGoogle Meet bridge (persistent link)\"\n      backup: \"Phone conference bridge\"\n    channel_rules:\n      - \"Only incident-related communication in the channel\"\n      - \"Use threads for side discussions\"\n      - \"Prefix messages with role (IC:, COMMS:, ENG:)\"\n\n  roles:\n    incident_commander:\n      responsibilities:\n        - Own the incident from declaration to resolution\n        - Coordinate all response activities\n        - Make decisions on response actions\n        - Assign tasks to responders\n        - Determine when incident is resolved\n        - Schedule post-mortem\n      selection: \"On-call IC roster, or senior engineer who declares the incident\"\n\n    communications_lead:\n      responsibilities:\n        - Draft and publish status page updates\n        - Coordinate customer notifications\n        - Handle internal stakeholder updates\n        - Manage executive communication\n        - Document timeline in real-time\n      selection: \"Designated from on-call comms roster or engineering manager\"\n\n    technical_lead:\n      responsibilities:\n        - Lead technical diagnosis and troubleshooting\n        - Coordinate technical responders\n        - Recommend mitigation and resolution actions\n        - Verify fix effectiveness\n      selection: \"Senior engineer with relevant system expertise\"\n\n    scribe:\n      responsibilities:\n        - Document all actions, decisions, and findings\n        - Maintain real-time timeline\n        - Record who did what and when\n        - Capture screenshots and log excerpts\n      selection: \"Any available team member (can be rotated)\"\n\n  workflow:\n    1_declare:\n      - \"IC declares incident with severity level\"\n      - \"War room channel and bridge created\"\n      - \"Roles assigned\"\n      - \"First status update posted\"\n\n    2_assess:\n      - \"Determine scope and customer impact\"\n      - \"Identify affected systems and services\"\n      - \"Establish working hypothesis\"\n\n    3_mitigate:\n      - \"Focus on restoring service first, root cause second\"\n      - \"IC approves all changes to production\"\n      - \"Changes documented in real-time\"\n      - \"Rollback if mitigation makes things worse\"\n\n    4_resolve:\n      - \"Confirm service restored to normal\"\n      - \"Verify monitoring shows healthy metrics\"\n      - \"IC declares incident resolved\"\n      - \"Final status page update\"\n\n    5_follow_up:\n      - \"Schedule post-mortem within 48 hours\"\n      - \"Assign action items from immediate findings\"\n      - \"Send internal summary\"\n```\n\n## On-Call Configuration\n\n```yaml\non_call_schedule:\n  rotation_structure:\n    primary:\n      rotation: \"Weekly\"\n      handoff: \"Monday 10:00 AM local time\"\n      team_size: \"Minimum 5 engineers in rotation\"\n    secondary:\n      rotation: \"Weekly (offset from primary)\"\n      activation: \"If primary does not acknowledge within 10 minutes\"\n\n  expectations:\n    response_time: \"Acknowledge alert within 5 minutes\"\n    availability: \"Reachable by phone and laptop within 15 minutes\"\n    handoff: \"Document any ongoing issues during handoff\"\n    compensation: \"Per company on-call compensation policy\"\n\n  health:\n    max_consecutive_weeks: 2\n    minimum_gap_between_rotations: \"2 weeks\"\n    post_incident_rest: \"If engaged for 4+ hours overnight, late start next day\"\n    burnout_monitoring: \"Track pages per person per week, rebalance if needed\"\n\n  pagerduty_configuration:\n    escalation_policy:\n      - level_1:\n          target: \"Primary on-call\"\n          timeout: \"5 minutes\"\n      - level_2:\n          target: \"Secondary on-call\"\n          timeout: \"10 minutes\"\n      - level_3:\n          target: \"Engineering manager\"\n          timeout: \"15 minutes\"\n\n    notification_rules:\n      high_urgency:\n        - \"Push notification immediately\"\n        - \"Phone call after 1 minute\"\n        - \"SMS after 2 minutes\"\n      low_urgency:\n        - \"Push notification\"\n        - \"Email after 5 minutes\"\n```\n\n## Post-Mortem Template\n\n```markdown\n# Post-Incident Review: [Incident Title]\n\n**Date:** YYYY-MM-DD\n**Severity:** SEV[1-4]\n**Duration:** [Start time] to [End time] ([X hours Y minutes])\n**Incident Commander:** [Name]\n**Author:** [Name]\n**Status:** Draft \u002F In Review \u002F Final\n\n## Executive Summary\n[2-3 sentence summary of what happened, the impact, and the resolution]\n\n## Impact\n- **Customer impact:** [Number\u002Fpercentage of customers affected, what they experienced]\n- **Duration of impact:** [How long customers were affected]\n- **Revenue impact:** [Estimated financial impact, if applicable]\n- **Data impact:** [Any data loss or corruption]\n- **SLA impact:** [Any SLA breaches]\n\n## Timeline (all times UTC)\n| Time | Event |\n|------|-------|\n| HH:MM | [First anomaly detected by monitoring] |\n| HH:MM | [Alert fired \u002F customer report received] |\n| HH:MM | [On-call engineer acknowledged] |\n| HH:MM | [Incident declared at SEV level] |\n| HH:MM | [War room established] |\n| HH:MM | [Root cause identified] |\n| HH:MM | [Mitigation applied] |\n| HH:MM | [Service restored] |\n| HH:MM | [Incident resolved] |\n\n## Root Cause\n[Detailed technical explanation of what caused the incident]\n\n## Detection\n- **How was the incident detected?** [Monitoring alert \u002F customer report \u002F manual observation]\n- **Time to detect:** [Time from first anomaly to detection]\n- **Could we have detected sooner?** [Yes\u002FNo, with explanation]\n\n## Response\n- **What went well:**\n  - [List things that worked effectively during response]\n  - [E.g., \"Runbook for database failover was accurate and followed successfully\"]\n  - [E.g., \"Communication to customers was timely and clear\"]\n\n- **What could be improved:**\n  - [List things that slowed or hindered response]\n  - [E.g., \"Took 20 minutes to identify the correct service owner\"]\n  - [E.g., \"Monitoring did not alert on the specific failure mode\"]\n\n## Contributing Factors\n[List all factors that contributed to the incident occurring or being worse than it could have been. This is not about blame - it is about understanding the system.]\n\n1. [Factor 1: e.g., \"Configuration change was not tested in staging\"]\n2. [Factor 2: e.g., \"Alert threshold was too high to catch gradual degradation\"]\n3. [Factor 3: e.g., \"No circuit breaker between Service A and Service B\"]\n\n## Action Items\n| ID | Action | Owner | Priority | Due Date | Status |\n|----|--------|-------|----------|----------|--------|\n| 1 | [Preventive action] | [Name] | P1 | YYYY-MM-DD | Open |\n| 2 | [Detection improvement] | [Name] | P2 | YYYY-MM-DD | Open |\n| 3 | [Process improvement] | [Name] | P2 | YYYY-MM-DD | Open |\n| 4 | [Runbook update] | [Name] | P3 | YYYY-MM-DD | Open |\n\n## Lessons Learned\n[Key takeaways that should be shared broadly]\n\n## Appendix\n- [Link to monitoring dashboards during incident]\n- [Link to relevant log queries]\n- [Link to war room channel archive]\n```\n\n## Post-Mortem Process\n\n```yaml\npost_mortem_process:\n  scheduling:\n    sev1: \"Within 48 hours of resolution\"\n    sev2: \"Within 1 week of resolution\"\n    sev3: \"Within 2 weeks (optional, based on learning potential)\"\n    sev4: \"Not required\"\n\n  meeting_format:\n    duration: \"60-90 minutes\"\n    attendees:\n      required: \"IC, technical lead, scribe, involved engineers\"\n      optional: \"Engineering manager, product manager, affected team leads\"\n    agenda:\n      - \"5 min: Review timeline and facts\"\n      - \"15 min: Walk through root cause and contributing factors\"\n      - \"15 min: Discuss what went well\"\n      - \"15 min: Discuss what could be improved\"\n      - \"15 min: Define and assign action items\"\n      - \"5 min: Identify lessons learned and sharing plan\"\n\n  principles:\n    - \"Blameless: Focus on systems and processes, not individuals\"\n    - \"Factual: Base discussion on data, logs, and observations\"\n    - \"Forward-looking: Prioritize preventive actions over assigning fault\"\n    - \"Complete: Address detection, response, and prevention\"\n    - \"Actionable: Every finding should produce a tracked action item\"\n\n  action_item_tracking:\n    - \"All action items entered into issue tracker (Jira, GitHub Issues)\"\n    - \"Priority assigned based on risk reduction potential\"\n    - \"Owner assigned with due date\"\n    - \"Reviewed in team standups and sprint planning\"\n    - \"Tracked to completion\"\n    - \"Monthly review of open post-mortem action items\"\n```\n\n## Incident Metrics\n\n```yaml\nincident_metrics:\n  mttr:\n    name: \"Mean Time to Resolve\"\n    definition: \"Average time from incident detection to resolution\"\n    target: \"SEV1: \u003C1h, SEV2: \u003C4h\"\n    trending: \"Track monthly, aim for improvement\"\n\n  mttd:\n    name: \"Mean Time to Detect\"\n    definition: \"Average time from incident start to detection\"\n    target: \"\u003C 5 minutes for SEV1\u002F2\"\n    trending: \"Monitors effectiveness of alerting\"\n\n  mtta:\n    name: \"Mean Time to Acknowledge\"\n    definition: \"Average time from alert to engineer acknowledgment\"\n    target: \"\u003C 5 minutes\"\n    trending: \"Monitors on-call responsiveness\"\n\n  incident_frequency:\n    name: \"Incidents per week\u002Fmonth by severity\"\n    target: \"Trending downward\"\n    trending: \"Monitors system reliability improvement\"\n\n  action_item_completion:\n    name: \"Post-mortem action item completion rate\"\n    target: \"> 90% completed on time\"\n    trending: \"Monitors follow-through on improvements\"\n\n  recurring_incidents:\n    name: \"Percentage of incidents with same root cause as previous incident\"\n    target: \"\u003C 10%\"\n    trending: \"Monitors effectiveness of preventive actions\"\n```\n\n## Incident Management Checklist\n\n```yaml\nincident_management_checklist:\n  process_setup:\n    - [ ] Severity levels defined with clear criteria\n    - [ ] Escalation matrix documented\n    - [ ] On-call schedule established and staffed\n    - [ ] War room procedures documented\n    - [ ] Post-mortem template created\n    - [ ] Communication templates prepared (status page, email)\n    - [ ] Incident management tool configured (PagerDuty, OpsGenie)\n\n  per_incident:\n    - [ ] Incident declared with severity level\n    - [ ] War room established (SEV1\u002F2)\n    - [ ] Roles assigned (IC, comms, technical lead, scribe)\n    - [ ] Timeline maintained in real-time\n    - [ ] Status page updated (customer-facing impact)\n    - [ ] Stakeholders notified per communication plan\n    - [ ] Resolution verified with monitoring\n    - [ ] Post-mortem scheduled\n    - [ ] Post-mortem conducted and published\n    - [ ] Action items tracked to completion\n\n  compliance:\n    - [ ] All SEV1\u002F2 incidents have post-mortems\n    - [ ] Incident log maintained for audit evidence\n    - [ ] Metrics reported monthly\n    - [ ] On-call health monitored (pages per person)\n    - [ ] Annual incident response training conducted\n    - [ ] Annual incident response plan test completed\n```\n\n## Best Practices\n\n- Define severity levels with concrete examples so there is no ambiguity during an active incident\n- Implement time-based escalation: if the on-call does not acknowledge, automatically escalate\n- Focus on mitigation first, root cause second: restore service before investigating why it failed\n- Run blameless post-mortems: the goal is to improve systems, not to assign fault to individuals\n- Track post-mortem action items to completion: an unfinished action item means the same incident can recur\n- Monitor incident metrics (MTTR, MTTD, frequency) as leading indicators of system reliability\n- Protect on-call health: track page volume per person and redistribute if someone is overburdened\n- Separate the incident commander role from the technical lead role in SEV1\u002F2 incidents\n- Practice incident response regularly with game days or chaos engineering exercises\n- Archive incident records and post-mortems for compliance evidence and organizational learning\n\n## Limitations\n\n- Guidance and checklists only; not legal advice and not a substitute for a qualified auditor.\n- Docs-only import: upstream templates and scripts not bundled.\n\n### Example\n\n```markdown\nMap this skill's control checklist to our current evidence and list gaps.\n```\n\n> Adapted from [BagelHole\u002FDevOps-Security-Agent-Skills](https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: helper scripts and templates not bundled.\n","# Incident Management\n\nImplement effective incident management processes including severity definitions, escalation matrices, war room procedures, and blameless post-mortem templates.\n\n## When to Use\n\n- Establishing incident management processes for production systems\n- Defining severity levels and escalation procedures\n- Running war rooms and coordinating incident response\n- Conducting blameless post-incident reviews\n- Building on-call schedules and notification workflows\n- Meeting compliance requirements for incident response (SOC 2, HIPAA, PCI DSS)\n\n## Severity Levels\n\n```yaml\nseverity_definitions:\n  SEV1_critical:\n    impact: \"Complete service outage or data breach affecting all\u002Fmost customers\"\n    examples:\n      - Production site completely down\n      - Data breach confirmed or suspected\n      - Complete loss of a critical business function\n      - Security incident with active exploitation\n    response_time: \"Immediate (within 5 minutes)\"\n    update_frequency: \"Every 15-30 minutes\"\n    who_is_paged: \"On-call engineer, engineering manager, incident commander, executive on-call\"\n    communication: \"Status page update, customer email, executive notification\"\n    resolution_target: \"\u003C 1 hour to mitigate\"\n\n  SEV2_major:\n    impact: \"Major feature broken or severe degradation affecting many customers\"\n    examples:\n      - Key feature completely non-functional\n      - Significant performance degradation (>5x latency)\n      - Data processing pipeline completely stalled\n      - Partial outage affecting a region or segment\n    response_time: \"Within 15 minutes\"\n    update_frequency: \"Every 30-60 minutes\"\n    who_is_paged: \"On-call engineer, engineering manager\"\n    communication: \"Status page update if customer-facing\"\n    resolution_target: \"\u003C 4 hours to mitigate\"\n\n  SEV3_moderate:\n    impact: \"Minor feature impaired or degradation affecting some customers\"\n    examples:\n      - Non-critical feature broken\n      - Moderate performance degradation\n      - Elevated error rate (below threshold for SEV2)\n      - Single-customer impact on non-critical function\n    response_time: \"Within 1 hour during business hours\"\n    update_frequency: \"Every 2-4 hours\"\n    who_is_paged: \"On-call engineer\"\n    communication: \"Internal only unless customer inquires\"\n    resolution_target: \"\u003C 1 business day\"\n\n  SEV4_low:\n    impact: \"Cosmetic issue, minor inconvenience, or non-customer-facing problem\"\n    examples:\n      - UI cosmetic bug\n      - Non-critical monitoring gap\n      - Internal tool degradation\n      - Documentation inaccuracy in production\n    response_time: \"Next business day\"\n    update_frequency: \"As needed\"\n    who_is_paged: \"None (ticket created)\"\n    communication: \"None\"\n    resolution_target: \"Within sprint planning cycle\"\n```\n\n## Escalation Matrix\n\n```yaml\nescalation_matrix:\n  tier_1_on_call_engineer:\n    reached_via: \"PagerDuty \u002F OpsGenie alert\"\n    responsibilities:\n      - Acknowledge alert within 5 minutes\n      - Assess severity and impact\n      - Begin troubleshooting\n      - Escalate to Tier 2 if unable to resolve within 30 minutes (SEV1\u002F2)\n    escalation_trigger: \"Cannot resolve, needs additional expertise, or severity upgrade\"\n\n  tier_2_team_lead_or_sme:\n    reached_via: \"PagerDuty escalation or direct page\"\n    responsibilities:\n      - Provide subject matter expertise\n      - Assist with diagnosis and resolution\n      - Coordinate with other teams if cross-service issue\n      - Escalate to Tier 3 if broader coordination needed\n    escalation_trigger: \"Multi-service issue, needs executive decision, or customer-facing SEV1\"\n\n  tier_3_engineering_management:\n    reached_via: \"PagerDuty escalation or direct call\"\n    responsibilities:\n      - Assign incident commander (if not already)\n      - Allocate additional resources\n      - Make business decisions (feature disable, rollback, etc.)\n      - Coordinate external communication\n    escalation_trigger: \"Business impact decision, extended outage, or PR\u002Flegal concern\"\n\n  tier_4_executive:\n    reached_via: \"Direct phone call\"\n    responsibilities:\n      - Authorize extraordinary measures\n      - Manage board\u002Finvestor communication\n      - Approve public statements\n      - Engage external resources (vendors, consultants)\n    escalation_trigger: \"Major breach, extended SEV1, regulatory or legal implication\"\n\n  time_based_escalation:\n    sev1:\n      \"15 min no ack\": \"Re-page on-call + backup on-call\"\n      \"30 min unresolved\": \"Page team lead\"\n      \"1 hour unresolved\": \"Page engineering manager + executive on-call\"\n      \"2 hours unresolved\": \"All-hands engineering involvement\"\n    sev2:\n      \"30 min no ack\": \"Re-page on-call + backup on-call\"\n      \"1 hour unresolved\": \"Page team lead\"\n      \"4 hours unresolved\": \"Page engineering manager\"\n```\n\n## War Room Procedures\n\n```yaml\nwar_room:\n  activation: \"Automatically for SEV1, on-demand for SEV2\"\n\n  setup:\n    communication_channel:\n      primary: \"Dedicated Slack channel (#incident-YYYY-MM-DD-brief-name)\"\n      voice: \"Zoom\u002FGoogle Meet bridge (persistent link)\"\n      backup: \"Phone conference bridge\"\n    channel_rules:\n      - \"Only incident-related communication in the channel\"\n      - \"Use threads for side discussions\"\n      - \"Prefix messages with role (IC:, COMMS:, ENG:)\"\n\n  roles:\n    incident_commander:\n      responsibilities:\n        - Own the incident from declaration to resolution\n        - Coordinate all response activities\n        - Make decisions on response actions\n        - Assign tasks to responders\n        - Determine when incident is resolved\n        - Schedule post-mortem\n      selection: \"On-call IC roster, or senior engineer who declares the incident\"\n\n    communications_lead:\n      responsibilities:\n        - Draft and publish status page updates\n        - Coordinate customer notifications\n        - Handle internal stakeholder updates\n        - Manage executive communication\n        - Document timeline in real-time\n      selection: \"Designated from on-call comms roster or engineering manager\"\n\n    technical_lead:\n      responsibilities:\n        - Lead technical diagnosis and troubleshooting\n        - Coordinate technical responders\n        - Recommend mitigation and resolution actions\n        - Verify fix effectiveness\n      selection: \"Senior engineer with relevant system expertise\"\n\n    scribe:\n      responsibilities:\n        - Document all actions, decisions, and findings\n        - Maintain real-time timeline\n        - Record who did what and when\n        - Capture screenshots and log excerpts\n      selection: \"Any available team member (can be rotated)\"\n\n  workflow:\n    1_declare:\n      - \"IC declares incident with severity level\"\n      - \"War room channel and bridge created\"\n      - \"Roles assigned\"\n      - \"First status update posted\"\n\n    2_assess:\n      - \"Determine scope and customer impact\"\n      - \"Identify affected systems and services\"\n      - \"Establish working hypothesis\"\n\n    3_mitigate:\n      - \"Focus on restoring service first, root cause second\"\n      - \"IC approves all changes to production\"\n      - \"Changes documented in real-time\"\n      - \"Rollback if mitigation makes things worse\"\n\n    4_resolve:\n      - \"Confirm service restored to normal\"\n      - \"Verify monitoring shows healthy metrics\"\n      - \"IC declares incident resolved\"\n      - \"Final status page update\"\n\n    5_follow_up:\n      - \"Schedule post-mortem within 48 hours\"\n      - \"Assign action items from immediate findings\"\n      - \"Send internal summary\"\n```\n\n## On-Call Configuration\n\n```yaml\non_call_schedule:\n  rotation_structure:\n    primary:\n      rotation: \"Weekly\"\n      handoff: \"Monday 10:00 AM local time\"\n      team_size: \"Minimum 5 engineers in rotation\"\n    secondary:\n      rotation: \"Weekly (offset from primary)\"\n      activation: \"If primary does not acknowledge within 10 minutes\"\n\n  expectations:\n    response_time: \"Acknowledge alert within 5 minutes\"\n    availability: \"Reachable by phone and laptop within 15 minutes\"\n    handoff: \"Document any ongoing issues during handoff\"\n    compensation: \"Per company on-call compensation policy\"\n\n  health:\n    max_consecutive_weeks: 2\n    minimum_gap_between_rotations: \"2 weeks\"\n    post_incident_rest: \"If engaged for 4+ hours overnight, late start next day\"\n    burnout_monitoring: \"Track pages per person per week, rebalance if needed\"\n\n  pagerduty_configuration:\n    escalation_policy:\n      - level_1:\n          target: \"Primary on-call\"\n          timeout: \"5 minutes\"\n      - level_2:\n          target: \"Secondary on-call\"\n          timeout: \"10 minutes\"\n      - level_3:\n          target: \"Engineering manager\"\n          timeout: \"15 minutes\"\n\n    notification_rules:\n      high_urgency:\n        - \"Push notification immediately\"\n        - \"Phone call after 1 minute\"\n        - \"SMS after 2 minutes\"\n      low_urgency:\n        - \"Push notification\"\n        - \"Email after 5 minutes\"\n```\n\n## Post-Mortem Template\n\n```markdown\n# Post-Incident Review: [Incident Title]\n\n**Date:** YYYY-MM-DD\n**Severity:** SEV[1-4]\n**Duration:** [Start time] to [End time] ([X hours Y minutes])\n**Incident Commander:** [Name]\n**Author:** [Name]\n**Status:** Draft \u002F In Review \u002F Final\n\n## Executive Summary\n[2-3 sentence summary of what happened, the impact, and the resolution]\n\n## Impact\n- **Customer impact:** [Number\u002Fpercentage of customers affected, what they experienced]\n- **Duration of impact:** [How long customers were affected]\n- **Revenue impact:** [Estimated financial impact, if applicable]\n- **Data impact:** [Any data loss or corruption]\n- **SLA impact:** [Any SLA breaches]\n\n## Timeline (all times UTC)\n| Time | Event |\n|------|-------|\n| HH:MM | [First anomaly detected by monitoring] |\n| HH:MM | [Alert fired \u002F customer report received] |\n| HH:MM | [On-call engineer acknowledged] |\n| HH:MM | [Incident declared at SEV level] |\n| HH:MM | [War room established] |\n| HH:MM | [Root cause identified] |\n| HH:MM | [Mitigation applied] |\n| HH:MM | [Service restored] |\n| HH:MM | [Incident resolved] |\n\n## Root Cause\n[Detailed technical explanation of what caused the incident]\n\n## Detection\n- **How was the incident detected?** [Monitoring alert \u002F customer report \u002F manual observation]\n- **Time to detect:** [Time from first anomaly to detection]\n- **Could we have detected sooner?** [Yes\u002FNo, with explanation]\n\n## Response\n- **What went well:**\n  - [List things that worked effectively during response]\n  - [E.g., \"Runbook for database failover was accurate and followed successfully\"]\n  - [E.g., \"Communication to customers was timely and clear\"]\n\n- **What could be improved:**\n  - [List things that slowed or hindered response]\n  - [E.g., \"Took 20 minutes to identify the correct service owner\"]\n  - [E.g., \"Monitoring did not alert on the specific failure mode\"]\n\n## Contributing Factors\n[List all factors that contributed to the incident occurring or being worse than it could have been. This is not about blame - it is about understanding the system.]\n\n1. [Factor 1: e.g., \"Configuration change was not tested in staging\"]\n2. [Factor 2: e.g., \"Alert threshold was too high to catch gradual degradation\"]\n3. [Factor 3: e.g., \"No circuit breaker between Service A and Service B\"]\n\n## Action Items\n| ID | Action | Owner | Priority | Due Date | Status |\n|----|--------|-------|----------|----------|--------|\n| 1 | [Preventive action] | [Name] | P1 | YYYY-MM-DD | Open |\n| 2 | [Detection improvement] | [Name] | P2 | YYYY-MM-DD | Open |\n| 3 | [Process improvement] | [Name] | P2 | YYYY-MM-DD | Open |\n| 4 | [Runbook update] | [Name] | P3 | YYYY-MM-DD | Open |\n\n## Lessons Learned\n[Key takeaways that should be shared broadly]\n\n## Appendix\n- [Link to monitoring dashboards during incident]\n- [Link to relevant log queries]\n- [Link to war room channel archive]\n```\n\n## Post-Mortem Process\n\n```yaml\npost_mortem_process:\n  scheduling:\n    sev1: \"Within 48 hours of resolution\"\n    sev2: \"Within 1 week of resolution\"\n    sev3: \"Within 2 weeks (optional, based on learning potential)\"\n    sev4: \"Not required\"\n\n  meeting_format:\n    duration: \"60-90 minutes\"\n    attendees:\n      required: \"IC, technical lead, scribe, involved engineers\"\n      optional: \"Engineering manager, product manager, affected team leads\"\n    agenda:\n      - \"5 min: Review timeline and facts\"\n      - \"15 min: Walk through root cause and contributing factors\"\n      - \"15 min: Discuss what went well\"\n      - \"15 min: Discuss what could be improved\"\n      - \"15 min: Define and assign action items\"\n      - \"5 min: Identify lessons learned and sharing plan\"\n\n  principles:\n    - \"Blameless: Focus on systems and processes, not individuals\"\n    - \"Factual: Base discussion on data, logs, and observations\"\n    - \"Forward-looking: Prioritize preventive actions over assigning fault\"\n    - \"Complete: Address detection, response, and prevention\"\n    - \"Actionable: Every finding should produce a tracked action item\"\n\n  action_item_tracking:\n    - \"All action items entered into issue tracker (Jira, GitHub Issues)\"\n    - \"Priority assigned based on risk reduction potential\"\n    - \"Owner assigned with due date\"\n    - \"Reviewed in team standups and sprint planning\"\n    - \"Tracked to completion\"\n    - \"Monthly review of open post-mortem action items\"\n```\n\n## Incident Metrics\n\n```yaml\nincident_metrics:\n  mttr:\n    name: \"Mean Time to Resolve\"\n    definition: \"Average time from incident detection to resolution\"\n    target: \"SEV1: \u003C1h, SEV2: \u003C4h\"\n    trending: \"Track monthly, aim for improvement\"\n\n  mttd:\n    name: \"Mean Time to Detect\"\n    definition: \"Average time from incident start to detection\"\n    target: \"\u003C 5 minutes for SEV1\u002F2\"\n    trending: \"Monitors effectiveness of alerting\"\n\n  mtta:\n    name: \"Mean Time to Acknowledge\"\n    definition: \"Average time from alert to engineer acknowledgment\"\n    target: \"\u003C 5 minutes\"\n    trending: \"Monitors on-call responsiveness\"\n\n  incident_frequency:\n    name: \"Incidents per week\u002Fmonth by severity\"\n    target: \"Trending downward\"\n    trending: \"Monitors system reliability improvement\"\n\n  action_item_completion:\n    name: \"Post-mortem action item completion rate\"\n    target: \"> 90% completed on time\"\n    trending: \"Monitors follow-through on improvements\"\n\n  recurring_incidents:\n    name: \"Percentage of incidents with same root cause as previous incident\"\n    target: \"\u003C 10%\"\n    trending: \"Monitors effectiveness of preventive actions\"\n```\n\n## Incident Management Checklist\n\n```yaml\nincident_management_checklist:\n  process_setup:\n    - [ ] Severity levels defined with clear criteria\n    - [ ] Escalation matrix documented\n    - [ ] On-call schedule established and staffed\n    - [ ] War room procedures documented\n    - [ ] Post-mortem template created\n    - [ ] Communication templates prepared (status page, email)\n    - [ ] Incident management tool configured (PagerDuty, OpsGenie)\n\n  per_incident:\n    - [ ] Incident declared with severity level\n    - [ ] War room established (SEV1\u002F2)\n    - [ ] Roles assigned (IC, comms, technical lead, scribe)\n    - [ ] Timeline maintained in real-time\n    - [ ] Status page updated (customer-facing impact)\n    - [ ] Stakeholders notified per communication plan\n    - [ ] Resolution verified with monitoring\n    - [ ] Post-mortem scheduled\n    - [ ] Post-mortem conducted and published\n    - [ ] Action items tracked to completion\n\n  compliance:\n    - [ ] All SEV1\u002F2 incidents have post-mortems\n    - [ ] Incident log maintained for audit evidence\n    - [ ] Metrics reported monthly\n    - [ ] On-call health monitored (pages per person)\n    - [ ] Annual incident response training conducted\n    - [ ] Annual incident response plan test completed\n```\n\n## Best Practices\n\n- Define severity levels with concrete examples so there is no ambiguity during an active incident\n- Implement time-based escalation: if the on-call does not acknowledge, automatically escalate\n- Focus on mitigation first, root cause second: restore service before investigating why it failed\n- Run blameless post-mortems: the goal is to improve systems, not to assign fault to individuals\n- Track post-mortem action items to completion: an unfinished action item means the same incident can recur\n- Monitor incident metrics (MTTR, MTTD, frequency) as leading indicators of system reliability\n- Protect on-call health: track page volume per person and redistribute if someone is overburdened\n- Separate the incident commander role from the technical lead role in SEV1\u002F2 incidents\n- Practice incident response regularly with game days or chaos engineering exercises\n- Archive incident records and post-mortems for compliance evidence and organizational learning\n\n## Limitations\n\n- Guidance and checklists only; not legal advice and not a substitute for a qualified auditor.\n- Docs-only import: upstream templates and scripts not bundled.\n\n### Example\n\n```markdown\nMap this skill's control checklist to our current evidence and list gaps.\n```\n\n> Adapted from [BagelHole\u002FDevOps-Security-Agent-Skills](https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: helper scripts and templates not bundled.\n",{"name":5,"risk":43,"source":44,"license":14,"category":45,"metadata":46,"date_added":49,"description":7,"source_repo":50,"source_type":21,"compatibility":51,"license_source":52},"safe","https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills","security",{"author":47,"version":48},"devops-skills","1.0","2026-09-20","BagelHole\u002FDevOps-Security-Agent-Skills","Checklist and framework guidance; no privileged tooling required. Apply controls through your own change process.","https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fincident-management","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill incident-management",{"tool":64,"command":65},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill incident-management",{"tool":67,"command":68},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill incident-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fincident-management\u002FSKILL.md",true,[],[73,100,124,146,174,198],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":84,"publishedAt":38},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[85,86,87,88,89,90,75,91,33,92,32,93,21,28,94,95,96,97,98,99],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","access","only","active","critical","scope","scripts","relevant","implementing",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":38},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[107,108,109,110,111,112,113,114,115,116,117,118,119,93,120,21,121,122,95,123],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":38},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[131,132,133,43,29,134,135,35,136,137,138,139,140,21,28,141,142,143,144,145],"transcript","youtube transcript","youtube","codex","research","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":163,"publishedAt":38},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[152,155,158],{"categoryNo":153,"categoryName":154,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":156,"categoryName":157,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":159,"categoryName":160,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[131,132,133,164,43,165,29,134,35,166,167,168,169,138,170,21,28,171,172,173],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":184,"publishedAt":38},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[180,183],{"categoryNo":181,"categoryName":182,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":156,"categoryName":157,"taxonomyType":82,"taxonomyTypeDesc":83},[133,185,186,111,43,187,188,189,190,35,168,191,192,193,194,28,195,141,196,197],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":205,"publishedAt":38},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[204],{"categoryNo":153,"categoryName":154,"taxonomyType":82,"taxonomyTypeDesc":83},[206,133,207,208,43,165,166,209,210,167,168,169,138,211,170,21,28,171,212,144],"youtube full","full","google","server","dlp","credits","automatic"]