rabbitmq-expert

Configures AMQP topologies with DLX, quorum queues, and secure messaging.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Probably-Group/Dev-AID --skill rabbitmq-expert-probably-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rabbitmq-expert
Source: https://github.com/Probably-Group/Dev-AID/tree/main/.dev-aid/skills/expert/rabbitmq-expert
Command: npx skills add https://github.com/Probably-Group/Dev-AID --skill rabbitmq-expert-probably-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design and implement dependable RabbitMQ AMQP messaging so messages are routed correctly and failures don’t silently cause data loss or infinite retry loops.

Core Features & Use Cases

  • Message safety & reliability: enforces manual ack/nack, durable queues, persistent messages, publisher confirms, and prefetch/QoS to prevent overload.
  • Routing & topology guidance: covers exchange/queue architecture choices and queue bindings appropriate for pub/sub and task/work-queue patterns.
  • Failure handling & HA: defines dead letter exchange (DLX) patterns with TTL and limits, and recommends quorum queues for high availability and poison-message detection.
  • Use case: you are implementing an order event pipeline and need reliable publish/consume behavior with validation, retries, and DLQ routing when message payloads are invalid.

Quick Start

Tell the AI to propose a RabbitMQ exchange/queue topology (including DLX and quorum queues) for an orders pub/sub workflow and to generate Python (pika and/or aio-pika) publishing and consuming code that validates messages and uses manual acknowledgments.

Frequently Asked Questions about rabbitmq-expert

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

FAQPage Schema
How do I configure a dead letter exchange in RabbitMQ to handle failed messages?

To configure a dead letter exchange (DLX) in RabbitMQ, define a DLX with TTL and limits on your main queues. This routes failed or expired messages to a dedicated DLQ, preventing infinite retry loops and silent data loss during consumer failures.

What's the best way to prevent message loss in RabbitMQ with publisher confirms and manual ack?

Prevent message loss in RabbitMQ by enabling publisher confirms on the sender and using manual ack/nack on the consumer. Combine this with durable exchanges, persistent messages, and QoS prefetch limits to ensure reliable delivery and prevent overload.

When should I use quorum queues instead of classic queues for RabbitMQ high availability?

Use quorum queues for RabbitMQ high availability when you need data replication and poison-message detection across cluster nodes. Quorum queues provide fault tolerance and prevent data loss, making them the recommended choice over classic mirrored queues for resilient architectures.

How do I design an exchange and queue topology for a Rabbit pub/sub workflow?

Design a RabbitMQ pub/sub topology by selecting the appropriate exchange type and binding queues to match your event routing needs. For a task or work-queue pattern, ensure durable queues and persistent messages so published events reach all subscribed consumers reliably.

Does this RabbitMQ messaging guidance apply to Kafka or Redis pub-sub use cases?

No, this RabbitMQ messaging guidance explicitly avoids Kafka, Redis pub-sub, and NATS use-cases. It focuses strictly on AMQP topology design, dead letter handling, TLS-secured connections, and consumer retry behavior specific to the RabbitMQ broker.

Why do my RabbitMQ consumers get overwhelmed and how do I set prefetch QoS limits?

RabbitMQ consumers get overwhelmed when too many messages are dispatched simultaneously. Set QoS prefetch limits to control the number of unacknowledged messages delivered, preventing consumer overload and ensuring stable processing during traffic spikes.