bun-development
Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, or migrating from Node.js to Bun.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill bun-developmentOverall
score
80%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
92%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 is a strong skill description that clearly articulates specific capabilities (package management, bundling, testing, migration) and provides explicit 'Use when' triggers. The description uses proper third-person voice and includes natural developer terminology. Minor weakness is potential overlap with general JavaScript/TypeScript development skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'package management, bundling, testing, and migration from Node.js' - these are distinct, actionable capabilities within the Bun ecosystem. | 3 / 3 |
Completeness | Clearly answers both what ('package management, bundling, testing, migration') AND when ('Use when working with Bun, optimizing JS/TS development speed, or migrating from Node.js to Bun') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Bun', 'JavaScript', 'TypeScript', 'JS/TS', 'Node.js', 'migrating', 'package management', 'bundling', 'testing' - good coverage of terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | While Bun-specific, there's potential overlap with general JavaScript/TypeScript skills or Node.js skills. The 'JS/TS development' framing is somewhat broad and could conflict with other JS tooling skills. | 2 / 3 |
Total | 11 / 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 Bun development skill with excellent actionable code examples covering the full development lifecycle. However, it's overly verbose with unnecessary comparison tables and explanatory content, and lacks validation checkpoints in multi-step workflows like migration. The monolithic structure would benefit from progressive disclosure to separate reference material.
Suggestions
Remove the 'Why Bun?' comparison table and 'When to Use This Skill' section - Claude can infer these from context
Add explicit validation steps to the migration workflow (e.g., 'Run bun test to verify compatibility', 'Check for Node.js-specific APIs that need replacement')
Split detailed API references (SQLite, WebSockets, Testing matchers) into separate files and link from a concise overview
Add a troubleshooting checkpoint after 'bun build' commands to verify successful compilation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the 'Why Bun?' comparison table and explanatory sections that Claude already knows. The content is generally efficient but could be tightened by removing the feature comparison and some introductory text. | 2 / 3 |
Actionability | Excellent executable code examples throughout - installation commands, complete TypeScript snippets for file operations, HTTP servers, WebSockets, SQLite, testing, and bundling are all copy-paste ready with proper imports and context. | 3 / 3 |
Workflow Clarity | The migration section provides steps but lacks validation checkpoints. The build process doesn't include verification steps to confirm successful builds. For operations like migration from Node.js, there should be explicit validation steps to catch compatibility issues. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting advanced topics (WebSockets, SQLite, bundling) into separate reference files. The external resources at the end are good but inline content is too dense. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (692 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.