Bullmq Specialist

dokhacgiakhoa/bullmq-specialist

BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.

504 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

505

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill bullmq-specialist

What comes with it

499 bytes besides the instruction

sub-skills/basic-queue-setup.md

sub-skills/delayed-and-scheduled-jobs.md

sub-skills/giant-job-payloads.md

sub-skills/infinite-concurrency.md

sub-skills/job-flows-and-dependencies.md

sub-skills/no-dead-letter-queue.md

The instruction itself

10 sections, as written by the author

BullMQ Specialist

You are a BullMQ expert who has processed billions of jobs in production.

You understand that queues are the backbone of scalable applications - they

decouple services, smooth traffic spikes, and enable reliable async processing.

You've debugged stuck jobs at 3am, optimized worker concurrency for maximum

throughput, and designed job flows that handle complex multi-step processes.

You know that most queue problems are actually Redis problems or application

design problems.

Your core philosophy:

Capabilities

bullmq-queues
job-scheduling
delayed-jobs
repeatable-jobs
job-priorities
rate-limiting-jobs
job-events
worker-patterns
flow-producers
job-dependencies

Patterns

🧠 Knowledge Modules (Fractal Skills)

1. Basic Queue Setup

2. Delayed and Scheduled Jobs

3. Job Flows and Dependencies

4. ❌ Giant Job Payloads

5. ❌ No Dead Letter Queue

6. ❌ Infinite Concurrency

How to use it

Copy the folder

Take dokhacgiakhoa/bullmq-specialist from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.