excalidash-event-driven-diagrammer

Generates and validates event-driven architecture diagrams with producers, brokers, consumers, and event stores.

2|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/gabedsam01/excalidash-v2 --skill excalidash-event-driven-diagrammer-gabedsam01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: excalidash-event-driven-diagrammer
Source: https://github.com/gabedsam01/excalidash-v2/tree/main/skills/excalidash/excalidash-event-driven-diagrammer
Command: npx skills add https://github.com/gabedsam01/excalidash-v2 --skill excalidash-event-driven-diagrammer-gabedsam01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Drawing event-driven architectures by hand often produces diagrams where async and sync edges are indistinguishable, producers bypass the message bus, and topics lack producers or consumers. This Skill generates and reviews pub-sub topology diagrams in Excalidraw with enforced layout, edge semantics, and architecture validation. ## Core Features & Use Cases - Topology Generation: Creates diagrams with producers on the left, a central event bus (Kafka, SNS/SQS, RabbitMQ, EventBridge) with named topics, consumers on the right, and an event store, using dashed arrows for async events and solid arrows for synchronous calls. - Repo Reverse-Engineering: Scans a codebase for publish/listener calls (e.g., kafkaTemplate.send, @KafkaListener) and classifies components into producers, consumers, and shared topics. - Quality Loop: Runs lint, score, repair, and architecture validation until the drawing scores at least 95 with zero hard blockers, flagging orphan topics, missing DLQs, and direct producer-to-consumer edges. - Use Case: Ask to diagram an order pipeline where OrderService publishes OrderPlaced to Kafka and ShippingService and EmailService subscribe, and receive a validated, exportable SVG with a sync/async legend. ## Quick Start Ask the assistant to draw your event-driven architecture showing which services publish to your Kafka topics and which services consume them, with async edges visually distinct from sync calls.

Frequently Asked Questions about excalidash-event-driven-diagrammer

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

FAQPage Schema
How do I draw an event-driven architecture diagram with Kafka producers and consumers?

Describe your producers, the Kafka topics, and the consumers, and the Skill generates a diagram with producers on the left, the broker in the center, and consumers on the right. Async event edges are dashed, sync calls are solid, and a legend keys both.

How to reverse-engineer a pub-sub diagram from a Spring Boot repository?

The Skill scans the repo for producer calls like kafkaTemplate.send and consumer annotations like @KafkaListener, then classifies components into producers, consumers, and shared topics via create_from_repo_analysis. The result is reshaped into the producers-bus-consumers topology.

Can it diagram SNS/SQS fan-out or EventBridge instead of Kafka?

Yes, the central bus can be Kafka, AWS SNS/SQS, EventBridge, RabbitMQ, NATS, or Pulsar, with named topics, streams, or queues shown on the bus. Fan-out from one event to many consumers is drawn explicitly.

When should I not use an event-driven diagram?

Do not use it for one ordered scenario with lifelines (use a sequence diagram), command/query model splits (use CQRS), mostly synchronous app topologies (use C4 Container), or ports-and-adapters designs (use Hexagonal). It is only for event flow topology.

Why does my fan-out diagram fail linting with arrow over text errors?

Fan-out produces many near-parallel dashed lines that can cross topic or event labels, triggering ARROW_TEXT_INTERSECTION blockers. The repair loop reroutes lines through 32px gutters beside the bus until the score reaches 95 with zero blockers.

Does the diagram expose broker credentials or API keys?

No, broker SASL credentials, AWS access keys, webhook secrets, and consumer-side API keys are redacted to typed placeholders before any tool call. The exported SVG, PNG, or JSON is re-scanned to confirm no secrets leaked.