event-driven-patterns
Message queue patterns with BullMQ, Kafka, RabbitMQ - saga, outbox, dead letter queue, exactly-once semantics.
Profile →npx skills add vibeeval/vibecosystem --skill event-driven-patterns --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.
# Event-Driven Patterns Message queue and event bus patterns for decoupled, reliable async processing. ## BullMQ Setup (Producer + Consumer) ```typescript import { Queue, Worker, QueueEvents } from 'bullmq' import Redis from 'ioredis' const connection = new Redis(process.env.REDIS_URL!, { maxRetriesPerRequest: null }) // Producer: define queue const emailQueue = new Queue('email', { connection }) const marketQueue = new Queue('market-resolution', { connection }) // Add job with options await emailQueue.add( 'send-welcome', { userId: 'abc', email: 'user@example.com' }, { attempts: 3, backoff: { type: 'exponential', delay: 1000 }, removeOnComplete: { count: 1000 }, removeOnFail: { count: 5000 } } ) // Delayed job (send after 1 hour) await emailQueue.add('send-reminder', { userId: 'abc' }, { delay: 3_600_000 }) // Consumer: named processor const emailWorker = new Worker( 'email', async (job) => { if (job.name === 'send-welcome') { await sendWelcomeEmail(job.data.email) } else if (job.name === 'send-reminder') { await sendReminderEmail(job.data.userId) } // Return value stored in job.returnvalue return { sent: true, at: new Date().toISOString() } }, { connection, concurrency: 10 } ) em
- BullMQ Setup (Producer + Consumer)
- Retry Policies and Dead Letter Queue
- Transactional Outbox Pattern
- Saga Pattern (Orchestration)
- Idempotent Consumers (Exactly-Once Semantics)
- Fan-Out Pattern
- Priority Queue
- Queue Monitoring
What does the event-driven-patterns skill do?
Message queue patterns with BullMQ, Kafka, RabbitMQ - saga, outbox, dead letter queue, exactly-once semantics.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill event-driven-patterns --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 vibeeval/vibecosystem, a repository with 521 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.