CtrlK
BlogDocsLog inGet started
Tessl Logo

bun-bundler

This skill should be used when the user asks about "bun build", "Bun.build", "bundling with Bun", "code splitting", "tree shaking", "minification", "sourcemaps", "bundle optimization", "esbuild alternative", "building for production", "bundling TypeScript", "bundling for browser", "bundling for Node", or JavaScript/TypeScript bundling with Bun.

59

Quality

68%

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-bundler/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

A highly actionable, code-rich reference for Bun.build that scores well on concrete guidance, but it is padded with duplicated options content, lacks a sequenced validation workflow, and references two bundle files that are missing.

Suggestions

Remove the duplicated options block from the body and defer detail to references/options.md, keeping only a minimal quick-start example inline.

Fix or remove the references to the nonexistent plugins.md and macros.md files, or create them so the "When to Load References" section is accurate.

Add a short end-to-end build workflow (configure entrypoints → set target/format → minify → build → verify result.success) with an explicit validation checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly lean code examples and tables, but the opening line ("fast JavaScript/TypeScript bundler... esbuild-compatible alternative with native performance") is marketing fluff, and the full Bun.build options block duplicates what is already in references/options.md.

2 / 3

Actionability

It provides executable CLI commands, complete Bun.build calls, a full plugin example, and flag/loader tables — all copy-paste ready with concrete values.

3 / 3

Workflow Clarity

Content is organized by feature rather than as a sequenced workflow; the Build Output section shows a success check and error logging, but there is no end-to-end build workflow with explicit validation checkpoints.

2 / 3

Progressive Disclosure

A "When to Load References" section signals references, but references/plugins.md and references/macros.md are cited yet do not exist, and the options content is both inlined in the body and duplicated in options.md.

2 / 3

Total

9

/

12

Passed

Description

72%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A trigger-heavy description with excellent natural keyword coverage and a distinct Bun-scoped niche, but it omits an explicit statement of what the skill does, relying entirely on when-to-use phrasing.

Suggestions

Lead with a concrete capability statement such as "Builds and bundles JavaScript/TypeScript projects with Bun's bundler, supporting code splitting, minification, and sourcemaps." before the trigger list.

Keep the trigger list but pair it with an explicit "Use when..." clause so both what and when are clearly answered.

DimensionReasoningScore

Specificity

The description names the bundling domain and implies actions via trigger terms like "code splitting", "minification", and "sourcemaps", but it never states the concrete capability (e.g. "bundles/builds JS/TS") as an action — only as topics to ask about.

2 / 3

Completeness

It has explicit, strong "when" guidance but the "what" is only implied; it never states what the skill does, only when to use it, so completeness is capped at 2.

2 / 3

Trigger Term Quality

It lists many natural terms a user would actually say — "bun build", "Bun.build", "esbuild alternative", "building for production", "bundling for browser/Node" — giving strong keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Triggers are anchored to a clear Bun-specific niche ("bun build", "Bun.build", "bundling with Bun") making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
secondsky/claude-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.