More screenshots
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
DeepSeek
Muse+22 moreClaude CodeCursorCodex CLIDeepSeekMuse
Dots
Manus
Grok
Grok Bot+18 agentsIncident Timeline Evidence Review
Diagnose and repair incident timelines, source evidence, action chronology, conflicting timestamps, decisions, and recovery claims.
$1
Incident Timeline Evidence Review
Example session with this skill installed
Review the timeline for the DB outage. Sources: slack-export.txt and db-logs.csv in /docs. Map the detection to the first failover attempt and flag any gaps.
- Read your context and instructions
- Compiled the incident timeline evidence
- Generated the data export
I have analyzed the Slack export and database logs to reconstruct the timeline for the database outage. I focused on the period between the first 'High Latency' alert and the successful failover completion.
Incident Timeline & Evidence Review
Source Register
| ID | Source | Type | Time Range (UTC) |
|---|---|---|---|
| S1 | slack-export.txt | Communication | 14:02 - 15:45 |
| S2 | db-logs.csv | System Logs | 13:50 - 16:00 |
Evidence-Backed Chronology
| Timestamp (UTC) | Event | Source | Status |
|---|---|---|---|
| 14:02:12 | First Latency 500ms+ alert triggered | S2 | Verified |
| 14:05:45 | On-call engineer (Alice) acknowledges in #ops | S1 | Verified |
| 14:10:00 | First failover command issued via CLI | - | GAP |
| 14:12:30 | Log entry: Secondary node promotion failed: timeout | S2 | Verified |
| 14:15:20 | Decision to manually restart primary | S1 | Verified |
Conflicts and Gaps
Gap: Missing CLI Logs. S1 mentions a failover attempt at 14:10:00, but S2 shows no connection attempts until 14:12:30. The actual command execution log is missing from the workspace.
*
Conflict: Detection Time. The official status page (referenced in S1) claims detection at 14:00:00, but the first log-based alert (S2) did not fire until 14:02:12.
Missing Evidence Needed
- CLI History/Audit Log: To confirm the exact time and parameters of the 14:10:00 failover attempt.
- Monitoring Config: To understand the 2-minute delay between user-reported latency and system alerts.
Next steps
- Retrieve the shell history from the jump host used by Alice.
- Update the draft post-mortem to reflect the 132-second detection lag.
- Verify if the secondary node timeout was due to network partition or resource exhaustion.
db-logs.csv
CSV · data export
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Incident Timeline Evidence Review is a bounded ToolForge Labs workflow. Diagnose and repair incident timelines, source evidence, action chronology, conflicting timestamps, decisions, and recovery claims. Works from full repositories or partial context such as snippets, logs, configuration, traces, and architecture notes. Produces concrete repairs or evidence-backed review outputs while preserving existing product/security policy.
It works from a full repository or partial evidence such as snippets, logs, configuration, traces, tickets, and architecture notes. The skill preserves existing product and security policy, separates verified facts from assumptions, avoids invented execution claims, and produces concrete repair or review steps with focused deterministic validation or traceable evidence.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Does not certify legal, compliance, or production readiness. Cannot verify documents or logs not explicitly provided in the workspace or prompt context.
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 2 months ago
Permissions
Use a clean branch or a controlled review workspace. Supply repository files, logs, traces, configuration, or evidence needed for the task. Review all patches/findings before merge or operational action; keep production credentials and destructive production actions out of the workflow.