CtrlK
BlogDocsLog inGet started
Tessl Logo

bun-development

Fast, modern JavaScript/TypeScript development with the Bun runtime, inspired by [oven-sh/bun](https://github.com/oven-sh/bun).

35

Quality

32%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills-claude/skills/bun-development/SKILL.md

The canonical home for this skill is bun-development in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

42%Scale 1-3

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

This skill is essentially a comprehensive Bun reference manual crammed into a single SKILL.md, which makes it highly actionable with excellent executable examples but severely bloated for a skill file. It explains many things Claude already knows (what environment variables are, basic test matchers, why faster is better) and fails to organize content into separate files for progressive disclosure. The migration workflow lacks validation checkpoints.

Suggestions

Reduce content by 60-70%: remove the comparison table, performance explanations, exhaustive matcher lists, and Node.js compatibility details that Claude already knows. Focus on Bun-specific APIs and gotchas only.

Split into multiple files: move detailed API references (SQLite, WebSocket, testing matchers, bundler API) into separate referenced files like TESTING.md, APIS.md, BUNDLING.md, and keep SKILL.md as a concise overview with quick-start examples.

Add validation checkpoints to the migration workflow: e.g., 'Run `bun test` to verify tests pass after migration' and 'Run `bun run dev` to confirm the app starts correctly'.

Remove the 'When to Use This Skill' section and 'Limitations' boilerplate — these consume tokens without adding actionable value for Claude.

DimensionReasoningScore

Conciseness

Extremely verbose at ~500+ lines. Includes extensive content Claude already knows: comparison tables (Node vs Bun), basic concepts like what environment variables are, exhaustive matcher lists, full tsconfig explanations, and Node.js compatibility details. The 'Why Bun?' table, migration compatibility section, and performance tips explaining why native APIs are faster are all unnecessary padding for Claude.

1 / 3

Actionability

Nearly all guidance is concrete and executable: real bash commands, complete TypeScript code examples for servers/SQLite/testing/bundling, specific package.json and tsconfig.json configurations, and copy-paste ready CLI commands. Code examples are complete and runnable.

3 / 3

Workflow Clarity

The migration section (8.2) provides a numbered sequence but lacks validation checkpoints — no step to verify the migration worked, test that packages installed correctly, or validate that the app runs. Project setup is clear but presented as reference material rather than a guided workflow with verification steps.

2 / 3

Progressive Disclosure

Monolithic wall of text with no bundle files to offload content. All 9 major sections with extensive subsections are inlined into a single file. The SQLite API reference, full matcher documentation, WebSocket examples, bundler API, and migration guide could all be separate referenced files. The Resources section links to external docs but doesn't structure the skill's own content across files.

1 / 3

Total

7

/

12

Passed

Description

22%Scale 1-3

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 too vague and lacks concrete actions, explicit trigger guidance, and a 'Use when...' clause. While it names the Bun runtime which provides some distinctiveness, it reads more like a tagline than a functional skill description that would help Claude select it appropriately from a large skill set.

Suggestions

Add a 'Use when...' clause specifying triggers like 'when the user mentions Bun, bun.sh, bunx, or wants to use Bun as a runtime, package manager, or bundler'.

List specific concrete actions such as 'Run scripts with Bun, manage packages with bun install, bundle code, execute tests with bun test, and scaffold projects with bun init'.

Differentiate from Node.js/Deno skills by explicitly stating what makes Bun-specific development unique (e.g., 'Bun-native APIs, Bun.serve, bun:test, bunfig.toml configuration').

DimensionReasoningScore

Specificity

The description says 'JavaScript/TypeScript development with the Bun runtime' but does not list any concrete actions like 'run scripts', 'install packages', 'bundle code', or 'test'. It names a domain but no specific capabilities.

1 / 3

Completeness

The description partially addresses 'what' (JavaScript/TypeScript development with Bun) but is vague, and there is no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.

1 / 3

Trigger Term Quality

It includes relevant keywords like 'JavaScript', 'TypeScript', 'Bun runtime', and 'Bun' which users might naturally mention. However, it misses common variations and related terms like 'bun install', 'bun run', 'bunx', 'package manager', 'bundler', or '.ts files'.

2 / 3

Distinctiveness Conflict Risk

Mentioning 'Bun runtime' specifically helps distinguish it from generic JS/TS skills, but 'JavaScript/TypeScript development' is broad enough to overlap with Node.js, Deno, or general JS/TS coding skills.

2 / 3

Total

6

/

12

Passed

Validation

81%

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

Validation — 9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (702 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Repository
popey/claude-code-skills
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.