swarm-event-bus-agent

Audit gnubok's event bus for initialization coverage and emission reliability.

209|46|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/erp-mafia/gnubok --skill swarm-event-bus-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-event-bus-agent
Source: https://github.com/erp-mafia/gnubok/tree/main/.claude/skills/swarm-event-bus-agent
Command: npx skills add https://github.com/erp-mafia/gnubok --skill swarm-event-bus-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only auditing of gnubok's event bus to identify gaps, coverage holes, and potential reliability issues without modifying code or data.

Core Features & Use Cases

  • Audits event bus wiring, initialization, and handler registrations to ensure proper startup sequencing.
  • Verifies Promise.allSettled isolation and avoids cascading failures in event emission.
  • Checks event_log TTL, cron cleanup, and extension boundaries for observability.

Quick Start

Review gnubok's event bus integration and verify all routes initialize handlers before emitting events.

Frequently Asked Questions about swarm-event-bus-agent

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

FAQPage Schema
How do I audit an event bus in Node.js without modifying application code?

You can audit an event bus read-only by analyzing initialization sequencing and emission sites without touching code or data. This verifies ensureInitialized coverage and correct event publishing across the architecture.

How does Promise.allSettled isolation prevent cascading failures in event-driven architecture?

Promise.allSettled isolation prevents cascading failures by ensuring individual handler rejections do not crash the entire event emission chain. Auditing verifies emission points correctly implement this pattern to maintain reliability during partial failures.

What is ensureInitialized coverage and why does it matter for TypeScript event buses?

EnsureInitialized coverage verifies all routes register event handlers before emitting events, preventing silent drops. Auditing checks bus/types.ts and lib/init.ts to confirm proper startup sequencing across the event-driven architecture.

Does this event bus audit work with TypeScript extensions and cron cleanup boundaries?

Yes, the audit checks event_log TTL, cron cleanup, and extension boundaries for observability. It analyzes the event bus, engine events, and API emission points to verify extension limits and cleanup schedules without modifying the codebase.

What are common event bus reliability gaps in Node.js observability setups?

Common reliability gaps include missing ensureInitialized coverage, improper Promise.allSettled isolation causing cascading failures, and unbounded event_log growth. Auditing identifies these holes by checking handler registrations, emission sites, and TTL cleanup schedules.