bun-runtime

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

87%

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

The body is concise, actionable, and well-organized with copy-paste-ready examples across all of Bun's roles; its only gap is that the migration and deployment sequences lack explicit validation or verification steps.

Suggestions

Add a validation checkpoint to the Vercel flow, e.g. 'After build, verify dist/ contains the expected entry before deploying; re-run with --frozen-lockfile if the lockfile drifts.'

Add a verification step to the Node→Bun migration, e.g. 'Run bun test after migrating to confirm existing tests pass; check for Bun-incompatible packages.'

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward with no concept-bloat (no 'what is a JS runtime' padding); nearly every line is an executable command or a tight factual note, so each token earns its place.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands and code (bun install/run/test, Bun.file/Bun.serve, a complete bun:test example, Vercel build/install commands) with specific flags.	3 / 3
Workflow Clarity	The migration ('replace node with bun', 'bun install', 'bun run/bun x') and Vercel ('set runtime', 'build', 'install --frozen-lockfile') flows are sequenced, but neither includes validation checkpoints or error-recovery feedback loops.	2 / 3
Progressive Disclosure	It is a self-contained, well-sectioned single file (When to Use, How It Works, Examples, Best Practices) with no nested references and no need for external bundle files, so the simple-skill allowance applies.	3 / 3
	Total	11 / 12 Passed

Description

72%

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 distinctive and uses natural trigger terms, but it enumerates capabilities as nouns rather than concrete actions and lacks an explicit 'Use when…' trigger clause, capping completeness and specificity at 2.

Suggestions

Rephrase capabilities as concrete actions, e.g. 'Run, install, bundle, and test JS/TS with Bun; migrate Node projects to Bun; configure Bun on Vercel.'

Add an explicit trigger clause such as 'Use when the user adopts Bun, migrates from Node, or deploys Bun to Vercel.' to lift completeness to 3.

Dimension	Reasoning	Score
Specificity	It enumerates four concrete capabilities ('runtime, package manager, bundler, and test runner') plus scenarios ('choose Bun vs Node, migration notes, and Vercel support'), but phrasings are noun-based rather than concrete action verbs, so it does not reach the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	It states what the skill covers, but the 'When to choose Bun vs Node, migration notes, and Vercel support' clause reads as a topic list rather than an explicit 'Use when the user…' trigger, so per the rubric guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	It surfaces the natural product names a user would actually say ('Bun', 'Node', 'Vercel') alongside 'migration', giving good coverage of likely trigger terms.	3 / 3
Distinctiveness Conflict Risk	The Bun-specific framing (Bun vs Node, migration, Vercel runtime) carves a clear niche unlikely to trigger competing skills.	3 / 3
	Total	10 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 4130457

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.