bun-development

Fast, modern JavaScript/TypeScript development with the Bun runtime, inspired by [oven-sh/bun](https://github.com/oven-sh/bun).

Quality

32%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/bun-development/SKILL.md

Quality

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 actionable detail. It identifies the domain (Bun runtime for JS/TS) but fails to list specific capabilities and entirely omits trigger guidance for when Claude should select this skill. The 'inspired by' reference to the GitHub repo adds no functional value for skill selection.

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 such as 'Use when the user mentions Bun, bun.sh, bunx, bun install, or wants a fast alternative to Node.js for running JavaScript/TypeScript.'

Remove the 'inspired by' GitHub reference which wastes space and adds no selection value; replace with distinguishing capabilities like 'bun:test', 'Bun.serve()', or 'bun build'.

Dimension	Reasoning	Score
Specificity	The description says 'JavaScript/TypeScript development with the Bun runtime' but does not list any concrete actions. It describes a domain and a tool but no specific capabilities like 'run scripts', 'install packages', 'bundle code', or 'test projects'.	1 / 3
Completeness	The description partially addresses 'what' (JavaScript/TypeScript development with Bun) but is vague about specific capabilities, and completely lacks a 'when' clause or any explicit trigger guidance. The missing 'Use when...' clause would cap this at 2 regardless, but the weak 'what' brings it to 1.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'JavaScript', 'TypeScript', 'Bun runtime', and 'Bun' which users might naturally mention. However, it misses common variations and related terms like 'bun install', 'bun run', 'package manager', 'bundler', '.ts files', or 'node alternative'.	2 / 3
Distinctiveness Conflict Risk	While 'Bun runtime' is somewhat distinctive, the broad framing of 'JavaScript/TypeScript development' could easily overlap with Node.js skills, general JS/TS development skills, or other runtime-specific skills. The Bun-specific aspect provides some distinction but the overall scope is too broad.	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.

This skill is essentially a comprehensive Bun documentation page rather than a focused, efficient skill file. While the code examples are excellent and fully executable, the content is far too verbose — it explains things Claude already knows, includes exhaustive API references inline, and doesn't leverage progressive disclosure at all. The migration workflow also lacks validation checkpoints.

Suggestions

Reduce the SKILL.md to a concise overview (~100 lines) covering quick start, key Bun-native APIs, and common commands, then move detailed sections (testing matchers, build API options, WebSocket examples, SQLite reference) into separate referenced files.

Remove the 'Why Bun?' comparison table and explanatory content that Claude already knows — focus only on Bun-specific syntax and APIs that differ from standard Node.js knowledge.

Add explicit validation steps to the migration workflow (e.g., 'Run bun test to verify all tests pass after migration', 'Check bun run start works before deleting node_modules').

Cut the exhaustive matcher listing in section 6.3 — Claude knows Jest-compatible matchers; only document Bun-specific testing differences.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~500+ lines. Includes extensive content Claude already knows: comparison tables (Node vs Bun), basic concepts like how to install packages, full matcher listings, migration steps that are largely obvious, and explanations of standard APIs. The 'Why Bun?' table, tsconfig explanations, and exhaustive matcher examples are unnecessary padding.	1 / 3
Actionability	All code examples are concrete, executable, and copy-paste ready. Commands are specific with real flags and arguments. Examples cover real use cases like HTTP servers, SQLite, testing, and bundling with complete, runnable code blocks.	3 / 3
Workflow Clarity	The migration section (8.2) provides a numbered sequence but lacks validation checkpoints — no step to verify the migration worked, test that packages installed correctly, or confirm compatibility. The build workflow also lacks verification of build output. For a skill covering migration and bundling (potentially destructive operations), explicit validation steps are missing.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with no bundle files to offload detailed content. The entire API reference, testing guide, bundling guide, migration guide, and performance tips are all inline. Content like the full matchers reference, SQLite examples, WebSocket server setup, and build API options should be in separate referenced files rather than crammed into a single SKILL.md.	1 / 3
	Total	7 / 12 Passed

Validation

81%

Warnings & errors only

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 (702 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: e40fdb8

Reviewed: about 2 hours ago

Table of Contents

Discovery Implementation Validation

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.