Incident Postmortem Framework
v1.0.0Generates structured blameless incident postmortems from raw notes, producing summaries, timelines, root cause analyses, impacts, action items, and preventio...
⭐ 0· 448·1 current·1 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and runtime instructions align: the skill transforms incident notes into structured postmortems and does not request unrelated binaries, credentials, or config paths.
Instruction Scope
SKILL.md contains only stepwise guidance for producing postmortems (ask clarifying questions, generate markdown, flag gaps, suggest prevention measures). It does not instruct reading system files, environment variables, or sending data to external endpoints beyond an informational link.
Install Mechanism
No install spec and no code files — instruction-only skill. This is the lowest-risk install profile (nothing is written to disk by the skill itself).
Credentials
The skill declares no required environment variables, credentials, or config paths. Nothing requested is disproportionate to creating written postmortems.
Persistence & Privilege
always is false and the skill does not request permanent presence or elevated system privileges. Autonomous invocation is allowed by default for skills on the platform, but this skill doesn't combine that with any high-risk access.
Assessment
This skill appears coherent and only provides instructions for formatting incident postmortems. Before using it, avoid pasting sensitive data (secrets, full logs with tokens, or personal data) into the prompt because anything you provide will be used to generate the document. Verify severity/duration fields and any numeric estimates (revenue impact, affected users) — the model may hallucinate or round figures. Review action-item owners and deadlines before publishing, and be aware the README contains a commercial link (AfrexAI context packs) but the skill does not itself contact that site. If you need the agent to access external systems (PagerDuty, Slack, ticketing), prefer explicit integrations that require scoped credentials rather than pasting exported data into the prompt.Like a lobster shell, security has layers — review code before you run it.
SREvk974mca8q06rbwcxtbcczsgen981m16bblamelessvk974mca8q06rbwcxtbcczsgen981m16bincidentvk974mca8q06rbwcxtbcczsgen981m16blatestvk974mca8q06rbwcxtbcczsgen981m16bpostmortemvk974mca8q06rbwcxtbcczsgen981m16broot-causevk974mca8q06rbwcxtbcczsgen981m16b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
