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 ./.agent/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 file is essentially a table of contents with persona framing but no substantive content. It delegates everything to sub-skills without providing any quick-start guidance, code examples, or workflow overview in the main file. The capabilities list and anti-pattern markers (❌) show good organization intent, but the complete absence of actionable content makes this ineffective as a standalone skill.
Suggestions
Add a Quick Start section with a minimal executable BullMQ queue + worker example (5-10 lines of TypeScript)
Include a brief workflow overview showing the typical sequence: create queue → add jobs → process with worker → handle failures
Add 1-2 sentence descriptions to each sub-skill link explaining what problem it solves
Remove or condense the persona narrative ('debugged stuck jobs at 3am') - Claude doesn't need motivation, just instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The persona introduction is somewhat verbose with unnecessary narrative ('debugged stuck jobs at 3am'). The capabilities list is efficient but the philosophical framing adds tokens without actionable value. | 2 / 3 |
Actionability | No concrete code, commands, or executable examples provided. The content describes capabilities and links to sub-skills but provides zero actionable guidance in the main file itself. | 1 / 3 |
Workflow Clarity | No workflow steps, sequences, or validation checkpoints are present. The skill lists capabilities and links but provides no guidance on how to actually use BullMQ or in what order to approach tasks. | 1 / 3 |
Progressive Disclosure | Good use of sub-skill references with clear one-level-deep links, but the main file lacks any quick-start content or overview of what each sub-skill covers. The 'Patterns' section is empty, suggesting incomplete structure. | 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 | |
3395991
Table of Contents
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.