bullmq-specialist
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications.
55
45%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/bullmq-specialist/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies the technology domain (BullMQ/Redis) clearly but reads more like a tagline than a functional skill description. It lacks specific concrete actions the skill can perform and entirely omits trigger guidance ('Use when...'), making it difficult for Claude to reliably select this skill at the right time.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about job queues, BullMQ setup, Redis-backed workers, task scheduling, or retry logic in Node.js/TypeScript.'
List specific concrete actions such as 'Create and configure queues, define workers, set up retry policies, implement rate limiting, manage job priorities, and handle delayed/scheduled jobs.'
Include additional natural trigger terms users might say, such as 'worker', 'queue', 'cron', 'scheduled task', 'delayed job', 'retry', and 'message queue'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (BullMQ, Redis-backed job queues) and some general actions (background processing, async execution), but doesn't list specific concrete actions like 'create workers', 'configure retry policies', 'set up rate limiting', or 'manage job priorities'. | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also vague, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes good keywords like 'BullMQ', 'Redis', 'job queues', 'background processing', 'Node.js', 'TypeScript', but misses common user terms like 'worker', 'queue', 'retry', 'cron job', 'scheduled task', 'delayed job', or 'message queue'. | 2 / 3 |
Distinctiveness Conflict Risk | BullMQ is a specific library which helps distinguish it, but 'background processing' and 'async execution' are generic enough to potentially overlap with other task/queue processing skills or general Node.js skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with production-ready, executable code examples covering key BullMQ patterns. However, it suffers from being a monolithic document with significant verbosity in non-code sections (validation checks, collaboration workflows, capabilities lists) that inflate token cost without proportional value. The workflow clarity is adequate but lacks explicit validation checkpoints within the code patterns themselves.
Suggestions
Extract the Validation Checks, Collaboration workflows, and detailed patterns into separate referenced files (e.g., VALIDATION.md, PATTERNS.md) to reduce the main skill's token footprint and improve progressive disclosure.
Remove or drastically condense the Capabilities, Scope, When to Use, and Limitations sections—these are metadata-like lists that consume tokens without teaching Claude how to do anything.
Add explicit validation steps within the code patterns, such as verifying Redis connectivity before queue creation and confirming job addition success in the basic setup pattern.
Condense the Validation Checks into a compact table or checklist format rather than repeating Severity/Message blocks for each item.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful content but is verbose in several areas. The 'Principles' section restates things Claude already knows (e.g., 'Idempotency is your responsibility'), the 'Capabilities' and 'Scope' sections are list-only with no actionable value, the 'Validation Checks' section is extremely verbose with repetitive severity/message formatting, and the 'Collaboration' and 'When to Use' sections add significant token cost with limited instructional value. | 2 / 3 |
Actionability | The code examples are concrete, executable, and copy-paste ready. The patterns section covers queue setup, delayed jobs, flows, graceful shutdown, and dashboard integration with complete, runnable TypeScript/JavaScript code including imports and configuration. | 3 / 3 |
Workflow Clarity | The collaboration workflows provide clear sequences, and the graceful shutdown pattern shows a proper step-by-step process. However, there are no explicit validation checkpoints in the main patterns (e.g., no 'verify Redis connection before proceeding' or 'check job was added successfully'). The validation checks section lists things to watch for but doesn't integrate them into the workflow steps. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of text with no references to external files despite being over 250 lines. The validation checks, collaboration workflows, and detailed patterns could all be split into separate files. There are no bundle files and no references to any supporting documents, making this a single large document that could benefit significantly from progressive disclosure. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
e40fdb8
- 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.