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.
55
44%
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
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 'when' guidance. Its main weakness is the lack of specific concrete actions — it describes the domain well but doesn't enumerate what the skill actually helps you do (e.g., create workers, configure retries, set up scheduled jobs). The distinctiveness is excellent due to the specific technology focus.
Suggestions
Add specific concrete actions like 'create queues and workers, configure retry strategies, set up scheduled/recurring jobs, manage job priorities and rate limiting' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (BullMQ, Redis-backed job queues, background processing, async execution) and the technology stack (Node.js/TypeScript), but doesn't list specific concrete actions like 'create workers', 'configure retry policies', 'set up rate limiting', or 'manage job priorities'. | 2 / 3 |
Completeness | Clearly answers both 'what' (BullMQ expert for Redis-backed job queues, background processing, reliable async execution in Node.js/TypeScript) and 'when' with an explicit 'Use when:' clause listing trigger terms. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'bullmq', 'bull queue', 'redis queue', 'background job', 'job queue'. These cover the most common ways users would refer to this technology, including the alternate spelling 'bull queue'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — BullMQ is a specific library, and the combination of Redis, job queues, and Node.js/TypeScript creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
0%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 an empty outline with no actionable content. It consists of persona fluff, bare capability keywords, empty anti-pattern headers, and pattern descriptions that lack any code, commands, or concrete guidance. It fails on every dimension because it provides no executable instructions, no workflows, and no meaningful content for Claude to act on.
Suggestions
Add complete, executable code examples for each pattern (Basic Queue Setup, Delayed Jobs, Job Flows) with proper TypeScript/Node.js BullMQ code including connection configuration, worker setup, and error handling.
Fill in the anti-pattern sections with concrete examples of what NOT to do and what to do instead, including code showing the correct approach.
Add a clear workflow for setting up a production BullMQ system with validation steps (e.g., verify Redis connection, test job processing, confirm error handling works).
Remove the persona-building paragraphs and replace with a concise quick-start section containing copy-paste-ready code for the most common use case.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with persona-building fluff ('You've debugged stuck jobs at 3am', 'processed billions of jobs') that wastes tokens explaining things Claude doesn't need. The capability list is just keywords with no actionable content. Anti-patterns are listed as headers with no content beneath them. | 1 / 3 |
Actionability | There is zero executable code, no concrete commands, no specific examples, and no actual instructions. Every section is either a vague label or an empty header. The patterns section describes what should exist but provides nothing actionable. | 1 / 3 |
Workflow Clarity | There are no steps, no sequences, no validation checkpoints, and no workflows of any kind. The 'Job Flows and Dependencies' section is just a title with a one-line description and no actual workflow guidance. | 1 / 3 |
Progressive Disclosure | The content is a skeleton of headers with no substance and no references to external files for detailed content. There's no navigation structure, no links to deeper documentation, and the sections that exist are empty or near-empty. | 1 / 3 |
Total | 4 / 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
d739c8b
- 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.