Works with the AI Agents you already use
incident timeline and resolution summary generator
This skill takes raw event logs, impact data, and follow-up records to generate a factual, access-controlled timeline and resolution summary.
$2.99
incident timeline and resolution summary generator
Example session with this skill installed
Generate an incident timeline for INC-90210. I have the event logs and impact windows. My access scope is limited to the 'Payments' service and 'Internal' classification. analysis_as_of: 2023-10-27.
- Read your context and instructions
- Compiled the incident timeline
I have processed the records for incident INC-90210 based on the 12 events and 2 impact windows provided. All calculations were performed via script to ensure precision.
Incident Timeline and Resolution Summary — INC-90210, 2023-10-27T14:00:00Z
1. Scope, sources and assumptions
- Incident: INC-90210 (Payments Service)
- Priority: P1 - Critical
- Sources: E1 (SysLog), E2 (Ticketing System)
- Access Scope: Payments, Classification: Internal
- Counts: 12 events processed, 0 excluded.
2. Timeline
| # | Time (UTC) | Type | Elapsed min | Gap min | Team | Summary | Source | Flags |
|---|---|---|---|---|---|---|---|---|
| 1 | 08:00:00 | detected | 0 | 0 | Monitoring | Automated alert for API 500 errors | E1 | |
| 2 | 08:10:00 | acknowledged | 10 | 10 | DevOps | On-call engineer acknowledged | E2 | |
| 3 | 09:30:00 | service_restored | 90 | 80 | DevOps | Database failover completed | E2 | |
| 4 | 11:00:00 | resolved | 180 | 90 | Support | Verified with stakeholders | E2 |
3. Durations and targets
| Measure | Measured | Target | Margin | Status |
|---|---|---|---|---|
| Time to Acknowledge | 10 min | 15 min | +5 min | MET |
| Time to Restore | 90 min | 60 min | -30 min | BREACHED |
4. Restoration evidence
- Status: Unverified
- Restoration Event: 09:30:00 (Database failover)
- Check Event: None found. Information gap — organizational validation required.
5. Impact
| Window Start | Window End | Measured User-Min | Status |
|---|---|---|---|
| 08:00:00 | 09:30:00 | 45,000 | Analytical estimate — validation required |
6. Pending follow-ups
- DB Optimization: Database Team, Due: 2023-11-05 (0 days overdue)
7. Proposed actions (drafts, not performed)
- Close INC-90210: Management decision required
- Send summary to Service Owner: Management decision required
8. Warnings and items for human review
- W001: No restoration_check event found. Manual verification of service stability required.
This summary supports, and does not replace, the judgment of the accountable service owner.
Next steps
- Provide the restoration check log to verify the fix.
- Review the breached restoration target with the DevOps team.
- Approve the draft follow-up actions for the Database Team.
Connects securely to your tools. The creator never sees your data.
About this skill
Incident response often suffers from fragmented data, making it difficult to reconstruct what actually happened and when. This skill takes raw event logs, impact data, and follow-up records to generate a factual, access-controlled timeline and resolution summary.
What it does
- Rebuilds timelines by processing incident events into a traceable, chronological sequence from multiple sources.
- Calculates metrics for detection, acknowledgement, restoration, and resolution times, comparing them against organizational SLA targets.
- Validates restoration by checking for verified evidence and matching fix events to change approvals.
- Quantifies impact by calculating user-minutes and service downtime across multiple impact windows.
- Tracks follow-ups by listing pending and overdue actions with assigned teams and due dates.
How it works
- Source Mapping: You provide raw incident data, and the agent maps each record to a specific source ID.
- Access Verification: The agent checks the requester's access scope for services and classification levels before processing.
- Deterministic Processing: A Python script handles all sorting, duration math, and gap analysis to prevent hallucinated metrics.
- Summary Generation: The agent produces a structured Markdown summary including durations, impact tables, and draft actions.
Frameworks & tools
This skill utilizes a Python-based execution environment to run scripts/run.py for all calculations. It follows a strict schema for JSON input/output and maps timestamps according to ISO 8601.
Why this beats prompting it yourself
Standard LLM prompts often hallucinate time calculations or struggle with complex timezone math across multiple log files. This skill uses a deterministic script for the math, ensuring durations and SLA margins are accurate while maintaining strict access control boundaries.
Use cases
- Reconstructing incident timelines from mixed ticket events and system logs.
- Performing a factual review of restoration evidence and change approvals.
- Identifying gaps in incident response timing compared to internal SLAs.
- Generating draft follow-up lists for service owner review.
Known limitations
Does not perform root-cause analysis or narrative post-mortem writing. Requires specific JSON-structured input for events and impact windows to function.
Requires pre-structured event data. Does not perform root-cause analysis. Calculations depend on a Python script; cannot estimate missing data by hand. Draft actions only.
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 any payment.
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 days ago