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.
48
51%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/bun/skills/bun-bundler/SKILL.mdQuality
Discovery
37%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a list of trigger terms with no explanation of what the skill actually does. While the trigger term coverage is excellent and would help Claude match user queries, the complete absence of capability descriptions means Claude cannot understand what actions this skill enables or what outputs it produces. The description inverts the typical problem — it has strong 'when' but zero 'what'.
Suggestions
Add concrete capability descriptions before the trigger terms, e.g., 'Configures and runs Bun.build() for JavaScript/TypeScript bundling, including code splitting, tree shaking, minification, sourcemap generation, and multi-target output (browser/Node).'
Restructure to lead with 'what it does' followed by 'Use when...' — e.g., 'Guides configuration of Bun's built-in bundler for production builds, plugin setup, and output optimization. Use when the user asks about...'
Rewrite trigger clause in third person voice (e.g., 'Applies when the user asks about...') rather than the current second-person-adjacent 'This skill should be used when the user asks about...' phrasing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists no concrete actions or capabilities. It only describes when to use the skill (trigger scenarios) but never states what the skill actually does — no verbs like 'bundles', 'configures', 'optimizes', etc. | 1 / 3 |
Completeness | The description answers 'when' extensively but completely fails to answer 'what does this do'. There is no explanation of the skill's capabilities, outputs, or concrete actions it performs. The 'what' component is entirely missing. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'bun build', 'Bun.build', 'code splitting', 'tree shaking', 'minification', 'sourcemaps', 'bundle optimization', 'esbuild alternative', 'building for production', 'bundling TypeScript', and variations for browser/Node targets. | 3 / 3 |
Distinctiveness Conflict Risk | The trigger terms are fairly specific to Bun's bundler, which helps distinguish it from generic bundling skills. However, terms like 'code splitting', 'tree shaking', 'minification', and 'building for production' could overlap with webpack, Vite, or esbuild skills if present. | 2 / 3 |
Total | 7 / 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 solid, highly actionable reference skill for Bun's bundler with excellent executable code examples covering CLI, JavaScript API, plugins, and common patterns. Its main weaknesses are moderate verbosity from redundant sections (target environments, overlapping CLI/API docs) and the lack of actual bundle files to support the referenced progressive disclosure structure. The workflow could benefit from more explicit validation steps for production build processes.
Suggestions
Consolidate the Target Environments section into a brief note (e.g., 'Set target to "browser", "bun", or "node"') rather than three nearly identical code blocks.
Move the CLI flags table and loaders table into the referenced files (references/options.md) to reduce the main skill's token footprint and actually implement the progressive disclosure that's promised.
Add an explicit production build workflow with validation steps: clean output dir → build → check result.success → verify output files exist → optional size reporting.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some redundancy—the target environments section repeats nearly identical code blocks three times with only the target value changed, and the CLI flags table largely duplicates information already shown in the Bun.build options. The loaders table and some sections could be tightened. | 2 / 3 |
Actionability | Excellent actionability throughout—every section provides fully executable, copy-paste ready code examples for both CLI and JavaScript API usage. The common patterns section gives complete, real-world build configurations, and the build output section shows how to handle results including error checking. | 3 / 3 |
Workflow Clarity | The Quick Start and Build Script sections show a clear build-then-check-errors flow, and the common errors table is helpful. However, there's no explicit multi-step workflow with validation checkpoints for production builds (e.g., clean dist → build → validate output → deploy), and the build process lacks feedback loops for error recovery beyond a simple exit. | 2 / 3 |
Progressive Disclosure | The skill references three separate files (references/options.md, references/plugins.md, references/macros.md) with clear loading conditions, which is good structure. However, no bundle files are provided, so these references don't actually exist, and the main SKILL.md itself is quite long (~250 lines) with content like the full CLI flags table and loaders table that could be offloaded to reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%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
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.