redemption-arc
From the author
Zuko's redemption arc for incidents and postmortems. Use for an outage, a bad deploy, data loss, a production incident, "what went wrong", "write the postmortem", or owning a mistake. Stabilizes first, then builds a blameless timeline, finds the root cause, and turns the lesson into structure.
Install
npx skills add tmcfarlane/team-avatar --skill redemption-arc -a claude-code
Installs to .claude/skills/redemption-arc/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- incident-responseanthropics/knowledge-work-pluginsRun an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.OfficialWriting★ 33.8K
- reflectOutlineDriven/outline-driven-developmentUse when a completed task needs reflection on invoked skills to propose and apply approved improvements. Not for remote, credential, publish, deploy, or irreversible changes.DevOps★ 55
- incident-responderOneWave-AI/claude-skillsProduction incident response automation. Reads logs, checks recent deploys, identifies root cause, suggests fixes, drafts incident comms, creates post-mortem templates. Severity classification (SEV1-4), escalation paths, status page updates. Generates incident-report.md with timeline, root cause, impact assessment, remediation steps, and prevention measures.DevOps★ 398
- postmortemhashgraph-online/awesome-codex-pluginsExplain why a change, incident or session went as it did, separating proven causes from coincidence. Use when: asked for a postmortem, retro or root-cause write-up.Writing★ 1.4K
- incident-postmortemgithub/awesome-copilotUse when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem. Triggers on phrases like "write a post-mortem", "incident review", "what went wrong", "outage report", "root cause analysis", or "RCA". Covers timeline reconstruction, contributing factor analysis, impact quantification, and action item generation with owners.Writing★ 40.6K
- after-action-reportrampstackco/claude-skillsRun 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.Engineering★ 1K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in