bullmq-specialist
BullMQ 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.
59
Quality
56%
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 ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/bullmq-specialist/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and clear 'Use when' guidance. The main weakness is the lack of specific concrete actions - it describes the domain well but doesn't enumerate what specific tasks the skill can help with (e.g., creating workers, scheduling jobs, handling failures).
Suggestions
Add specific concrete actions like 'create workers, schedule delayed jobs, handle retries, monitor queue metrics' to improve specificity
Consider adding more trigger variations like 'worker', 'delayed job', 'retry logic', 'queue processing' to the Use when clause
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (BullMQ, Redis-backed job queues) and general actions (background processing, async execution), but doesn't list specific concrete 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 trigger terms). | 3 / 3 |
Trigger Term Quality | Includes good natural keywords users would say: 'bullmq', 'bull queue', 'redis queue', 'background job', 'job queue'. These cover common variations and terms users naturally use when seeking help with this technology. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting BullMQ specifically with distinct triggers like 'bullmq', 'bull queue', 'redis queue'. Unlikely to conflict with general Node.js or Redis skills due to the specific queue/job terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a skeleton or outline with no actual instructional content. While it demonstrates awareness of BullMQ concepts (delayed jobs, flows, anti-patterns), every section that should contain actionable guidance is empty. The persona narrative wastes tokens that could be used for actual code examples and implementation details.
Suggestions
Add executable code examples for each pattern section (Basic Queue Setup, Delayed Jobs, Job Flows) with copy-paste ready TypeScript/Node.js snippets
Flesh out the anti-patterns with concrete 'instead do this' code showing the correct approach
Include a quick-start section with minimal working queue + worker setup that Claude can immediately use
Add validation/debugging guidance for common issues like stuck jobs, Redis connection problems, and job retry strategies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes unnecessary narrative framing ('You've debugged stuck jobs at 3am') that doesn't add actionable value. The capabilities list is lean but the persona description is padding. | 2 / 3 |
Actionability | The skill provides zero executable code, commands, or concrete examples. Section headers like 'Basic Queue Setup' and 'Delayed and Scheduled Jobs' are empty placeholders with no actual implementation guidance. | 1 / 3 |
Workflow Clarity | Despite mentioning 'Job Flows and Dependencies' and 'complex multi-step job processing', there are no actual steps, sequences, or validation checkpoints provided. The content is entirely descriptive headers without substance. | 1 / 3 |
Progressive Disclosure | The structure with sections for Patterns, Anti-Patterns, and Related Skills shows reasonable organization intent, but the sections are empty shells. References to related skills are present but the core content that should be disclosed is missing entirely. | 2 / 3 |
Total | 6 / 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
- duclm1x1/Dive-Ai
- Commit
20ba150
- 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.