bun-cloudflare-workers

This skill should be used when the user asks about "Cloudflare Workers with Bun", "deploying Bun to Workers", "wrangler with Bun", "edge deployment", "Bun to Cloudflare", or building and deploying applications to Cloudflare Workers using Bun.

Quality

63%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/bun/skills/bun-cloudflare-workers/SKILL.md

Quality

Discovery

62%

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 excels at trigger term coverage and distinctiveness, providing many natural phrases a user might say. However, it critically lacks any description of what the skill actually does — it reads entirely as a 'Use when...' clause without specifying concrete actions like generating wrangler configs, setting up project scaffolding, or troubleshooting deployment issues. This makes it hard for Claude to understand the skill's actual capabilities.

Suggestions

Add concrete capability descriptions before the trigger clause, e.g., 'Scaffolds Cloudflare Workers projects using Bun, generates wrangler.toml configurations, handles deployment workflows, and troubleshoots common edge deployment issues.'

Restructure to lead with 'what it does' followed by 'Use when...', e.g., 'Configures, builds, and deploys Bun applications to Cloudflare Workers. Use when the user asks about...'

Dimension	Reasoning	Score
Specificity	The description does not list any concrete actions or capabilities. It only describes when to use the skill ('when the user asks about...') but never states what the skill actually does beyond the vague 'building and deploying applications to Cloudflare Workers using Bun.'	1 / 3
Completeness	The 'when' is explicitly and thoroughly covered with multiple trigger phrases. However, the 'what does this do' is essentially missing — there is no description of specific capabilities, actions, or outputs the skill provides. The description is almost entirely a 'Use when...' clause with no substantive 'what' section.	2 / 3
Trigger Term Quality	The description includes many natural trigger phrases users would actually say: 'Cloudflare Workers with Bun', 'deploying Bun to Workers', 'wrangler with Bun', 'edge deployment', 'Bun to Cloudflare'. These cover multiple natural variations of how a user might phrase their request.	3 / 3
Distinctiveness Conflict Risk	The description targets a very specific niche — Cloudflare Workers deployment using Bun with wrangler. This is unlikely to conflict with other skills due to the highly specific technology combination mentioned.	3 / 3
	Total	9 / 12 Passed

Implementation

64%

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

The skill provides highly actionable, executable code examples covering a broad range of Cloudflare Workers features with Bun. However, it is overly long and monolithic—most binding-specific code (KV, D1, R2, Durable Objects) should live in the referenced files rather than inline. The deployment workflow lacks validation checkpoints, and the referenced bundle files don't actually exist.

Suggestions

Move KV, D1, R2, Durable Objects, and Hono examples into the referenced `references/bindings.md` file, keeping only the basic worker example inline to improve conciseness and progressive disclosure.

Add validation/verification steps to the deployment workflow, e.g., 'After deploy, verify with: curl https://my-worker.<subdomain>.workers.dev/' and 'Check logs: bunx wrangler tail'.

Create the referenced bundle files (references/bindings.md, references/performance.md) so the progressive disclosure references actually resolve.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~300 lines) and includes many full code examples for features Claude already knows well (basic fetch handlers, KV get/put, D1 queries, R2 storage). The API compatibility table and common errors table are efficient, but the extensive inline code for every Cloudflare binding type could be trimmed or moved to reference files.	2 / 3
Actionability	All code examples are fully executable TypeScript with proper types, complete function signatures, and copy-paste ready configurations. The wrangler.toml examples, package.json, and build scripts are concrete and specific.	3 / 3
Workflow Clarity	The Quick Start provides a clear sequence (create → install → dev → deploy), but there are no validation checkpoints anywhere in the deployment workflow. No verification steps after deploy, no guidance on checking logs or testing the deployed worker, and no error recovery feedback loops for the build-deploy process.	2 / 3
Progressive Disclosure	The skill references `references/bindings.md` and `references/performance.md` at the bottom with clear loading criteria, which is good. However, no bundle files exist to back these references, and the main file is monolithic with extensive inline code for KV, D1, R2, Durable Objects, Hono, cron, and testing that should be split into those reference files rather than inlined.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Commit: 5e92b71

Reviewed: 21 days ago

Table of Contents

Discovery Implementation Validation

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.