ralph-operations
mikeyobrienUse when managing Ralph orchestration loops, analyzing diagnostic data, debugging hat selection, investigating backpressure, or performing post-mortem analysis
incident-responder
DokhacgiakhoaExpert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management. Masters incident command, blameless post-mortems, error budget management, and system reliability patterns. Handles critical outages, communication strategies, and continuous improvement.
post-mortems-retrospectives
RefoundAIHelp users run effective post-mortems and retrospectives. Use when someone is reviewing a project that succeeded or failed, wants to establish learning practices, is dealing with failure aftermath, or needs to improve team learning loops.
managing-incidents
ancolemanGuide incident response from detection to post-mortem using SRE principles, severity classification, on-call management, blameless culture, and communication protocols. Use when setting up incident processes, designing escalation policies, or conducting post-mortems.
post-mortem
boshu2Wrap up completed work. Council validates the implementation, then extract learnings. Triggers: "post-mortem", "wrap up", "close epic", "what did we learn".
campaign-review
davekilleenPost-mortem on recent campaign
incident-review
davekilleenPost-mortem on incidents
ops-incident-response
LerianStudioStructured workflow for production incident management following SRE best practices. Covers incident declaration, triage, coordination, resolution, and post-mortem.
runbooks-incident-response
TheBushidoCollectiveUse when creating incident response procedures and on-call playbooks. Covers incident management, communication protocols, and post-mortem documentation.
incident-response
korallisRespond 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.
incident
htlin222Handle production incidents with urgency. Use when production issues occur for debugging, fixes, and post-mortems.
Regression Suite from Bug Reports
PramodDuttaConvert bug reports and incident post-mortems into automated regression tests that prevent recurrence of previously discovered defects.
postmortem
neurofooBlameless post-mortem incident analysis with timeline, root cause, and action items. Use after outages, security incidents, project failures, or any event you want to prevent recurring.
project-retrospective
jamditisGenerate LESSONS.md retrospective files that capture institutional knowledge, especially failures. Use when closing out journalism projects, investigations, events, or publications. Includes templates for research projects, event post-mortems, editorial tools, and publications.
SRE Engineer
404kidwizExpert Site Reliability Engineer specializing in SLOs, error budgets, and reliability engineering practices. Proficient in incident management, post‑mortems, capacity planning, and building scalable, resilient systems with a focus on reliability, availability, and performance.
reviews-retros-reflection
lyndonklUse when conducting sprint retrospectives, project post-mortems, weekly reviews, quarterly reflections, after-action reviews (AARs), team health checks, process improvement sessions, celebrating wins while learning from misses, establishing continuous improvement habits, or when user mentions "retro", "retrospective", "what went well", "lessons learned", "review meeting", "reflection", or "how can we improve".
postmortem-generator
palladiusCreates a PostMortem given enough context about an incident/outage. Will guide user to timeline, action items/bugs, and finally draft a Google Doc with the results.
incident-responder
omer-metinProduction incident response - from detection through resolution to post-mortem. Effective communication, systematic investigation, and blameless learning from failuresUse when "incident, outage, production issue, site down, on-call, post-mortem, war room, severity, pages, alerts, rollback, incident, outage, on-call, post-mortem, production, reliability, SRE, communication" mentioned.
site-reliability-engineer
nahisahoProduction monitoring, observability, SLO/SLI management, and incident response. Trigger terms: monitoring, observability, SRE, site reliability, alerting, incident response, SLO, SLI, error budget, Prometheus, Grafana, Datadog, New Relic, ELK stack, logs, metrics, traces, on-call, production monitoring, health checks, uptime, availability, dashboards, post-mortem, incident management, runbook. Completes SDD Stage 8 (Monitoring) with comprehensive production observability: - SLI/SLO definitions and tracking - Monitoring stack setup (Prometheus, Grafana, ELK, Datadog, etc.) - Alert rules and notification channels - Incident response runbooks - Observability dashboards (logs, metrics, traces) - Post-mortem templates and analysis - Health check endpoints - Error budget tracking Use when: user needs production monitoring, observability platform, alerting, SLOs, incident response, or post-deployment health tracking.
incident-management
dralgorhythmHandle production incidents effectively. Use when responding to outages, conducting post-mortems, or improving reliability. Covers incident response and blameless culture.
post-mortems-retrospectives
liqiongyuRun blameless post-mortems & retrospectives and produce a Post-mortems & Retrospectives Pack (brief + agenda, facts/timeline, contributing factors + root causes, decisions + action tracker, kill criteria, learning dissemination plan). Use for postmortem, post-mortem, retrospective, retro, after action review, lessons learned. Category: Leadership.
security-incident-reporting
dirnbauerSecurity Incident Report templates drawing from NIST/SANS. DDoS post-mortem, CVE correlation, timeline documentation, and blameless root cause analysis. Use when working with incident report, post-mortem, sir, ddos analysis, security reporting, root cause analysis, cve correlation, nist 800-61.
debugging
krzysztofsurdySystematic debugging workflow — reproduce, investigate, hypothesize, fix, and prevent. Covers root cause analysis, bug category strategies, evidence-based diagnosis, and post-mortem documentation.
learn-from-session
doodledoodAnalyze Claude Code sessions to learn what went right or wrong and suggest high-confidence improvements to skills. Use this Skill when asked to analyze a session, learn from a session, or review workflow effectiveness. It accepts a session UUID, a .jsonl session file path, or inline commentary; automatically locates and reads session files when given an ID; and creates a persistent analysis log (/tmp/session-analysis-{id-short}-{timestamp}.md). Outputs contain only high-signal recommendations that would have prevented specific rework, each tied to exact message numbers and justified by the “3/3 counterfactual” test: (1) identify the rework message(s), (2) show the skill change would have triggered before the rework, and (3) show the change would have produced correct output initially. Use cases include post-mortems, CI feedback for skill authors, repository hygiene, and training-data corrections. Core advantages are reduced rework, actionable fixes with reproducible evidence, and a clear audit trail; if a session file cannot be found, the Skill prompts the user for the path or corrected ID.
session-review
philoserfAnalyzes the current session to extract patterns, preferences, and learnings. Produces a structured review capturing what worked and what to improve. Use for session retrospectives, debriefs, post-mortems, or when reflecting on insights worth remembering.
incident-responder
agent-skills-hubExpert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management. Masters incident command, blameless post-mortems, error budget management, and system reliability patterns. Handles critical outages, communication strategies, and continuous improvement. Use IMMEDIATELY for production incidents or SRE practices.
postmortem-author
kingdonGenerate Sunkworks-style post-mortem reports with timeline reconstruction, failure pattern recognition, honest technical assessments, and recovery playbooks. Trigger with /postmortem
lessons-learned
flonatStructured, blameless post-mortem process for incidents, mistakes, or stalled sessions. Converts problems into systematic improvements (skills, guards, docs, hooks). Use when something went wrong or when stakeholders ask 'how do we prevent this?'.
lessons-learned
flonatStructured post-mortem after incidents, mistakes, or stuck sessions. Transforms problems into systematic improvements (skills, guards, docs, hooks). Use when something went wrong or when asking “how do we prevent this.”
design-on-call-rotation
pjt222Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or alert fatigue, improving incident response times, or after a post-mortem identifies handoff issues.
conduct-post-mortem
pjt222Conduct a blameless post-mortem analysis after an incident. Build timeline reconstruction, identify contributing factors, and generate actionable improvements. Focus on systemic issues rather than individual blame. Use after any production incident or service degradation, following a near-miss, when investigating recurring issues, or to share systemic learnings across teams.
conduct-post-mortem
pjt222Conduct a blameless post-mortem analysis after an incident. Build timeline reconstruction, identify contributing factors, and generate actionable improvements. Focus on systemic issues rather than individual blame. Use after any production incident or service degradation, following a near-miss, when investigating recurring issues, or to share systemic learnings across teams.
incident-response-commander
organvm-iv-taxisGuides teams through IT outages and security incidents, providing structured workflows for detection, containment, eradication, and post-mortem analysis.
design-on-call-rotation
pjt222Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or alert fatigue, improving incident response times, or after a post-mortem identifies handoff issues.
parallel-retrospective
jimmc414Analyze completed parallel workflows for lessons learned. Use when: reviewing workflow execution quality, identifying process improvements, evaluating skill effectiveness, post-mortem analysis after parallel work, assessing planning accuracy. Triggers: retrospective, review, post-mortem, lessons learned, workflow analysis, evaluate parallel, workflow quality, planning assessment.
post-mortems-retrospectives
jasonmeansHelp users run effective post-mortems and retrospectives. Use when someone is reviewing a project that succeeded or failed, wants to establish learning practices, is dealing with failure aftermath, or needs to improve team learning loops.
incident-responder
oki3505FExpert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management. Masters incident command, blameless post-mortems, error budget management, and system reliability patterns. Handles critical outages, communication strategies, and continuous improvement. Use IMMEDIATELY for production incidents or SRE practices.
incident-responder
haniakrim21Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management. Masters incident command, blameless post-mortems, error budget management, and system reliability patterns. Handles critical outages, communication strategies, and continuous improvement. Use IMMEDIATELY for production incidents or SRE practices.
20-05-debrief
CygnusfearWrite a full-fidelity post-mortem after completing development work. Use after any merge, feature completion, or significant work session.
20-04-post-merge-hygiene
CygnusfearPost-merge cleanup — document implementation, write post-mortem, update docs, close tickets, clean worktrees and branches.