tdg-personal/bun-runtime
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
65
65%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
50%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 identifies Bun's key roles and touches on comparison/migration topics, giving a reasonable sense of scope. However, it lacks an explicit 'Use when...' clause, doesn't list concrete actions Claude would perform, and misses several natural trigger terms users might use. It reads more like a topic summary than a skill selection guide.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Bun, wants to migrate from Node to Bun, or needs help configuring Bun as a runtime, bundler, or test runner.'
List concrete actions such as 'Configure Bun projects, migrate package.json scripts from Node, set up bun test suites, troubleshoot Bun on Vercel deployments.'
Include additional natural trigger terms like 'bun install', 'bun run', 'bunx', 'bun.lockb', 'switch from npm/yarn to Bun'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Bun) and lists roles (runtime, package manager, bundler, test runner) plus some topics (migration notes, Vercel support), but doesn't describe concrete actions like 'configure Bun projects', 'migrate from Node to Bun', or 'set up Bun test suites'. | 2 / 3 |
Completeness | The 'what' is partially covered (Bun's roles and comparison topics), but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Bun', 'Node', 'runtime', 'package manager', 'bundler', 'test runner', 'Vercel', and 'migration', but misses common user phrases like 'bun install', 'bun run', 'switch from Node', '.bunfig', or 'bun.lockb'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Bun' specifically helps distinguish it, but terms like 'runtime', 'package manager', 'bundler', and 'test runner' could overlap with Node.js or other JavaScript tooling skills without clearer scoping. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid reference skill with good executable examples and concrete migration guidance. The main weaknesses are some unnecessary explanatory text that Claude doesn't need, and the lack of structured workflows with validation checkpoints for deployment scenarios. The content would benefit from tighter prose and clearer sequencing for multi-step operations like Vercel deployment.
Suggestions
Trim the introductory and 'How It Works' sections—remove explanations of what Bun is (JavaScriptCore, Zig, etc.) and focus only on actionable differences from Node.
Add a sequenced Vercel deployment workflow with explicit validation steps (e.g., verify build output, check runtime setting, test locally with `bun run build` before deploying).
Consider splitting Vercel deployment and runtime API into referenced sub-files if the skill grows, to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary explanation Claude already knows (e.g., 'Bun is a fast all-in-one JavaScript runtime and toolkit', explaining what JavaScriptCore and Zig are, 'Drop-in Node-compatible runtime'). The 'How It Works' section has some padding that could be trimmed. | 2 / 3 |
Actionability | Provides fully executable bash commands and TypeScript code examples that are copy-paste ready, including install, run, test, env handling, file API, and server setup. Migration steps are concrete with specific command replacements. | 3 / 3 |
Workflow Clarity | The skill covers multiple tasks (migration, Vercel deployment, testing) but presents them as flat descriptions rather than sequenced workflows. The Vercel deployment section lacks validation steps (e.g., verifying the build succeeded, checking runtime configuration). For a skill that's more reference than multi-step process, this is adequate but not exemplary. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in a single file. The Vercel deployment details, runtime API examples, and testing could be split into referenced files. For the length (~70 lines of content), it's borderline acceptable but slightly monolithic. | 2 / 3 |
Total | 9 / 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 | |
Reviewed
Table of Contents