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.
59
Quality
57%
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 ./.agent/skills/bun-development/SKILL.mdQuality
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
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill file functions as a pure index/table of contents with 30 sub-skill links but provides no actionable content in the main file itself. While progressive disclosure to sub-files is appropriate, the SKILL.md should include at minimum a quick-start example and key commands. The content fails to give Claude any executable guidance without navigating to sub-files.
Suggestions
Add a 'Quick Start' section with 3-5 essential Bun commands (e.g., `bun init`, `bun run`, `bun install`) directly in the main file
Include at least one executable code example showing basic Bun usage (e.g., a simple HTTP server with Bun.serve)
Remove or condense the 'When to Use This Skill' section - these use cases are self-evident from the skill title
Group the 30 sub-skills into logical categories (e.g., 'Package Management', 'Testing', 'APIs') with brief descriptions of what each section covers
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively lean but the 'When to Use This Skill' section explains obvious use cases Claude would infer. The numbered list of 30 sub-skills is efficient as a table of contents but could be more compact. | 2 / 3 |
Actionability | The skill body contains zero executable code, commands, or concrete examples. It's purely a navigation index with no actionable guidance in the main file itself. | 1 / 3 |
Workflow Clarity | No workflows are defined in this content. The numbered list suggests a learning sequence but provides no actual steps, validation checkpoints, or process guidance for any task. | 1 / 3 |
Progressive Disclosure | Good use of sub-skills for detailed content, but the main file is essentially just a table of contents with no quick-start content or overview. References are one level deep but there's no substantive content before the links. | 2 / 3 |
Total | 6 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.