message-queues
RabbitMQ, Kafka, SQS, pub/sub, competing consumers, dead letter queues, and event streaming
Profile →npx skills add cosmicstack-labs/mercury-agent-skills --skill message-queues --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Message Queues Design reliable message-driven systems. ## Queue Types | Queue | Persistence | Ordering | Use Case | |-------|------------|----------|----------| | RabbitMQ | Optional | Per queue | Task distribution, RPC | | Apache Kafka | Durable (disk) | Per partition | Event streaming, logs | | AWS SQS | Durable | Best effort (std) / Strict (FIFO) | Serverless decoupling | | Redis Pub/Sub | None | Per channel | Real-time notifications | ## RabbitMQ Patterns ### Work Queues (Competing Consumers) ``` Producer → Queue → Consumer 1 → Consumer 2 → Consumer 3 ``` - Messages distributed round-robin - Ack on success, nack on failure (requeue or DLQ) - Prefetch count controls concurrency ### Pub/Sub (Exchange → Binding → Queue) - Fanout: broadcast to all queues - Direct: route by routing key - Topic: route by pattern (user.*, user.created) - Headers: route by header values ## Kafka Patterns ### Topics & Partitions - Messages within a partition are ordered - Partitions enable parallelism - Consumer group = one instance per partition ### Producer ```javascript await producer.send({ topic: 'order-events', messages: [{ key: orderId, value: JSON.stringify(order) }], }); ``` ### Consumer ```j
- Queue Types
- RabbitMQ Patterns
- Work Queues (Competing Consumers)
- Pub/Sub (Exchange → Binding → Queue)
- Kafka Patterns
- Topics & Partitions
- Producer
- Consumer
- Dead Letter Queues
- Best Practices
What does the message-queues skill do?
RabbitMQ, Kafka, SQS, pub/sub, competing consumers, dead letter queues, and event streaming
How do I install it?
Run `npx skills add cosmicstack-labs/mercury-agent-skills --skill message-queues --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From cosmicstack-labs/mercury-agent-skills, a repository with 364 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.