spotiarr-bullmq

Manage BullMQ queues and workers for SpotiArr background jobs.

41|6|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/mralexsaavedra/spotiarr --skill spotiarr-bullmq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spotiarr-bullmq
Source: https://github.com/mralexsaavedra/spotiarr/tree/main/skills/spotiarr-bullmq
Command: npx skills add https://github.com/mralexsaavedra/spotiarr --skill spotiarr-bullmq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents brittle background job handling by defining reliable BullMQ queue names, worker entry expectations, and scheduling/job configuration patterns for SpotiArr’s asynchronous processing.

Core Features & Use Cases

  • Real queue orchestration: Uses a single source of truth for queue singletons and consistent real queue names for track downloading, searching, and sync workflows.
  • Production worker contracts: Enforces worker placement and validates job.data at the worker entry via parsing.
  • Deterministic job behavior: Applies job-type-specific retry/backoff decisions, job ID dedup patterns, and event handling requirements to keep UI/SSE and entity status aligned.

Quick Start

Configure the queues singleton initialization, register workers using the specified factories under infrastructure/workers, and enqueue jobs from the application layer using the defined queue names and job ID rules.

Frequently Asked Questions about spotiarr-bullmq

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I wire BullMQ queues and workers for background downloads without overlapping execution?

Wire BullMQ queues by initializing a queue singleton for consistent naming, register workers using a factory pattern, and enqueue jobs from the application layer with deduplication-based job IDs to prevent overlapping execution.

How do I validate BullMQ job.data at the worker entry before processing queue jobs?

Validate BullMQ job.data at the worker entry by applying Zod parsing to unvalidated payloads before execution, ensuring strict worker placement and safe async processing of queued tasks.

What is the best way to configure BullMQ job retry attempts and backoff strategies?

Configure BullMQ job retry attempts and backoff strategies by applying job-type-specific configuration rules during the enqueue process, ensuring deterministic behavior for failed background tasks.

How do I trigger BullMQ worker processing from cron-driven scheduled jobs?

Trigger BullMQ worker processing from cron-driven scheduled jobs by enqueuing tasks into the defined queue names from the application layer, allowing the singleton queue to dispatch jobs to registered workers.

Why do my BullMQ background tasks have brittle job handling and misaligned entity status?

Brittle job handling and misaligned entity status occur without deterministic job behavior, which requires applying event handling requirements and job ID dedup patterns to keep UI/SSE and entity status aligned.

Can I use a single queue singleton for multiple BullMQ track downloading, searching, and sync workflows?

Yes, you can use a single queue singleton initialization as a single source of truth for consistent real queue names across track downloading, searching, and sync workflows in BullMQ.