Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dokhacgiakhoa/bullmq-specialist
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications.
Passed 21 of 22 test cases with the skill, and 19 of 22 without it.
3 fixed18 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have VIP customer jobs and free tier customer jobs. I plan to create two distinct Redis queues ('vip-queue' and 'free-queue') and run a custom loop that manually pops from 'vip-queue' first before checking 'free-queue'. Is this the standard approach?
| Checked | Without skill | With skill |
|---|---|---|
| Recommend using job priority attributes within a single queue rather than manually polling multiple queues. | Missed | Passed |
The instructions your model reads when the skill loads.
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:
test cases passed, vs 19 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.