bun-development
Fast, modern JavaScript/TypeScript development with the Bun runtime, inspired by [oven-sh/bun](https://github.com/oven-sh/bun).
44
32%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/bun-development/SKILL.mdQuality
Discovery
22%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 is too vague and lacks concrete actions, explicit trigger guidance, and a 'Use when...' clause. While it correctly identifies the Bun runtime as its domain, it fails to explain what specific tasks it enables or when Claude should select it over other JavaScript/TypeScript-related skills.
Suggestions
Add specific concrete actions like 'Run scripts, install packages, bundle code, and execute tests using the Bun runtime'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions Bun, bun.sh, bunx, bun install, or wants a fast alternative to Node.js/npm.'
Include more natural trigger terms and file extensions like 'bunfig.toml', 'bun.lockb', 'bunx', 'bun test', 'bun build' to improve distinctiveness from generic JS/TS skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'JavaScript/TypeScript development with the Bun runtime' but does not list any concrete actions (e.g., run scripts, install packages, bundle code, test). It names a domain but no specific capabilities. | 1 / 3 |
Completeness | The description loosely addresses 'what' (JavaScript/TypeScript development with Bun) but provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance, and even the 'what' is vague. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'JavaScript', 'TypeScript', 'Bun runtime', and 'Bun' which users might naturally mention. However, it misses common variations like 'bun install', 'bun run', 'package manager', 'bundler', or '.ts files'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Bun runtime' specifically helps distinguish it from generic JS/TS skills, but 'JavaScript/TypeScript development' is broad enough to overlap with Node.js, Deno, or general JS/TS coding skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is a comprehensive Bun reference guide with excellent, executable code examples, but it severely violates conciseness and progressive disclosure principles. It reads more like full documentation than a skill file — much of the content (basic test matchers, Node.js compatibility details, comparison tables) is either already known to Claude or should be split into separate reference files. The lack of validation checkpoints in multi-step workflows like migration also weakens its effectiveness.
Suggestions
Reduce content by 60-70%: remove the 'Why Bun?' comparison table, basic test matcher listings, Node.js compatibility explanations, and other content Claude already knows. Focus on Bun-specific gotchas and patterns only.
Split into multiple files: move testing details to TESTING.md, SQLite/APIs to API_REFERENCE.md, migration guide to MIGRATION.md, and bundling to BUNDLING.md, with one-line references from the main skill.
Add validation checkpoints to the migration workflow (section 8.2): e.g., 'Run bun test to verify tests pass after migration' and 'Check for Node.js-specific APIs that need replacement'.
Remove the 'When to Use This Skill' section — Claude can infer applicability from the content itself.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Includes extensive content Claude already knows (basic test matchers, what environment variables are, comparison tables with Node.js, basic SQL operations). The 'Why Bun?' table, migration compatibility section explaining that fs/path/crypto work, and exhaustive matcher listings are all unnecessary padding. | 1 / 3 |
Actionability | All code examples are concrete, executable, and copy-paste ready. Commands are specific with real flags and arguments. TypeScript examples are complete and runnable, from HTTP servers to SQLite queries to build configurations. | 3 / 3 |
Workflow Clarity | The migration section (8.2) provides a clear sequence of steps, and project setup is well-ordered. However, there are no validation checkpoints — e.g., no verification after migration steps, no error handling guidance for build failures beyond checking result.success, and no feedback loops for common failure scenarios. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with everything inlined. The full API reference for file I/O, HTTP servers, WebSockets, SQLite, password hashing, testing matchers, mocking, bundling, and migration are all in one file. Content like the complete testing matchers reference, SQLite examples, and WebSocket server setup should be in separate referenced files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (697 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
d739c8b
- 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.