Skip to main content

Command menu

Jump to a page or search the catalog

AI Tools & Scripts

Incident Postmortem Writer: Blameless Report, Timeline and Action Items from Your Logs

For engineering teams after an outage: give your agent the chat export, alerts, logs and deploy history and get a blameless postmortem with a sourced one-timezone timeline, a causal chain, checkable action items as CSV, and a customer update draft. تقرير ما بعد الحادثة من أدلتك أنت.

$4.00

What you get: 1 file · 43.72 KB · ZIP

See purchase options

Product description

English

For engineering teams who have to explain an incident to people who were not there.

Give your agent the raw evidence: the incident channel export, alerts, logs, deploy history and notes. The agent drafts a blameless postmortem for your team to review before publishing internally, a short update for customers, and the action items as a CSV.

What it writes each run

  • postmortem.md: a plain summary, impact with numbers taken only from the evidence, a timeline in one time zone with a source for every row, detection and response, a numbered causal chain that separates trigger, root cause and contributing factors, what went well, what went badly, where you got lucky, action items, open questions and a gap list.
  • status_update.md: a short customer-facing update, drafted without internal names or blame for you to review.
  • action_items.csv: the same action items with id, type, owner role, priority and done-condition.

Timeline first, from the evidence

A bundled Python script (standard library, no network calls) reads timestamped lines from several files, including ISO 8601, web server and syslog formats, epoch times and time-only chat lines. It converts them to one time zone from the offsets you give, sorts them, and flags long silences, out-of-order lines, minute-precision times and assumed zones. The agent builds the timeline before any cause is discussed.

Facts apart from interpretation

The skill instructs the agent to keep summary, impact, timeline and detection to what the evidence shows, to cite evidence for each link of the causal chain or mark it inferred, to show both sides when sources disagree, and to write an unsupported cause as not established.

Blameless by rule

The skill instructs the agent to refer to roles and systems in place of named people, to rewrite phrases such as "should have" and "failed to" from a bundled table, and to keep "human error" out of the chain. Review the draft for names and blame wording before sharing.

Honest about its limits

It works from what you provide, and the agent is instructed to mark gaps [NEEDS: ...]. Line references are written by the agent and should be spot-checked by someone who was there. The customer update is a draft, and formal regulatory or contractual notices are outside its scope.

Arabic

On request all three files are written in Arabic; system names, commands, log excerpts and the CSV header stay in Latin script. Arabic output was tried on one test case and was not reviewed by a second native reader; check it before sharing.

In the download: SKILL.md, the script, four reference files (method, blameless language, action items, Arabic notes), three templates, and one complete example: five evidence files from a database pool incident in, the three deliverables out, with nine action items and the raw merged timeline.

How it was tried: Tried on two cases (a database pool incident in English, a certificate expiry incident in Arabic); the download includes one worked example in English. The bundled script has 17 unit tests.

بالعربي

لفرق الهندسة التي عليها أن تشرح حادثة لمن لم يحضرها.

أعطِ وكيلك الأدلة الخام: تصدير قناة الحادثة، والتنبيهات، والسجلات، وسجل الإصدارات، والملاحظات. تستلم تقرير ما بعد الحادثة بلا لوم، ونصًّا قصيرًا للعملاء، وقائمة الإجراءات في ملف CSV.

ماذا تستلم

  • ملف postmortem.md: ملخص، وأثر بأرقام من الأدلة فقط، وتسلسل زمني بتوقيت واحد مع مصدر لكل سطر، وسلسلة سببية تفصل الشرارة عن السبب الجذري والعوامل المساعدة، وأسئلة مفتوحة.
  • ملف status_update.md: تحديث موجز للعملاء بلا أسماء داخلية.
  • ملف action_items.csv: الإجراءات، ولكل إجراء نوع ودور مسؤول وأولوية وشرط إنجاز يمكن التحقق منه.

التسلسل الزمني أولًا

سكربت بايثون مرفق يعمل على جهازك بلا اتصال بالشبكة: يقرأ الأسطر ذات الأوقات من عدة ملفات، ويحوّلها إلى توقيت واحد، ويرتّبها، ويعلّم الفجوات والأسطر غير المرتبة.

بلا لوم وبلا تخمين

تنص التعليمات على الإشارة إلى الأدوار لا إلى الأشخاص، وعلى ألا يُذكر سبب لا تسنده الأدلة بل يُكتب أنه غير مثبت. راجع المسودة قبل مشاركتها.

حدود واضحة

التقرير مسودة للمراجعة، وأرقام الأسطر المذكورة تحتاج تدقيقًا ممن حضر الحادثة. وتحديث العملاء مسودة، وقرار النشر والتعويض لك.

العربية

عند الطلب تُكتب الملفات الثلاثة بالعربية، وتبقى أسماء الأنظمة والأوامر ومقتطفات السجلات بالحروف اللاتينية.

Questions / أسئلة

What evidence does it need? / ما الأدلة التي يحتاجها؟

Whatever you have: an incident channel export, alerts, logs, deploy history, notes. With no evidence at all it asks for material instead of writing a generic report. ما لديك من محادثات وتنبيهات وسجلات، ولا يكتب بلا أدلة.

Does it guess the root cause? / هل يخمّن السبب الجذري؟

The skill instructs the agent not to: each link of the causal chain is to cite evidence or be marked inferred, and an unsupported cause is to be written as not established with what would settle it. Check the chain against your evidence. التعليمات تمنع التخمين، وراجع السلسلة مقابل أدلتك.

How does it keep the report blameless? / كيف يبقى التقرير بلا لوم؟

The skill instructs the agent to write roles in place of people, to paraphrase chat quotes and to leave out names and handles, with a bundled table of rewrites for phrases such as failed to or should have. Search the files for names before sharing. التعليمات تطلب ذكر الأدوار لا الأسماء، وراجع الملفات قبل مشاركتها.

How are different time zones handled? / كيف يعالج اختلاف التوقيت؟

You give each source's offset and the script converts every timed line to one zone, sorts them, and flags long silences, out-of-order lines and assumed zones. تُحوَّل كل الأوقات إلى توقيت واحد مع تعليم الفجوات.

Are the action items usable as they are? / هل الإجراءات جاهزة للاستعمال؟

Each has a type (prevent, detect or mitigate), an owner role, a priority and a done-condition a third person can verify. Names and due dates are for you to assign in your tracker. لكل إجراء دور مسؤول وشرط إنجاز، والأسماء والمواعيد عليك.

Can I publish the customer update as written? / هل أنشر تحديث العملاء كما هو؟

Treat it as a draft. The skill instructs the agent to leave out internal names and unproven causes and to word planned actions as planned; what to share and any compensation decision are yours. اعتبره مسودة، وقرار النشر لك.

Can it be in Arabic? / هل يكون بالعربي؟

Yes, as an added option: all three files in Arabic, with system names, commands, log excerpts and the CSV header left in Latin script. نعم، مع بقاء أسماء الأنظمة والأوامر كما هي.

What you get

1 file · 43.72 KB

  • incident-postmortem-writer-1.0.0.zipZIP · 43.72 KB
LicenseCommercial use allowed
PublishedNov 14, 2026
File size43.72 KB
File formatZIP
Versionv1.0

Tags

postmortemincident reportblamelessincident timelinesreon-callroot causearabicai agent skill
R
RR HH

Frequently asked questions

Do I get access instantly?

Yes. This is a digital product - you can download it right after checkout, straight from your library.

Can I use it for commercial projects?

Yes. Commercial use is allowed: use it in your own business and in things you sell. You may not resell or redistribute the file itself.

What's your refund policy?

You can request a refund within 30 days. If something isn't right, request it from your order and the Getly team reviews it.

What file formats and sizes will I get?

You'll download 1 file - ZIP - 43.72 KB in total.

Do I get free updates?

Yes - when the seller ships a new version, you can re-download the latest files from your library at no extra cost. Check the changelog for recent updates.

Price

$4.00