Publish and consume RabbitMQ messages with standardized schemas and naming conventions.
npx skills add https://github.com/duc01226/EasyPlatform --skill message-bus
Please help me install this Agent Skill. Skill: message-bus Source: https://github.com/duc01226/EasyPlatform/tree/main/.claude/skills/backend-message-bus Command: npx skills add https://github.com/duc01226/EasyPlatform --skill message-bus
This Skill guides implementing cross-service communication via message bus patterns (events, requests), including producers, consumers, and naming conventions.
Configure and implement a sample event pipeline by adding a producer and a consumer as described in the guide.
High-intent search queries and answers about installing and using this skill.
Cross-service messaging with RabbitMQ uses a message bus pattern where producers publish events and consumers subscribe to them. This Skill guides you through setting up producers and consumers, defining standardized message schemas, and implementing entity event patterns (CRUD operations) for reliable inter-service communication.
Event-driven synchronization publishes entity changes from one service and consumers in other services process those events to update their local state. This Skill covers message naming conventions, schema mapping, and event-driven workflows that keep services synchronized without direct coupling.
Yes. RabbitMQ message buses handle entity CRUD events (create, read, update, delete) across services through producer-consumer patterns. This Skill provides naming conventions and pre-flight checks to ensure reliable entity event publishing and consumption for data synchronization.
Configure a producer to publish messages to a message bus topic, then configure a consumer to listen and process those messages. This Skill includes a quick-start guide with practical examples showing how to implement both patterns with standardized schemas and naming conventions.
Standardized naming conventions ensure consistent, discoverable messaging across services. This Skill enforces naming patterns for producers and consumers, includes shared cross-service message definitions that map entity data to target schemas, and provides pre-flight validation.
Yes. This Skill enforces standardized schemas for all messages to ensure producers and consumers understand each other's data formats. Shared cross-service message definitions map entity data to target schemas with pre-flight checks before publishing.
erymuzuanPublish and subscribe to RabbitMQ entity change events with routing keys.
JeromyJSmithExtract structured BIM element data, quantities, and property sets from IFC files using IfcOpenShell.
curiositechDesigns Kafka-based ordering pipelines with transactional outbox, idempotent consumers, and DLQ policies for backend microservices architectures.
rnavarychImplement message queue systems with RabbitMQ, Kafka, Redis Streams, SQS, and Pub/Sub.
