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.

73

1.01x
Quality

60%

Does it follow best practices?

Impact

99%

1.01x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/bullmq-specialist/SKILL.md

The canonical home for this skill is bullmq-specialist in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

26%Weight 40%Scale 1-5

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

The body is well-structured at a section level but almost entirely placeholder content: it names capabilities and patterns without any code, commands, steps, or validation guidance. It reads as an outline rather than an actionable skill.

Suggestions

Replace each 'Patterns' and 'Anti-Patterns' entry with concrete, copy-paste-ready BullMQ code or commands (e.g. a minimal Queue/Worker setup, a delayed-job example, a DLQ configuration).

Add a sequenced workflow with validation checkpoints for risky operations (e.g. verify Redis connectivity, confirm job completion, inspect failed jobs before retrying).

Remove the persona narrative ('billions of jobs', 'debugged at 3am'), the empty 'Your core philosophy:' header, and the filler 'When to Use' sentence to tighten token efficiency.

DimensionReasoningScore

Conciseness

Mostly compact, but includes unnecessary persona padding ('processed billions of jobs', 'debugged stuck jobs at 3am') and empty filler like the dangling 'Your core philosophy:' header and the vacuous 'When to Use' line, which could be trimmed.

3 / 5

Actionability

No code, commands, or executable guidance anywhere — sections like 'Basic Queue Setup — Production-ready BullMQ queue with proper configuration' only describe topics rather than instructing, matching the 'entirely vague or abstract; only describes' anchor.

1 / 5

Workflow Clarity

There is no sequenced workflow, no steps, and no validation checkpoints for batch/destructive job-processing operations, fitting the 'steps missing or incoherent; no sequence; no validation' anchor.

1 / 5

Progressive Disclosure

No bundle files exist and none are needed for this short overview; content is organized into clear headed sections (Capabilities, Patterns, Anti-Patterns), with only minor gaps like the empty 'core philosophy' header.

4 / 5

Total

9

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states the skill's purpose and provides explicit, natural trigger terms. Minor specificity gaps prevent a perfect specificity score, but completeness and trigger coverage are excellent.

DimensionReasoningScore

Specificity

Names the domain (BullMQ, Redis-backed job queues) and several concrete capabilities — 'background processing, and reliable async execution in Node.js/TypeScript' — but stops short of comprehensive coverage of distinct actions, fitting the 'several specific actions; minor gaps' anchor.

4 / 5

Completeness

It explicitly answers both 'what' ('BullMQ expert for Redis-backed job queues, background processing...') and 'when' with concrete trigger phrases in the 'Use when:' clause.

5 / 5

Trigger Term Quality

The 'Use when: bullmq, bull queue, redis queue, background job, job queue' clause gives comprehensive coverage including natural synonyms (bullmq/bull queue) that users would actually say.

5 / 5

Distinctiveness Conflict Risk

BullMQ is a clear niche with distinct triggers (bullmq, bull queue, job queue) and minimal overlap risk with adjacent skills like redis-specialist.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.