CtrlK
BlogDocsLog inGet started
Tessl Logo

bun-runtime

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

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

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 body is actionable and well-structured with executable examples throughout, assuming Claude's competence. Its main weakness is workflow clarity, since migration and Vercel deploy guidance lacks explicit validation or verification steps.

Suggestions

Add an explicit validation/verification step to the Vercel deploy sequence (e.g., confirm the build succeeded and the runtime is set before considering the deploy complete).

Tighten the redundancy between the intro line and the "How It Works" list, which both restate Bun's four roles.

For the Node migration flow, add a brief check that `bun install` completed and scripts run before declaring migration success, to introduce a feedback loop.

DimensionReasoningScore

Conciseness

Largely lean with compact code and no over-explanation of JS/Node basics, but the four-role list is repeated in both the intro and the "How It Works" section and could be tightened.

4 / 5

Actionability

Provides copy-paste-ready, fully executable commands and code (bun install/run/test, bun:test, Bun.file, Bun.serve) covering the common cases.

5 / 5

Workflow Clarity

Loose sequences exist (Node migration swaps, Vercel build/install steps) but there are no explicit validation checkpoints or feedback loops for the deploy/migration workflows.

3 / 5

Progressive Disclosure

Well-organized into clear sections (When to Use, How It Works, Examples, Best Practices) and self-contained with no bundle files; the Runtime API snippet could arguably live in a reference file but is small enough inline.

4 / 5

Total

16

/

20

Passed

Description

78%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, well-triggered, and clearly distinct, answering both what Bun does and when to reach for it. It is strong overall, with only minor room to convert role nouns into more explicit action verbs.

DimensionReasoningScore

Specificity

Enumerates concrete capabilities ("runtime, package manager, bundler, and test runner") plus migration notes and Vercel support, but lists roles as nouns rather than explicit actions, leaving minor gaps.

4 / 5

Completeness

Provides a clear "what" (Bun's four tool roles) and an explicit "when" ("When to choose Bun vs Node, migration notes, and Vercel support"), though the trigger guidance could be slightly more specific.

4 / 5

Trigger Term Quality

Includes natural terms users say ("Bun", "Node", "Vercel", "migration") with good coverage, though a few common synonyms/variations are absent.

4 / 5

Distinctiveness Conflict Risk

"Bun" is a distinct named tool with clear niche triggers (Bun vs Node, Vercel runtime), giving minimal conflict risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.