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.

63

1.01x
Quality

44%

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/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

18%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-sectioned but almost entirely non-instructional: it relies on persona framing and one-line pattern descriptions with no code, commands, or sequenced workflow. It functions as an outline rather than actionable guidance.

Suggestions

Replace the persona intro and 'core philosophy' filler with concrete code: a basic Queue/Worker setup, a delayed-job example, and a flow-producer example.

Expand each Patterns subsection into executable steps with configuration values (concurrency, removeOnComplete, attempts/backoff) rather than single descriptive sentences.

Add validation/verification guidance for job operations (inspecting failed jobs, retry/backoff behavior, DLQ handling) so the workflow includes checkpoints.

DimensionReasoningScore

Conciseness

The persona intro ('processed billions of jobs', 'queues... decouple services, smooth traffic spikes') explains queue concepts Claude already knows, and 'Your core philosophy:' dangles with no content, matching the noticeably-verbose/padded anchor rather than the mostly-efficient 3.

2 / 5

Actionability

There is no code, command, or executable guidance anywhere; sections like 'Production-ready BullMQ queue with proper configuration' only describe, fitting the entirely-vague/no-instruction anchor.

1 / 5

Workflow Clarity

No multi-step process is sequenced and no validation checkpoints exist for batch/job operations; the Patterns section is only titles with one-line descriptions, matching the steps-missing anchor.

1 / 5

Progressive Disclosure

The file is under 50 lines with no external references needed and is organized into labeled sections (Capabilities, Patterns, Anti-Patterns, Related Skills); minor gaps (a redundant 'When to Use' and dangling 'core philosophy') keep it at 4 rather than 5.

4 / 5

Total

8

/

20

Passed

Description

70%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.

The description clearly identifies a distinct niche and supplies an explicit Use-when trigger list with natural synonyms. Its main weakness is framing capabilities as a domain summary rather than enumerating concrete actions.

DimensionReasoningScore

Specificity

Names the domain ('Redis-backed job queues, background processing, and reliable async execution') but offers only high-level framing rather than a list of concrete actions, matching the 1-2 concrete actions anchor; not 4 because no enumerated specific actions.

3 / 5

Completeness

Both 'what' and an explicit 'Use when:' trigger clause are present; the 'what' is domain-framed ('expert for...') rather than a concrete action list, so it sits at 4 rather than the fully-explicit 5 anchor.

4 / 5

Trigger Term Quality

The 'Use when: bullmq, bull queue, redis queue, background job, job queue' clause covers natural synonyms a user would say, but omits common variations like 'worker', 'cron', or 'scheduled jobs', fitting the good-but-incomplete anchor.

4 / 5

Distinctiveness Conflict Risk

BullMQ is a specific, well-scoped niche with distinct triggers, but the 'redis queue' trigger could overlap with a generic redis skill, giving minor conflict risk consistent with the 4 anchor.

4 / 5

Total

15

/

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.