bullmq-specialist
tessl i github:sickn33/antigravity-awesome-skills --skill bullmq-specialistBullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.
Validation
63%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed | |
Implementation
22%This skill is essentially a skeleton or outline with no substantive content. It has good structural intent with clear section headers for patterns and anti-patterns, but every section that should contain actionable guidance is empty or contains only a one-line description. The persona introduction wastes tokens on narrative that doesn't help Claude perform BullMQ tasks.
Suggestions
Add executable code examples for each pattern (Basic Queue Setup, Delayed Jobs, Job Flows) showing actual BullMQ implementation with proper TypeScript/Node.js syntax
Fill in the Anti-Patterns section with concrete 'instead of X, do Y' guidance including code showing both the wrong and right approaches
Remove or drastically shorten the persona paragraph - replace with a brief statement of when to use BullMQ and key constraints
Add a workflow for common operations like 'setting up a new queue' or 'debugging stuck jobs' with explicit validation steps (e.g., checking Redis connection, verifying job state)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The persona introduction is verbose and unnecessary - Claude doesn't need to be told it has 'debugged stuck jobs at 3am'. The capabilities list is lean, but the overall content has padding that doesn't add actionable value. | 2 / 3 |
Actionability | Despite listing patterns like 'Basic Queue Setup' and 'Job Flows and Dependencies', there is zero executable code, no concrete examples, and no actual implementation guidance. The content describes what topics exist but provides no instructions on how to do anything. | 1 / 3 |
Workflow Clarity | No workflows are defined. Pattern sections are empty headers with no steps, sequences, or validation checkpoints. 'Job Flows and Dependencies' mentions multi-step processing but provides no actual workflow guidance. | 1 / 3 |
Progressive Disclosure | The structure with sections for Capabilities, Patterns, and Anti-Patterns shows reasonable organization intent, but the sections are empty shells. Related Skills references are appropriate, but there are no links to detailed documentation or examples. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
90%This is a solid skill description with excellent trigger terms and clear 'Use when' guidance. The main weakness is the somewhat abstract capability description - it mentions 'background processing' and 'async execution' but doesn't enumerate specific concrete actions the skill enables. The description successfully carves out a distinct niche for BullMQ-related tasks.
Suggestions
Expand the capabilities section with specific concrete actions like 'create workers, define job processors, configure retries, schedule delayed jobs, monitor queue metrics'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (BullMQ, Redis-backed job queues) and mentions some actions (background processing, async execution), but doesn't list multiple concrete specific actions like 'create workers', 'schedule jobs', 'handle retries', or 'monitor queue health'. | 2 / 3 |
Completeness | Clearly answers both what (BullMQ expert for Redis-backed job queues, background processing, async execution in Node.js/TypeScript) and when (explicit 'Use when:' clause with specific trigger terms). | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural terms users would say: 'bullmq', 'bull queue', 'redis queue', 'background job', 'job queue'. These are terms users would naturally use when seeking help with this technology. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting BullMQ specifically with distinct triggers like 'bullmq', 'bull queue', 'redis queue'. Unlikely to conflict with general Redis skills or other queue systems due to specific terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.