Install
$ agentstack add skill-clarentcinematics-codex-skills-for-enterprise-incident-postmortem-assistant ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Incident Postmortem Assistant
Workflow
- Identify incident scope, affected systems, customer or business impact, timeline, responders, and available evidence.
- Separate observed facts from hypotheses, assumptions, downstream symptoms, and missing context.
- Build a blameless narrative with impact, detection, mitigation, resolution, and learning points.
- Convert lessons into corrective actions with owners and due dates only when stated.
- Flag unresolved questions, evidence gaps, repeated timestamps, ambiguous ownership, and follow-up needs.
Script-Assisted Workflow
When given a timeline or incident notes file, run scripts/check_incident_timeline.py --input before drafting the postmortem. Use --json when structured evidence is needed. Treat the script output as deterministic evidence about timeline quality, not as the final root cause.
Output Standard
Use this structure by default:
- Incident Summary: scope, status, impact, and confidence.
- Timeline: observed events with timestamps, owners, and actions when stated.
- Impact: affected users, services, duration, and business effect; use
Not statedwhen absent. - Root-Cause Hypotheses: ranked hypotheses with evidence and uncertainty.
- Contributing Factors: process, system, monitoring, release, dependency, or handoff factors.
- Corrective Actions: action, owner, due date, and validation method when stated.
- Open Questions: missing facts needed before publication.
- Caveats: source limitations and non-inferred fields.
Rules
- Keep the postmortem blameless and evidence-grounded.
- Do not invent severity, customer impact, owners, dates, root cause, or corrective action commitments.
- Label hypotheses as hypotheses until supported by source evidence.
- Treat unresolved timeline gaps, repeated timestamps, and missing owners as review risks.
- Escalate legal, customer-notification, or compliance conclusions to human review.
References
Read references/postmortem-rubric.md when preparing a formal postmortem, executive incident recap, or corrective-action review.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ClarentCinematics
- Source: ClarentCinematics/Codex-Skills-for-Enterprise
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.