Skills bullmq-specialist
📦

bullmq-specialist

Content revision r1 Safe ⚙️ External commands

Build Reliable BullMQ Queues

Teams can struggle with stuck jobs, retries, schedules, and Redis-backed worker behavior. This skill helps Claude, Codex, and Claude Code design and review BullMQ queue systems.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "bullmq-specialist" from https://skillstore.io/skills/sickn33-bullmq-specialist.md and its manifest at https://skillstore.io/api/skills/sickn33-bullmq-specialist/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-bullmq-specialist.md Signed manifest GET /api/skills/sickn33-bullmq-specialist/manifest Signed lockfile GET /api/skills/sickn33-bullmq-specialist/lockfile

Test it

Using "bullmq-specialist". I need to process uploaded videos after users submit them.

Expected outcome:

Recommends separate queues for upload validation, transcoding, thumbnail creation, and notification. Defines retry rules, idempotency keys, and monitoring signals.

Using "bullmq-specialist". Our jobs are stuck and Redis CPU is high.

Expected outcome:

Lists likely causes such as excessive concurrency, large payloads, slow processors, and missing backoff. Suggests checking queue metrics and worker logs first.

Using "bullmq-specialist". We need daily digest emails with retries and rate limits.

Expected outcome:

Proposes repeatable scheduling, bounded concurrency, per-provider rate limits, dead letter handling, and clear event logging for failed deliveries.

Security Audit

Safe
v4 • 7/6/2026 Open versioned report

The only static finding is a false positive caused by Markdown inline code formatting in SKILL.md. No prompt injection, credential access, network behavior, executable code, or malicious intent was found in the reviewed skill text.

1
Files scanned
58
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
SKILL.md:57
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-bullmq-specialist/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-bullmq-specialist/security.svg)](https://skillstore.io/skills/sickn33-bullmq-specialist?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-bullmq-specialist?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-bullmq-specialist/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-bullmq-specialist.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). bullmq-specialist security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-bullmq-specialist/audits/4

BibTeX citation

@techreport{sickn33-sickn33-bullmq-specialist-2026, author = {sickn33}, title = {bullmq-specialist security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/sickn33-bullmq-specialist/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "bullmq-specialist security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-06" url: "https://skillstore.io/skills/sickn33-bullmq-specialist/audits/4" identifiers: - type: other value: "skillstore:sickn33-bullmq-specialist:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Plan a New Queue System

Create a BullMQ design for asynchronous work, retries, delayed jobs, and worker boundaries before implementation.

Diagnose Production Job Failures

Review stuck jobs, retry behavior, Redis pressure, and worker settings to find likely causes and fixes.

Modernize Background Processing

Convert ad hoc cron tasks or inline work into structured BullMQ queues, schedules, and flows.

Try These Prompts

Create a Basic Queue 
Help me design a basic BullMQ queue for this Node.js task. Include the queue purpose, worker behavior, retry policy, and failure handling.
Review Worker Settings 
Review my BullMQ worker design for concurrency, rate limits, retries, and Redis impact. Point out risks and suggest practical improvements.
Design Scheduled Jobs 
Design a BullMQ approach for delayed and repeatable jobs in my application. Include scheduling strategy, idempotency rules, and observability needs.
Architect Job Flows 
Design a BullMQ FlowProducer architecture for this multi-step workflow. Include dependencies, failure behavior, compensation steps, and monitoring points.

Best Practices

  • Keep job payloads small and store large data in durable application storage.
  • Make processors idempotent so retries do not duplicate external side effects.
  • Set explicit concurrency, retry, backoff, and dead letter behavior for each queue.

Avoid

  • Do not use giant job payloads for files, records, or nested business data.
  • Do not rely on infinite concurrency to fix throughput problems.
  • Do not skip dead letter handling for important background work.

Frequently Asked Questions

What does this skill help with?
It helps design, review, and troubleshoot BullMQ queues, workers, schedules, retries, events, and job flows.
Can it generate BullMQ implementation code?
It can guide implementation patterns and suggest code structure when the user asks for code-oriented help.
Does it require Redis expertise?
Basic Redis context helps, but the skill explains Redis-related queue concerns in practical terms.
Can it debug live production queues?
It can reason from logs, metrics, configuration, and symptoms provided by the user. It cannot inspect systems directly.
Is it useful for scheduled jobs?
Yes. It covers delayed jobs, repeatable jobs, scheduling behavior, and operational safeguards.
Who should use this skill?
Backend engineers, platform teams, and technical leads who manage Redis-backed background processing can use it.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/bullmq-specialist

Ref

01171b582d636c013315c5e0d969c64f8d9cdff2

Maintenance freshness

7/18/2026

Usage

5 downloads · 102 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all