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

Pending

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 users would say when needing this skill. However, it critically lacks any description of what the skill actually does — no concrete actions, capabilities, or outputs are listed. It reads as a pure 'Use when...' clause without the substantive capability description that should precede it.

Suggestions

Add concrete capability descriptions before the trigger clause, e.g., 'Configures wrangler.toml, sets up Bun-compatible Workers projects, handles build and deployment pipelines, and resolves compatibility issues between Bun and Cloudflare Workers.'

Restructure to lead with 'what it does' followed by 'when to use it', e.g., 'Scaffolds, builds, and deploys Cloudflare Workers applications using Bun as the runtime. Use when...'

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' component.	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 combination of 'Cloudflare Workers' and 'Bun' is a very specific niche. The trigger terms are distinct enough that this skill is unlikely to conflict with a general Cloudflare skill or a general Bun skill, as it targets the intersection of both technologies.	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.

This is a comprehensive, highly actionable skill with excellent executable code examples covering the full Cloudflare Workers ecosystem with Bun. Its main weaknesses are verbosity (too many full inline examples that could be referenced externally) and lack of validation/verification steps in the deployment and build workflows. The API compatibility table and common errors section add genuine value.

Suggestions

Move detailed binding examples (KV, D1, R2, Durable Objects) into the referenced bindings.md file and keep only one brief example inline to reduce the main file's length

Add explicit validation steps to the deployment workflow, e.g., 'bun test' before deploy, verify deployment with 'wrangler tail' or curl after deploy

Remove version-specific dependency versions (e.g., '@cloudflare/workers-types': '^4.20250906.0') or note them as examples to avoid staleness

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes more examples than necessary. Multiple full worker implementations (KV, D1, R2, Durable Objects, Cron) are verbose when Claude could infer patterns from one or two examples. The API compatibility table is useful but some sections could be condensed.	2 / 3
Actionability	All code examples are fully executable TypeScript/bash with proper imports, types, and complete implementations. Configuration files (wrangler.toml, package.json) are copy-paste ready with realistic values. The common errors table provides specific fixes.	3 / 3
Workflow Clarity	The Quick Start provides a clear sequence for project creation and deployment, but there are no validation checkpoints. For deployment (a potentially destructive operation), there's no 'verify deployment succeeded' step, no testing before deploy workflow, and the build-then-deploy sequence lacks validation between steps.	2 / 3
Progressive Disclosure	The skill references external files (references/bindings.md, references/performance.md) with clear loading criteria, which is good. However, the main file is quite long (~300 lines) with extensive inline examples for KV, D1, R2, Durable Objects, and R2 that could be split into reference files, making the overview leaner.	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: 88da5ff

Reviewed: 17 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.