Skip to main content

After Action Report

Skill Verified Active

Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.

Purpose

To help teams systematically analyze past events to capture actionable lessons and improve future outcomes, fostering a blameless learning culture.

Features

  • Structured AAR/postmortem generation
  • Blameless analysis framework
  • Timeline reconstruction and analysis
  • Root cause analysis (Five Whys, causal chain)
  • Identification of contributing factors and successes
  • Generation of specific, owned, and dated action items
  • Markdown document output

Use Cases

  • Running postmortems after incidents
  • Conducting retrospectives after launches or sprints
  • Documenting lessons learned at project closeout
  • Analyzing recurring issues to find systemic causes

Non-Goals

  • Real-time incident response
  • Pre-launch planning and runbooks
  • Performing the actual root cause investigation (gathers data for it)

Installation

npx skills add rampstackco/claude-skills

Runs the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.

Quality Score

Verified
100 /100
Analyzed about 14 hours ago

Trust Signals

Last commit3 days ago
Stars168
LicenseMIT
Status
View Source

Similar Extensions

Incident Response

100

Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers on incident response, production incident, outage, service down, site down, P0, P1, severity, downtime, on-call, incident commander, status page, postmortem prep. Also triggers when something is actively broken in production and the user is figuring out what to do.

Skill
rampstackco

Incident Commander

98

Incident Commander Skill

Skill
alirezarezvani

Incident Followup Audit

97

Audits post-incident engineering follow-through after a sev or incident to verify whether the durable follow-up happened: regression tests, monitors, docs, runbooks, ownership updates, tickets, rollback learnings, and remaining backlog. Use when a user asks whether incident follow-up is complete, what still needs to be done after a postmortem, or how to close the engineering loop. Do NOT use for live incident response, root-cause analysis, or a generic bug hunt unrelated to an incident.

Skill
ckorhonen

Teach Guidance

100

Guide a person in becoming a better teacher and explainer. AI coaches content structuring, audience calibration, explanation clarity, Socratic questioning technique, feedback interpretation, and reflective practice for technical presentations, documentation, and mentoring. Use when a person needs to present technical content and wants preparation coaching, wants to write better documentation or tutorials, struggles to explain concepts across expertise levels, is mentoring a colleague, or is preparing for a talk or knowledge-sharing session.

Skill
pjt222

Prepare Inspection Readiness

100

Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.

Skill
pjt222

External Context

100

Invoke parallel document-specialist agents for external web searches and documentation lookup

Skill
Yeachan-Heo

© 2025 SkillRepo · Find the right skill, skip the noise.