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.

Quality

52%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Content

22%

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

This SKILL.md is essentially a bare table of contents with 30 links to sub-skill files and no substantive content of its own. It provides no executable code, no concrete examples, no workflow guidance, and no quick-start material. A good SKILL.md should include at least a concise quick-start section with key commands and examples, with sub-files reserved for detailed topics.

Suggestions

Add a Quick Start section with the most essential Bun commands (e.g., `bun init`, `bun install`, `bun run`) as executable examples directly in the SKILL.md.

Group the 30 sub-skills into logical categories (e.g., Package Management, Runtime APIs, Testing, Bundling, Migration) with brief 1-line descriptions for each group to aid navigation.

Include at least one concrete workflow (e.g., 'Create and run a new Bun project') with numbered steps and commands directly in the main file.

Add a decision-tree or brief guidance section helping Claude choose which sub-skill to consult based on the user's task.

Dimension	Reasoning	Score
Conciseness	The 'When to Use This Skill' section is somewhat unnecessary filler that Claude could infer. The numbered list of 30 sub-skills is reasonably lean as a table of contents, but the dual numbering system (list numbers + file prefixes) adds redundancy.	2 / 3
Actionability	The SKILL.md contains zero executable code, zero concrete commands, and zero specific examples. It is entirely a table of contents pointing to sub-skill files, providing no actionable guidance on its own.	1 / 3
Workflow Clarity	There is no workflow, sequence, or process described. The content is purely a flat list of links with no guidance on how to approach tasks, no validation steps, and no decision logic for choosing between sub-skills.	1 / 3
Progressive Disclosure	The skill does attempt progressive disclosure by linking to 30 sub-skill files, but the references are excessively granular (30 separate files) with no grouping or categorization in the main file beyond implicit numbering prefixes. Without bundle files to verify, and with no quick-start content inline, it fails to provide a useful overview before directing to sub-files.	2 / 3
	Total	6 / 12 Passed

Description

82%

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 solid description that clearly identifies its domain (Bun runtime) and provides explicit trigger guidance. Its main strengths are the comprehensive trigger terms and the explicit 'Use when' clause. The primary weakness is that the capability descriptions are somewhat category-level rather than listing specific concrete actions, and some terms could overlap with general JavaScript tooling skills.

Suggestions

Add more specific concrete actions like 'run scripts with bun run, install packages with bun install, execute tests with bun test, bundle applications with bun build' to increase specificity.

Strengthen distinctiveness by adding a negative boundary such as 'Not for general Node.js or npm workflows unless migrating to Bun' to reduce conflict with general JS/TS skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Bun runtime, JS/TS development) and lists some actions (package management, bundling, testing, migration), but these are category-level rather than deeply specific concrete actions like 'install packages with bun install' or 'run tests with bun test'.	2 / 3
Completeness	Clearly answers both 'what' (package management, bundling, testing, migration from Node.js) and 'when' with an explicit 'Use when...' clause covering three trigger scenarios: working with Bun, optimizing JS/TS speed, or migrating from Node.js.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'Bun', 'JavaScript', 'TypeScript', 'JS/TS', 'Node.js', 'package management', 'bundling', 'testing', 'migration'. These cover terms users would naturally use when seeking help with Bun-related tasks.	3 / 3
Distinctiveness Conflict Risk	While 'Bun' is a distinct trigger, terms like 'JavaScript/TypeScript development', 'package management', 'bundling', and 'testing' could overlap with general Node.js, npm, webpack, or other JS tooling skills. The Bun-specific focus helps but the broader JS/TS framing creates some conflict risk.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: Dokhacgiakhoa/antigravity-ide
Commit: c4a059b

Reviewed: 5 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.