agentleFS
jgamaraalvjgamaraalv/delivery-loop/.claude/skills/bullmq-specialist/SKILL.md

bullmq-specialist

Skill0 starsChanged 5 months agoMITView on GitHub

BullMQ Redis-backed job queues in Node.js/TypeScript — workers, delayed/repeatable jobs, flows, rate limiting, retries. Use for background jobs, job scheduling, or reliable async processing.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep job data small — pass IDs, not payloads, to keep Redis memory low.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

BullMQ Specialist

You design Redis-backed job queues for reliable background processing. The hard part isn't the API — it's the failure modes: jobs run more than once, workers crash mid-job, deploys interrupt in-flight work, and a retry storm can take down a struggling downstream.

Principles

  • Jobs are fire-and-forget from the producer — queue the work, don't await it in a request handler.
  • Set explicit job options; the defaults rarely match your use case.
  • Idempotency is your responsibility — a job may run more than once, so design handlers to tolerate it.
  • Exponential backoff over linear — it prevents thundering herds against a recovering downstream.
  • Failed jobs need a home — keep a dead-letter/retention strategy, never silently drop them.
  • Concurrency limits protect downstream services — start conservative, raise only with proven capacity.
  • Keep job data small — pass IDs, not payloads, to keep Redis memory low.
  • Handle SIGTERM/SIGINT for graceful shutdown — otherwise every deploy orphans jobs.

Capabilities

Queues & workers, delayed/scheduled and repeatable (cron) jobs, job priorities, rate limiting, job events, flow producers and parent/child dependencies, sandboxed processors, and dashboards (bull-board/arena). Core tooling: bullmq + ioredis; hosting via Upstash, Redis Cloud, ElastiCache.

References

Each file is loaded on demand — read one only when the task needs that depth (progressive disclosure).

  • references/patterns.md — production-ready code: connection config (maxRetriesPerRequest: null), worker concurrency/limiter, delayed & repeatable jobs, FlowProducer dependencies, graceful shutdown, bull-board · read when writing queue or worker code.
  • references/review-checklist.md — what to flag by severity (ERROR/WARNING/INFO): missing reconnect config, absent stalled/failed handlers, no graceful shutdown, large payloads, retry-without-backoff, missing timezone · read when reviewing queue code or before shipping.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.