event-driven

Orchestrate asynchronous messaging and event patterns for Kafka and RabbitMQ.

4|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/pluginagentmarketplace/custom-plugin-system-design --skill event-driven-pluginagentmarketplace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-driven
Source: https://github.com/pluginagentmarketplace/custom-plugin-system-design/tree/main/skills/event-driven
Command: npx skills add https://github.com/pluginagentmarketplace/custom-plugin-system-design --skill event-driven-pluginagentmarketplace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes assets (resource) and scripts (resource) and references (resource) components.

What problem does it solve?

Enables scalable, decoupled systems by standardizing asynchronous messaging and event patterns across distributed components.

Core Features & Use Cases

  • Supports Kafka, RabbitMQ, event sourcing, and CQRS with delivery guarantees.
  • Handles common patterns: pub/sub, work queues, event-driven workflows, and dead-letter handling.
  • Useful for building resilient microservices, real-time data pipelines, and audit-backed systems.

Quick Start

Invoke the event-driven skill to orchestrate asynchronous messaging across your Kafka or RabbitMQ brokers.

Frequently Asked Questions about event-driven

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

FAQPage Schema
How do I implement a saga pattern with dead-letter handling in Kafka?

This skill orchestrates Kafka saga patterns by configuring producers and consumers with retry logic, dead-letter handling, and structured schemas to ensure reliable asynchronous messaging and event-driven workflows.

What is the best way to configure RabbitMQ pub/sub with delivery guarantees?

The best way to configure RabbitMQ pub/sub with delivery guarantees is to orchestrate asynchronous messaging patterns using structured schemas, validation, and retry logic for scalable, decoupled distributed systems.

How does CQRS and event sourcing work for audit-backed microservices?

CQRS and event sourcing work for audit-backed microservices by standardizing asynchronous event patterns across distributed components, enabling decoupled data pipelines and reliable state tracking through structured schemas.

Can I use this event-driven skill for real-time data pipelines and work queues?

Yes, you can use this event-driven skill for real-time data pipelines and work queues. It supports Kafka and RabbitMQ configurations, applying delivery guarantees and observability across pub/sub and work queue patterns.

Why do I need dead-letter handling and retry logic for distributed systems?

You need dead-letter handling and retry logic for distributed systems to build resilient microservices. This skill standardizes these patterns to manage failed events and ensure delivery guarantees across asynchronous messaging components.