CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

46

Quality

48%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/bullmq-specialist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

7%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is almost entirely a shell — it has persona narrative, an empty 'Patterns' section, a keyword-only 'Capabilities' list, and links to sub-skills with no substantive content in the main file itself. There is no executable code, no concrete guidance, and no workflow description. The only redeeming quality is the organized linking to sub-skill files, but the main SKILL.md fails to serve as a useful overview or quick reference.

Suggestions

Add a concrete quick-start section with executable code showing basic queue creation, job addition, and worker processing (e.g., `new Queue('myQueue', { connection })`, `queue.add()`, `new Worker()`).

Replace the persona narrative with a brief 1-2 line purpose statement and remove the 'Capabilities' keyword list — instead integrate those concepts into actionable sections or brief descriptions of what each sub-skill covers.

Add at least one complete workflow with validation steps, such as setting up a queue with connection verification, adding a job, and confirming processing.

Fill the empty 'Patterns' section with concrete anti-pattern examples or common configuration snippets, or remove it entirely.

DimensionReasoningScore

Conciseness

The opening paragraphs are verbose persona-building fluff that Claude doesn't need ('You've debugged stuck jobs at 3am', 'processed billions of jobs'). The 'Capabilities' section is just a list of keywords with no actionable content. The 'Patterns' section is empty. Most tokens are wasted on narrative rather than instruction.

1 / 3

Actionability

There is zero executable code, no concrete commands, no configuration examples, no specific guidance on how to use BullMQ. The entire content is either persona description, a keyword list, or links to sub-skills. The SKILL.md itself provides no actionable instruction whatsoever.

1 / 3

Workflow Clarity

There are no workflows, no steps, no sequences, and no validation checkpoints described. The content is entirely structural (links and lists) with no process guidance for any queue operation.

1 / 3

Progressive Disclosure

The skill does link to six sub-skill files with descriptive names, which shows some structural intent. However, the main SKILL.md provides no quick-start content or overview of what each sub-skill covers, and without bundle files to verify the references exist, the navigation is present but the overview layer is essentially empty.

2 / 3

Total

5

/

12

Passed

Description

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 specific tasks the skill can help with (e.g., creating workers, configuring retries, setting up scheduled jobs). The distinctiveness is excellent due to the specific technology focus.

Suggestions

Add specific concrete actions like 'create workers, configure retry policies, set up scheduled/recurring jobs, manage job priorities and rate limiting' to improve specificity.

DimensionReasoningScore

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

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
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.