sse-event-debug

Debug SSE event divergence by inspecting broadcaster stats, event logs, and reservation transitions.

1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/mattbutlerengineering/mattbutlerengineering --skill sse-event-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sse-event-debug
Source: https://github.com/mattbutlerengineering/mattbutlerengineering/tree/main/services/reservations/.claude/skills/sse-event-debug
Command: npx skills add https://github.com/mattbutlerengineering/mattbutlerengineering --skill sse-event-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you debug why reservation Server-Sent Events (SSE) appear to diverge between the broadcaster and subscribers, including missing events, stuck state transitions, and unexpected connection drops.

Core Features & Use Cases

  • SSE broadcaster validation: Inspect active SSE connections and broadcaster stats to confirm the stream is live and producing events.
  • Event publication verification: Query the reservation event log in the database to confirm the event was actually created and persisted.
  • Reservation state machine inspection: Verify reservation status and timestamps to detect stalled or incorrect transitions that explain downstream subscriber behavior.

Use case example: A venue dashboard shows a reservation status that doesn't match the backend while the SSE stream seems connected—use this Skill to confirm publication in the DB, validate SSE connection state, then check the reservation state machine transitions.

Quick Start

Use the sse-event-debug Skill to triage SSE event divergence for the reservations service for a specific venueId by checking broadcaster connections, validating event publication in the database, and inspecting the reservation’s current status and last update time.

Frequently Asked Questions about sse-event-debug

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

FAQPage Schema
Why do SSE events go missing between the broadcaster and subscribers in a reservations service?

SSE events go missing when broadcaster connections drop, event publication fails to persist in the database, or reservation state machine transitions stall. Inspecting broadcaster stats, querying the reservation event log, and verifying state transitions identifies the root cause of the SSE event divergence.

How do I debug a stuck reservation state machine transition during real-time streaming?

To debug a stuck reservation state machine transition, verify the reservation status and timestamps in the database to detect stalled or incorrect transitions. Then inspect the SSE broadcaster connections to ensure real-time streaming is live and producing events for the given venueId and reservationId.

How do I verify if a reservation event was actually published to the SSE stream?

Verify reservation event publication by querying the reservation event log in the database to confirm the event was created and persisted. Then validate active SSE broadcaster connections and inspect broadcaster stats to ensure the event is actively streaming to subscribers.

What's the best way to triage unexpected SSE connection drops during reservation event streaming?

Triage unexpected SSE connection drops by inspecting active SSE broadcaster stats to confirm stream liveness, validating event publication in the reservation database tables, and reasoning through reservation state machine transitions to find the mismatch root cause for the specific venueId.

Can I use this approach to debug SSE divergence for a specific venueId and reservationId?

Yes, you can debug SSE divergence for a specific venueId and reservationId by validating broadcaster connections, querying database reservation event and reservation tables, and inspecting state machine transitions to pinpoint why subscriber behavior diverges from the backend.

What should I check when a venue dashboard reservation status doesn't match the backend despite an active SSE stream?

When a venue dashboard reservation status mismatches the backend, check event publication in the database reservation event log, validate SSE connection state via broadcaster stats, and inspect the reservation state machine transitions for stalled or incorrect status updates.