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.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill bullmq-specialist64
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 somewhat abstract capability description - it mentions 'background processing' and 'async execution' but doesn't enumerate specific concrete actions the skill enables. The description successfully differentiates itself from other skills through technology-specific terminology.
Suggestions
Add specific concrete actions like 'create workers, schedule delayed jobs, handle retries, manage job priorities, monitor queue metrics' to improve specificity
| 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 with explicit 'Use when:' clause listing 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 | Very clear niche with distinct triggers specific to BullMQ and Redis queues. The combination of 'bullmq', 'bull queue', and 'redis queue' creates a unique fingerprint unlikely to conflict with other skills. | 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 substantive content. It declares expertise and lists capabilities/patterns but provides zero executable code, concrete examples, or actionable guidance. The persona narrative wastes tokens while the sections that should contain actual BullMQ implementation details are empty headers.
Suggestions
Add complete, executable code examples for each pattern (Basic Queue Setup, Delayed Jobs, Job Flows) with proper TypeScript/Node.js imports and configuration
Expand anti-patterns with concrete bad code examples and their corrected versions
Include specific Redis connection configuration, worker concurrency settings, and error handling patterns
Add validation/debugging steps for common issues like stuck jobs, Redis connection failures, and job retry strategies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary narrative ('processed billions of jobs', 'debugged stuck jobs at 3am') that doesn't add actionable value. The capabilities list is lean but the persona framing is verbose. | 2 / 3 |
Actionability | The skill provides zero executable code, commands, or concrete examples. Pattern sections like 'Basic Queue Setup' and 'Delayed and Scheduled Jobs' are empty headers with no implementation details. Anti-patterns are listed but not explained. | 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 declarative with no procedural guidance. | 1 / 3 |
Progressive Disclosure | The structure with sections (Capabilities, Patterns, Anti-Patterns, Related Skills) shows 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 | |
- 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.