- Home
- Skills
- Testing & Debugging
- Incident Postmortem Timeline
Works with the AI Agents you already use
Incident Postmortem Timeline
Incident postmortem timeline: merges app, web, deploy and database logs into one timeline for your outage review. Local and read-only.
$5
Incident Postmortem Timeline
Example session with this skill installed
/incident-timeline-builder deploy.log app.log nginx.log db.log --tz UTC
- Read your context and instructions
- Compiled the incident postmortem timeline
Illustrative. The four log files are invented and use four different time formats; the report below is what the script prints.
INCIDENT TIMELINE 2026-10-30 09:40:00 to 10:22:10 (UTC), 20 events from 4 file(s)
Key moments
change before the first error 09:55:02 [deploy.log:1] 2026-10-30T11:55:02+02:00 deploy: starting rollout of v2.14.0 to 4 pods
change before the first error 09:57:55 [deploy.log:2] 2026-10-30T11:57:55+02:00 deploy: pod api-3 restarted with v2.14.0
first error 09:58:05 [db.log:3] {"ts":1793354285000,"level":"error","msg":"FATAL: remaining connection slots are reserved"}
last error 09:58:27 [nginx.log:3] 10.0.0.7 - - [30/Oct/2026:09:58:27 +0000] "POST /api/pay HTTP/1.1" 502 157 "-" "app/2.14"
error window 0.4 minutes between first and last error line
first line after the last error 10:20:30 [deploy.log:3] 2026-10-30T12:20:30+02:00 deploy: rollback to v2.13.2 complete
Timeline (errors marked !!, warnings !, changes >>, recovery ++)
09:40:00 [db.log] {"ts":1793353200000,"level":"info","msg":"checkpoint complete"}
---- quiet for 10.0 minutes ----
09:50:01 [app.log] 2026-10-30 09:50:01,120 INFO api request served in 41 ms
---- quiet for 5.0 minutes ----
09:55:02 >> [deploy.log] 2026-10-30T11:55:02+02:00 deploy: starting rollout of v2.14.0 to 4 pods
09:57:55 >> [deploy.log] 2026-10-30T11:57:55+02:00 deploy: pod api-3 restarted with v2.14.0
09:57:58 ! [db.log] {"ts":1793354278000,"level":"warn","msg":"too many connections for role app (limit 100)"}
09:58:05 !! [db.log] {"ts":1793354285000,"level":"error","msg":"FATAL: remaining connection slots are reserved"}
09:58:12 ! [app.log] 2026-10-30 09:58:12,401 WARN db pool: waiting for a free connection (timeout 5000 ms)
09:58:20 !! [app.log] 2026-10-30 09:58:20,010 ERROR checkout failed: could not get a database connection (x4 until 09:58:23) (+4 continuation line(s))
09:58:25 !! [nginx.log] 10.0.0.5 - - [30/Oct/2026:09:58:25 +0000] "POST /api/pay HTTP/1.1" 502 157 "-" "app/2.14" (x3 until 09:58:27)
---- quiet for 22.1 minutes ----
10:20:30 >> [deploy.log] 2026-10-30T12:20:30+02:00 deploy: rollback to v2.13.2 complete
10:20:55 [db.log] {"ts":1793355655000,"level":"info","msg":"connection count back under limit"}
10:21:00 [app.log] 2026-10-30 10:21:00,000 INFO db pool: connections available again
10:21:05 [app.log] 2026-10-30 10:21:05,000 INFO api request served in 38 ms
10:21:30 [nginx.log] 10.0.0.5 - - [30/Oct/2026:10:21:30 +0000] "POST /api/pay HTTP/1.1" 200 412 "-" "app/2.13"
10:22:10 >> [deploy.log] 2026-10-30T12:22:10+02:00 deploy: service healthy
Limits: clocks of different machines can differ by seconds or more, so order within a few seconds across files is uncertain. Kinds are guessed from words in the line. Lines without a time are attached to the line before them. Credentials found in lines are masked.
Next steps
- Start at the changes listed before the first error; treat them as leads, not as proof.
- Use the Timeline template in the reference file to write the postmortem section from these lines only.
Connects securely to your tools. The creator never sees your data.
About this skill
Get the timeline half of a postmortem in one command. Point it at the logs of an incident (application, web-server access log, deploy log, database log, JSON lines) and it merges them into one time-ordered list, converts time zones, finds the first and the last error, lists the deploys and restarts that came just before the first error, marks quiet gaps, collapses repeated lines and shows the first line after the last error. It reads ISO 8601 (with or without an offset), Python logging, syslog, web-server access logs and epoch seconds or milliseconds. A reference file shows how to turn the report into the Timeline section of a postmortem and what not to conclude from it.
What it reads and writes: only the log files you name; it writes nothing. If you paste logs into the chat, the skill first saves each one as its own file in your current folder and tells you. No network connection, no environment variables, nothing to install. Tokens, bearer headers and passwords found in printed lines are masked.
Honest limits: clocks on different machines can differ, so order within a few seconds across files is uncertain. Error, warning, change and recovery are guessed from words in the line. A change before the first error is a lead, not a cause, and the timeline cannot show what was not logged. Needs Python 3.9+.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.
Needs Python 3.9+. Clock differences between machines make order within a few seconds uncertain; kinds are guessed from words; a change before the first error is a lead, not a cause; it cannot show what was not logged.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 15 days ago
- Software
Python
Permissions
File Scopes
Reads only the log files you name; no network connection, no environment variables, no other files. When you paste logs into the chat, the skill first saves each as its own file in the current folder. Words such as token or password appear in the code as patterns used to mask secrets in printed lines.