Skip to content
Conduit

skill

background-job-patterns

14 language-agnostic patterns for background job / queue systems (Sidekiq, BullMQ, Asynq, JobRunr, Laravel Queue, and more) — a Claude Skill

gabrielras/background-job-patternscommunitylistedunreviewed
Use skill

Set up

Skills are installed by placing their folder where your agent loads skills.

Download ZIP from GitHub Open the repository

The download comes from github.com/gabrielras/background-job-patterns itself, not from our server, so what you get is exactly what its author published.

Install instructions come from the README

Skills do not use an MCP config. Follow the steps in the README below.

README

synced Oct 23, 2026

background-job-patterns

A Claude Skill covering the patterns that repeat across every background job / async queue system — Sidekiq, BullMQ, Asynq, River, Faktory, JobRunr, Quartz, Laravel Queue, Symfony Messenger — regardless of language or backend.

Every queue system solves the same problem: deliver work at least once to a worker that might crash, hang, or run twice. The pattern is the reusable unit, not any one library's implementation.

Installation

  1. npx skills (recommended): npx skills add gabrielras/background-job-patterns
  2. Manual: clone this repo and copy into ~/.claude/skills/background-job-patterns
  3. Local dev: claude --plugin-dir ./background-job-patterns

What's Inside

  • SKILL.md — overview, quick-reference table, symptom-based diagnosis flow
  • references/patterns.md — all 14 patterns in full: core principle, when to use, before/after pseudocode, common mistakes

14 Patterns

  1. At-Least-Once + Idempotency
  2. Visibility Timeout / Lease
  3. Dead Letter
  4. Exponential Backoff With Jitter
  5. Concurrency Bounded by the Weakest Downstream Resource
  6. Blast Radius of an Unhandled Failure Follows the Concurrency Unit
  7. Enqueue in the Same Transaction as the Data (Transactional Outbox)
  8. Ordering Is Not Guaranteed by Default
  9. Queue Depth Is the Primary Health Signal
  10. Reloading Code Requires an Explicit Signal
  11. Poison Message Containment
  12. Durable / Checkpointed Execution
  13. Competing Consumers
  14. Circuit Breaker

Sources

Stripe (idempotency keys) · AWS SQS docs (visibility timeout, dead-letter queues) · Marc Brooker / AWS Architecture Blog (backoff and jitter) · Mike Perham (Sidekiq, Faktory) · Brandur Leach (River) · Enterprise Integration Patterns (Hohpe & Woolf) · Michael Nygard, Release It!

Design Principle

The pattern is what transfers across stacks — not the implementation. This skill points at the relevant pattern for a given symptom; applying it still requires reading the actual code.

License

MIT — see LICENSE.

↑↓ navigate openesc close