What problem does it solve? Setting up queue-consuming background workers on Render involves choosing the right service type, wiring a Redis-compatible broker correctly, and handling SIGTERM so in-flight jobs are not lost during deploys. This Skill provides the configuration patterns and shutdown guidance to do that reliably. ## Core Features & Use Cases - Worker Blueprint Configuration: Generate render.yaml services of type: worker wired to Render Key Value via fromService connection strings, with the correct noeviction maxmemory policy so queue keys are never dropped. - Framework Setup Guides: Minimal app and YAML examples for Celery (Python), Sidekiq (Ruby), BullMQ (Node.js), Asynq (Go), and Oban (Elixir, backed by PostgreSQL instead of Redis). - Graceful Shutdown Patterns: Per-language SIGTERM handlers and maxShutdownDelaySeconds tuning so workers stop dequeuing, finish in-flight jobs, and exit cleanly before SIGKILL. - Use Case: You need to move image-resizing jobs off your web service. Use this Skill to create a BullMQ worker service in render.yaml, connect it to a Key Value broker, and add a SIGTERM handler that drains active jobs within a 60-second shutdown window. ## Quick Start Ask the assistant to create a Render background worker in render.yaml that consumes jobs from a Key Value queue with graceful SIGTERM shutdown for your chosen framework.