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.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bullmq-specialist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 content is highly actionable with executable, copy-paste-ready BullMQ examples and a strong validation-checks section, but it is monolithic with no progressive disclosure to separate files and its workflows lack explicit validation feedback loops for batch operations.

Suggestions

Add explicit validate-fix-retry checkpoints to the workflows (e.g., after shutdown, verify no orphaned/stalled jobs remain before exiting) to lift workflow clarity above 3.

Move the larger reference material (full pattern library, collaboration stacks, validation-check catalog) into separate files under references/ and link to them from SKILL.md to improve progressive disclosure.

Trim the repeated 'When to use' boilerplate lines and verbose inline comments to tighten conciseness toward anchor 5.

DimensionReasoningScore

Conciseness

The body is dense and practical with executable code and terse principle bullets, only mildly padded by repeated 'When to use' boilerplate and verbose inline comments, fitting anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Provides copy-paste ready, fully executable code for queue/worker setup, delayed and repeatable jobs, job flows, graceful shutdown, and the bull-board dashboard, covering the common cases as in anchor 5.

5 / 5

Workflow Clarity

Multi-step sequences exist (graceful shutdown, collaboration workflows) but lack explicit validation checkpoints or validate-fix-retry feedback loops, and since BullMQ is a batch/background processing domain the rubric caps workflow clarity at 3.

3 / 5

Progressive Disclosure

The single file is well sectioned but contains no bundle files and no one-level-deep references, inlining content (full patterns, collaboration stacks) that a skill this large could split out, fitting anchor 3 rather than the well-signaled-references anchor 5.

3 / 5

Total

15

/

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 is specific and distinctive, naming a clear BullMQ niche with good trigger terms, but it lacks an explicit 'Use when...' clause so completeness is capped at 3. Adding concrete trigger guidance would raise the completeness and likely the overall score.

Suggestions

Append an explicit 'Use when...' clause listing natural user triggers (e.g., 'Use when the user mentions BullMQ, job queues, background jobs, delayed/repeatable jobs, or worker processes').

Add common synonyms and file/term variations (task queue, background tasks, scheduled jobs, cron) to broaden trigger term coverage toward anchor 5.

Replace the abstract 'reliable async execution' with one or two concrete actions (e.g., 'retries with backoff, dead-letter handling') to strengthen specificity.

DimensionReasoningScore

Specificity

Names the BullMQ domain plus several concrete capabilities ('Redis-backed job queues', 'background processing', 'reliable async execution', 'Node.js/TypeScript') with only minor coverage gaps, fitting anchor 4 rather than the exhaustive list of anchor 5.

4 / 5

Completeness

Provides a clear 'what' (BullMQ expert for job queues, background processing, async execution) but has no explicit 'Use when...' trigger clause, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes the natural terms users would say ('BullMQ', 'job queues', 'background processing', 'async execution') but misses some common synonyms like 'task queue', 'background tasks', 'cron', or 'scheduled jobs', so it lands at anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche tied to a named library ('BullMQ expert', 'Redis-backed job queues') with distinct triggers and minimal overlap with other skills, matching anchor 5.

5 / 5

Total

16

/

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
sickn33/antigravity-awesome-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.