Name: bun-runtime
Rating: 60.8 (1 reviews)
Author: affaan-m

bun-runtime

Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/bun-runtime/SKILL.md

The canonical home for this skill is bun-runtime in affaan-m/ECC

Quality

Content

76%Weight 40%Scale 1-5

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 with executable examples across Bun's main capabilities and is well-structured and concise. Workflow clarity is the weakest dimension because the migration and Vercel guidance is presented as informal sequences without explicit validation checkpoints.

Suggestions

Tighten the few padded phrases (e.g., drop 'significantly faster than npm/yarn' and 'implemented in Zig' unless decision-relevant) to push conciseness toward 5.

Convert the Vercel deploy guidance into an explicit numbered sequence with a verification step (e.g., confirm the runtime is set, then build, then install with --frozen-lockfile, then verify the build output) to raise workflow clarity.

Add a short validation cue for migrations (e.g., run 'bun test' after swapping node → bun to confirm compatibility).

Dimension	Reasoning	Score
Conciseness	The body is largely lean with well-chosen code blocks and minimal padding; only minor instances of over-explanation ('significantly faster than npm/yarn', 'implemented in Zig') could be trimmed, matching the 'efficient; minor over-explanation' anchor rather than the fully lean 5.	4 / 5
Actionability	Provides copy-paste-ready, executable commands and code across the common cases — 'bun install', 'bun run dev', 'bun test', bun:test imports, Bun.file, and Bun.serve — fully covering the common usage surface, matching the 'fully executable; covers common cases' anchor.	5 / 5
Workflow Clarity	Light sequences exist (migration replacements, Vercel set-runtime → build → install) but they are informal topic-style listings without explicit checkpoints or validation; no destructive/batch operations trigger the cap, so this fits the 'steps present but checkpoints missing/implicit' anchor.	3 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and is organized into clearly labeled sections (When to Use, How It Works, Examples, Best Practices) with good navigation; it is over 50 lines so the simple-skill 5 does not apply, fitting the 'good structure; minor organization gaps' anchor.	4 / 5
	Total	16 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 specific and well-scoped to Bun with strong natural trigger terms, but it lacks an explicit 'Use when...' trigger clause, capping completeness. Distinctiveness is good given the clearly named Bun niche.

Suggestions

Add an explicit 'Use when ...' trigger clause (e.g., 'Use when adopting Bun, migrating Node scripts to Bun, or deploying Bun on Vercel') to lift completeness above 3.

Include common synonym/extension terms (e.g., 'bun.lock', '.ts native execution') to push trigger-term coverage toward 5.

Reframe 'When to choose Bun vs Node, migration notes, and Vercel support' as concrete trigger phrases rather than a topic list.

Dimension	Reasoning	Score
Specificity	Names the Bun domain and lists several concrete capabilities — 'runtime, package manager, bundler, and test runner' plus 'When to choose Bun vs Node, migration notes, and Vercel support' — with only minor coverage gaps, matching the 'several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	The 'what' is clear (Bun as runtime/PM/bundler/test runner), but the 'when' is only weakly implied via the topic phrase 'When to choose Bun vs Node' rather than an explicit 'Use when...' trigger clause; per the rubric, a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Bun', 'Node', 'Vercel') alongside capability keywords ('runtime', 'package manager', 'bundler', 'test runner'), giving good keyword coverage; a few common variations or synonyms are missing, so it sits at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The 'Bun' niche is clearly distinguishable and unlikely to fire for unrelated skills, with only minor overlap risk against a general Node/runtime skill, fitting the 'mostly distinct; minor overlap risk' anchor better than the fully conflict-free 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .agents/skills/bun-runtime/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.