CtrlK
BlogDocsLog inGet started
Tessl Logo

pleaseai/bun

All-in-one JavaScript/TypeScript toolkit: fast runtime, package manager, test runner, and bundler. Version-aware skill backed by the ask CLI.

75

Quality

94%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

Highly actionable content with a clear verification workflow and well-structured one-level-deep references to real bundle files. The only weakness is inline, time-sensitive version notes that would read more cleanly and age better in a dedicated 'deprecated/old patterns' section.

Suggestions

Move the per-feature version-gate bullets (1.2.3+, 1.2.0+, 1.2.x, 1.0.24+, etc.) into a dedicated 'Version compatibility / old patterns' section so the main flow stays lean and the time-sensitive data is isolated per the conciseness guideline.

Replace some of the inline version history prose in 'Critical: Do Not Trust Internal Knowledge' with a compact version→feature table to cut tokens while preserving the same guidance.

Consider collapsing the 'Migration Quick Reference' and 'Common Decision Points' tables where they overlap (e.g. test-runner and bundling rows appear in both) to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is mostly lean (tables, bullets, executable blocks, no 'what is Bun' padding), but the 'Critical' section carries many inline time-sensitive version numbers (e.g. 'Bun 1.2.3+', '1.2.0+', '1.0.24+') that the rubric penalizes unless isolated in an 'old patterns'/'deprecated' section.

2 / 3

Actionability

Provides copy-paste-ready commands throughout — the version resolver script, `ask src`/`ask docs` invocations, install commands, `bun --print`, and a migration table mapping each from-tool to an exact Bun command.

3 / 3

Workflow Clarity

The numbered 'When working with Bun' sequence (resolve version → verify against tagged source → cross-reference docs → confirm in REPL → surface trade-offs) is explicit and includes a validation/feedback loop before generating code.

3 / 3

Progressive Disclosure

A clear Topic Map table points to six real one-level-deep reference files plus the resolver script, with an explicit 'do not read all of them upfront' cue and verified-existing linked paths.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states capabilities, provides explicit 'Use when' triggers with natural developer keywords, and carves out a distinct Bun-only niche. It is long but every clause maps to a concrete capability or trigger.

DimensionReasoningScore

Specificity

Names many concrete actions — 'answer questions about Bun', 'write code using its runtime, package manager, test runner, and bundler' — and enumerates specific APIs, modules, CLI commands, config files, and test primitives rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both 'what' (answer questions and write code with Bun's runtime/PM/test runner/bundler) and 'when' via an explicit 'Use when developers call...' clause with enumerated triggers.

3 / 3

Trigger Term Quality

Covers natural terms developers say — 'Bun.serve', 'bun install', 'bunx', 'bun test', 'bun:sqlite', 'migration from npm/yarn/pnpm/jest/vitest' — giving broad coverage of likely user phrasings.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to Bun-specific surfaces (bun:* modules, Bun.* APIs, bunfig.toml, bun.lock) so it is unlikely to trigger for non-Bun skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents