CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bun-workers

Use for Web Workers in Bun, worker_threads, parallel processing, and background tasks.

49

Quality

62%

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 ./plugins/bun/skills/bun-workers/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 a well-organized, mostly executable pattern cookbook with good breadth across Web Workers and worker_threads in Bun. Its two real weaknesses are broken progressive disclosure — references are named but the files don't exist — and the absence of validation/error-recovery in the batch-oriented pool patterns, plus a few small handler-management bugs in the pool code.

Suggestions

Create the actual `references/optimization.md` and `references/patterns.md` files (or remove the "When to Load References" section) so the body's navigation pointers resolve to real files.

Move advanced material (worker pool, parallel map, message channel) into the reference files to slim SKILL.md into a true overview with working basic examples.

Add validation and error-recovery to the WorkerPool example: reject queued promises on worker error, then respawn the worker, so batch execution has a feedback loop.

DimensionReasoningScore

Conciseness

The body is almost entirely executable code with minimal prose and assumes Claude's competence. The main trimmable redundancy is the "Worker with URL" section repeating the identical `new Worker(new URL("./worker.ts", import.meta.url))` line already shown in Basic Usage, which keeps it just below the lean anchor 5.

4 / 5

Actionability

Concrete, executable TypeScript examples cover the common cases (basic messaging, transferables, SharedArrayBuffer/Atomics, worker_threads, pools, termination, error handling). Minor gaps: `processNext` re-assigns `worker.onmessage` on each call accumulating handlers, and the pool's permanent `on("message")` handler coexists with `once("message", resolve)` while worker errors never reject queued promises — real but minor defects, matching anchor 4 rather than fully copy-paste-safe 5.

4 / 5

Workflow Clarity

This is a pattern reference rather than a sequenced workflow, and worker-pool execution is a batch operation with no validation or error-recovery loop (a failed task's promise is never rejected), which caps this dimension at 3 per the batch-operations guideline. It stays above 2 because the Termination section does model a graceful-shutdown-then-timeout checkpoint.

3 / 5

Progressive Disclosure

The "When to Load References" section directs Claude to `references/optimization.md` and `references/patterns.md`, but no references directory or bundle files exist — the navigation pointers are broken. Meanwhile ~375 lines of advanced material (worker pool, parallel map, message channel) that the skill itself implies belongs in those files is inlined, matching anchor 2 rather than 3 or 4 because the referenced files are not real.

2 / 5

Total

13

/

20

Passed

Description

47%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 has strong, natural trigger terms for a well-defined Bun-workers niche, but it is missing the "what" half entirely — it never states what the skill provides or does. Adding a concrete capability clause (e.g., "Create and manage workers... ") would lift both completeness and specificity substantially.

Suggestions

Add an explicit 'what' clause stating concrete capabilities, e.g. "Create and manage Web Workers and worker_threads in Bun: spawning workers, transferring buffers, worker pools, graceful termination."

Include common synonyms users might say, such as "thread pool", "concurrency", or "multi-threading", to broaden natural trigger coverage.

Consider trimming the generic "parallel processing, and background tasks" or making them more specific to reduce overlap with general async/concurrency skills.

DimensionReasoningScore

Specificity

"Use for Web Workers in Bun, worker_threads, parallel processing, and background tasks" names the domain precisely but contains no capability verbs at all — it never states what the skill actually does (create, configure, or terminate workers). This matches the anchor "names the domain but actions are minimal or generic"; it falls short of 3 because no concrete actions are listed.

2 / 5

Completeness

The description is only a "when" clause ("Use for...") with no "what" — it mirrors the bad-anchor pattern "Use when working with documents" almost exactly. It does not reach 3 because a clear statement of what the skill does is entirely absent.

2 / 5

Trigger Term Quality

"Web Workers", "worker_threads", "parallel processing", and "background tasks" are natural phrases users would say when needing this skill. Good coverage, but common synonyms like "thread pool", "concurrency", or "multi-threading" are missing, so it falls short of the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

"Web Workers in Bun" and "worker_threads" define a clear niche with minimal conflict risk, but the trailing "parallel processing, and background tasks" are broad generic terms that overlap with general concurrency/async skills. Mostly distinct with minor overlap, matching anchor 4 rather than 3.

4 / 5

Total

12

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/bun/skills/bun-workers/SKILL.md

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.