القائمة
BullMQ expert for Redis-backed job queues, background processing,
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/BEKO2210/Firstbrain --skill bullmq-specialistيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | bullmq-specialist |
| description | BullMQ expert for Redis-backed job queues, background processing, |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | life-learning |
| category | career |
| risk | none |
| source | vibeship-spawner-skills (Apache 2.0) |
| tags | ["skill","life-learning","career","bullmq","specialist"] |
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications.
Production-ready BullMQ queue with proper configuration
When to use: Starting any new queue implementation
import { Queue, Worker, QueueEvents } from 'bullmq'; import IORedis from 'ioredis';
// Shared connection for all queues const connection = new IORedis(process.env.REDIS_URL, { maxRetriesPerRequest: null, // Required for BullMQ enableReadyCheck: false, });
// Create queue with sensible defaults const emailQueue = new Queue('emails', { connection, defaultJobOptions: { attempts: 3, backoff: { type: 'exponential', delay: 1000, }, removeOnComplete: { count: 1000 }, removeOnFail: { count: 5000 }, }, });
// Worker with concurrency limit const worker = new Worker('emails', async (job) => { await sendEmail(job.data); }, { connection, concurrency: 5, limiter: { max: 100, duration: 60000, // 100 jobs per minute }, });
// Handle events
worker.on('failed', (job, err) => {
console.error(Job ${job?.id} failed:, err);
});
Jobs that run at specific times or after delays
When to use: Scheduling future tasks, reminders, or timed actions
// Delayed job - runs once after delay await queue.add('reminder', { userId: 123 }, { delay: 24 * 60 * 60 * 1000, // 24 hours });
// Repeatable job - runs on schedule await queue.add('daily-digest', { type: 'summary' }, { repeat: { pattern: '0 9 * * *', // Every day at 9am tz: 'America/New_York', }, });
// Remove repeatable job await queue.removeRepeatable('daily-digest', { pattern: '0 9 * * *', tz: 'America/New_York', });
Complex multi-step job processing with parent-child relationships
When to use: Jobs depend on other jobs completing first
import { FlowProducer } from 'bullmq';
const flowProducer = new FlowProducer({ connection });
// Parent waits for all children to complete await flowProducer.add({ name: 'process-order', queueName: 'orders', data: { orderId: 123 }, children: [ { name: 'validate-inventory', queueName: 'inventory', data: { orderId: 123 }, }, { name: 'charge-payment', queueName: 'payments', data: { orderId: 123 }, }, { name: 'notify-warehouse', queueName: 'notifications', data: { orderId: 123 }, }, ], });
Properly close workers without losing jobs
When to use: Deploying or restarting workers
const shutdown = async () => { console.log('Shutting down gracefully...');
// Stop accepting new jobs await worker.pause();
// Wait for current jobs to finish (with timeout) await worker.close();
// Close queue connection await queue.close();
process.exit(0); };
process.on('SIGTERM', shutdown); process.on('SIGINT', shutdown);
Visual monitoring for BullMQ queues
When to use: Need visibility into queue status and job states
import { createBullBoard } from '@bull-board/api'; import { BullMQAdapter } from '@bull-board/api/bullMQAdapter'; import { ExpressAdapter } from '@bull-board/express';
const serverAdapter = new ExpressAdapter(); serverAdapter.setBasePath('/admin/queues');
createBullBoard({ queues: [ new BullMQAdapter(emailQueue), new BullMQAdapter(orderQueue), ], serverAdapter, });
app.use('/admin/queues', serverAdapter.getRouter());
Severity: ERROR
BullMQ requires maxRetriesPerRequest null for proper reconnection handling
Message: BullMQ queue/worker created without maxRetriesPerRequest: null on Redis connection. This will cause workers to stop on Redis connection issues.
Severity: WARNING
Workers should handle stalled events to detect crashed workers
Message: Worker created without 'stalled' event handler. Stalled jobs indicate worker crashes and should be monitored.
Severity: WARNING
Workers should handle failed events for monitoring and alerting
Message: Worker created without 'failed' event handler. Failed jobs should be logged and monitored.
Severity: WARNING
Workers should gracefully shut down on SIGTERM/SIGINT
Message: Worker file without graceful shutdown handling. Jobs may be orphaned on deployment.
Severity: INFO
Queue additions should be fire-and-forget in request handlers
Message: Queue.add awaited in request handler. Consider fire-and-forget for faster response.
Severity: WARNING
Job data should be small - pass IDs not full objects
Message: Job appears to have large inline data. Pass IDs instead of full objects to keep Redis memory low.
Severity: INFO
Jobs should have timeouts to prevent infinite execution
Message: Job added without explicit timeout. Consider adding timeout to prevent stuck jobs.
Severity: WARNING
Retries should use exponential backoff to avoid thundering herd
Message: Job has retry attempts but no backoff strategy. Use exponential backoff to prevent thundering herd.
Severity: WARNING
Repeatable jobs should specify timezone to avoid DST issues
Message: Repeatable job without explicit timezone. Will use server local time which can drift with DST.
Severity: INFO
High concurrency can overwhelm downstream services
Message: Worker concurrency is high. Ensure downstream services can handle this load (DB connections, API rate limits).
Skills: bullmq-specialist, email-systems, redis-specialist
Workflow:
1. Email request received (API)
2. Job queued with rate limiting (bullmq-specialist)
3. Worker processes with backoff (bullmq-specialist)
4. Email sent via provider (email-systems)
5. Status tracked in Redis (redis-specialist)
Skills: bullmq-specialist, backend, devops
Workflow:
1. API receives request (backend)
2. Long task queued for background (bullmq-specialist)
3. Worker processes async (bullmq-specialist)
4. Result stored/notified (backend)
5. Workers scaled per load (devops)
Skills: bullmq-specialist, ai-workflow-automation, performance-hunter
Workflow:
1. AI task submitted (ai-workflow-automation)
2. Job flow created with dependencies (bullmq-specialist)
3. Workers process stages (bullmq-specialist)
4. Performance monitored (performance-hunter)
5. Results aggregated (ai-workflow-automation)
Skills: bullmq-specialist, backend, redis-specialist
Workflow:
1. Repeatable jobs defined (bullmq-specialist)
2. Cron patterns with timezone (bullmq-specialist)
3. Jobs execute on schedule (bullmq-specialist)
4. State managed in Redis (redis-specialist)
5. Results handled (backend)
Works well with: redis-specialist, backend, nextjs-app-router, email-systems, ai-workflow-automation, performance-hunter