incident-analysis

Trace event chains to identify root causes of failed transfers and missing events.

2|Updated Jan 2, 2026

Search Tags:#debugging #logs #event-driven #root-cause #cloud-functions #incident-analysis

Ready to run

npx skills add https://github.com/abdullahbokl/Boklo-Wallet --skill incident-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-analysis
Source: https://github.com/abdullahbokl/Boklo-Wallet/tree/main/.agent/skills/incident-analysis
Command: npx skills add https://github.com/abdullahbokl/Boklo-Wallet --skill incident-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performs root-cause analysis of failed transfers, missing events, or notification issues using system-level reasoning.

Core Features & Use Cases

Trace the end-to-end event chain from transaction creation to completion to locate where a failure occurred.
Check data consistency by comparing Ledger sums to aggregated Balance and identify anomalies.
Hypothesize potential failure modes (e.g., delayed event delivery, reversible transactions) and verify against logs and system state.

Quick Start

Trace the incident from transaction creation through completion and identify the first failing link.

Frequently Asked Questions about incident-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find the root cause of failed transfers and missing events in an event-driven backend?▼

To find the root cause of failed transfers and missing events, trace the end-to-end event chain from transaction creation to completion to locate the first failing link. You can verify event delivery by checking transaction logs and reconciling the ledger state.

How do I trace delayed event delivery and notification failures across cloud functions?▼

Trace delayed event delivery by applying system-level reasoning to hypothesize potential failure modes and verify them against event tracing data. This process locates exactly where notification failures or transaction delays occur within the event-driven backend.

Why does my ledger state show balance misupdates after a transaction delay?▼

Balance misupdates often occur due to delayed event delivery or reversible transactions disrupting data consistency. Check data consistency by comparing Ledger sums to aggregated Balance to identify anomalies and verify the correct ledger state.

What data do I need to debug production incidents involving transaction delays?▼

Debugging production incidents requires access to transaction logs, event tracing data, and ledger state. These inputs are necessary to verify event delivery, reconcile state, and guide corrective actions for transaction delays.

Can I use this incident analysis approach for both development and production environments?▼

Yes, this incident analysis applies to both production and development incidents involving balance misupdates, transaction delays, or notification failures. It traces the event chain across the event-driven backend to pinpoint failures in any environment.