bun-development

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable, packed with executable, copy-paste-ready code and commands across all Bun features, and is well organized by section. Its weaknesses are verbosity/duplication, a destructive migration workflow lacking validation checkpoints, and a monolithic single-file structure with no progressive disclosure to separate reference files.

Suggestions

Add a validation/rollback checkpoint to the Node.js migration workflow (e.g. verify the app runs under Bun before deleting node_modules, or back up package-lock.json).

Split the large reference material (built-in APIs, testing matchers, bundling/migration details) into separate files in references/ and link to them from SKILL.md to apply progressive disclosure.

Remove duplication — the Homebrew install block and the Quick Reference table restate commands already shown — and trim the promotional 'Why Bun?' comparison table.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean reference material (executable code, command tables) that assumes Claude's competence, but at ~700 lines it is voluminous with mild duplication (Homebrew listed twice, a Quick Reference table restating prior commands) and a promotional 'Why Bun?' table that could be trimmed, fitting the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	Nearly every section provides fully executable, copy-paste-ready commands and code (bun init/add/test/build, Bun.serve, full tsconfig and package.json, test matchers, build API), matching the 'fully executable code/commands; copy-paste ready' anchor rather than the pseudocode/incomplete score-2 anchor.	3 / 3
Workflow Clarity	The one multi-step process ('Common Migration Steps') is numbered but lacks validation checkpoints, and it includes a destructive step ('rm -rf node_modules package-lock.json') with no verify/recovery loop, which per the guidelines caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is a single monolithic ~700-line SKILL.md with no external references; sections are well-organized, but API/migration/testing detail that should be split into separate reference files is inline, matching the 'content that should be separate is inline' anchor rather than the deeply-nested score-1 case.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 clearly identifies a distinct niche (Bun-runtime JS/TS development) with usable trigger terms, but it lacks concrete action verbs and omits any explicit 'when to use' trigger clause. It reads as a domain statement rather than a what-and-when summary.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggering situations (e.g. 'Use when starting a Bun project, migrating from Node.js, or using Bun's bundler/test runner').

Replace the abstract 'development with' phrasing with specific concrete actions (e.g. 'scaffold, run, test, bundle, and deploy JS/TS with Bun').

Include common natural trigger terms a user would actually say, such as 'bun test', 'bun build', or 'migrate Node.js to Bun'.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain ('JavaScript/TypeScript development with the Bun runtime') but uses abstract language ('development with') rather than listing multiple concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It answers 'what' (JS/TS development with Bun) but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2 — 'when' is missing rather than implied.	2 / 3
Trigger Term Quality	It includes relevant natural keywords a user would say ('JavaScript', 'TypeScript', 'Bun', 'Bun runtime') but misses common variations like 'bun test', 'bun bundler', or 'migrate from Node to Bun', fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Tying the skill explicitly to the Bun runtime (and citing oven-sh/bun) gives it a clear niche with distinct triggers unlikely to conflict with general JS/TS skills, matching the 'clear niche with distinct triggers' anchor; it is not generic like a score-2 example.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (707 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 9fc5f98

Reviewed: 4 days 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.