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.
67
58%
Does it follow best practices?
Impact
Pending
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
44%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 heavily lopsided: it provides excellent trigger term coverage but completely omits what the skill actually does. It reads as a pure 'Use when...' clause with no 'what' clause, making it impossible for Claude to understand the skill's capabilities. Adding concrete actions like 'Configures and runs Bun.build for bundling JavaScript/TypeScript, including code splitting, tree shaking, and minification' would dramatically improve it.
Suggestions
Add a 'what' clause at the beginning describing concrete capabilities, e.g., 'Configures Bun.build to bundle JavaScript and TypeScript projects, set up code splitting, enable tree shaking, generate sourcemaps, and optimize bundles for production.'
Restructure to follow the pattern: capabilities first, then 'Use when...' triggers, rather than having only trigger terms with no description of actions.
Replace the leading 'This skill should be used when' with third-person action verbs describing what the skill does, then append the trigger guidance as a separate 'Use when...' sentence.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists no concrete actions or capabilities. It only describes when to use the skill (trigger terms) but never says 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. | 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 highly specific to Bun's bundler functionality, with distinct terms like 'Bun.build', 'bun build', and 'esbuild alternative' that clearly carve out a niche unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
72%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, well-structured bundler reference skill with excellent actionability and good progressive disclosure. Its main weaknesses are some redundancy in the target environments and CLI flags sections (which largely duplicate the options block), and a lack of explicit validation workflows for verifying build output. Overall it serves as an effective quick reference for Bun's bundler.
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.
Add a brief validation step to the workflow, such as checking output file existence/size or running the bundled output to verify correctness.
| 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 — all code examples are fully executable and copy-paste ready, covering CLI usage, JavaScript API, plugins, build output handling, and common patterns like production and library builds. Error handling is shown explicitly. | 3 / 3 |
Workflow Clarity | The build script pattern includes error checking (result.success check with process.exit), but there's no explicit validation workflow for verifying build output correctness (e.g., checking output file sizes, testing the bundle works). For a bundling skill, a validate-fix-retry loop for common build failures would strengthen this. | 2 / 3 |
Progressive Disclosure | The skill has a clear Quick Start section followed by progressively detailed sections, and appropriately references external files (references/options.md, references/plugins.md, references/macros.md) with clear guidance on when to load them. Navigation is well-structured and one level deep. | 3 / 3 |
Total | 10 / 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
88da5ff
- 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.