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

53

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/bun-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The skill is highly actionable with concrete, executable examples throughout, but it is a monolithic ~700-line document that exceeds a lean token budget and lacks validation checkpoints for its destructive migration steps. Splitting reference material into separate files and adding verify steps would improve its weaker dimensions.

Suggestions

Split the bulk of the API reference, migration guide, and testing detail into one-level-deep reference files (e.g., BUN_APIS.md, MIGRATION.md) with clearly signaled links from the overview.

Add explicit validation/rollback checkpoints to destructive and batch operations, especially the Node.js migration that runs 'rm -rf node_modules package-lock.json'.

Trim verbosity such as the redundant install methods and the 'Why Bun?' comparison table to reduce the token footprint.

DimensionReasoningScore

Conciseness

The body is roughly 700 lines with padding such as the 'Why Bun?' comparison table, five overlapping install methods, and restated basics Claude already knows; individual sections are mostly efficient, but overall it could be tightened to better respect the token budget.

2 / 3

Actionability

It provides extensive copy-paste-ready, executable commands and complete code examples across installation, project setup, package management, running, built-in APIs, testing, bundling, and migration.

3 / 3

Workflow Clarity

Sections are numbered and the migration flow is sequenced 1-4, but destructive/batch operations like 'rm -rf node_modules package-lock.json' and the compile step have no validation or rollback checkpoints, which caps workflow clarity at 2 per the guidelines.

2 / 3

Progressive Disclosure

All content lives inline in a single ~700-line file with no bundle files and no external references; the API reference, migration guide, and testing sections would benefit from being split into one-level-deep reference files with clear signaling.

2 / 3

Total

9

/

12

Passed

Description

57%

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 clearly identifies the Bun niche and is distinct from other skills, but it lacks concrete capability actions and any explicit 'Use when' trigger guidance. Adding specific verbs and a trigger clause would raise its strongest-weighted dimensions.

Suggestions

Replace the abstract word 'development' with concrete actions, e.g., 'Run, test, bundle, and serve JS/TS apps with the Bun runtime'.

Add an explicit trigger clause such as 'Use when starting new JS/TS projects with Bun or migrating from Node.js to Bun'.

Include common user trigger terms like 'Bun', 'bun test', 'bun build', and 'Node.js to Bun migration' to improve trigger term coverage.

DimensionReasoningScore

Specificity

The phrase 'JavaScript/TypeScript development with the Bun runtime' names the domain but offers no concrete actions (e.g., bundle, test, serve, migrate); it is more than 'Helps with documents' yet not a list of specific actions, so it sits at the middle anchor.

2 / 3

Completeness

It states what the skill covers but provides no 'Use when...' trigger guidance, and the judging guidelines cap completeness at 2 when explicit trigger guidance is missing.

2 / 3

Trigger Term Quality

'JavaScript/TypeScript' and 'Bun runtime' are relevant keywords, but common user variations like 'Bun', 'Node.js migration', 'bun test', or 'bundle' are absent, and 'inspired by oven-sh/bun' is metadata rather than a trigger term.

2 / 3

Distinctiveness Conflict Risk

'Bun runtime' carves out a clear niche distinct from general Node.js/JavaScript skills, making it unlikely to trigger for the wrong skill.

3 / 3

Total

9

/

12

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

skill_md_line_count

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

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
sickn33/antigravity-awesome-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.