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

47

Quality

50%

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 ./skills/bun-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 a well-structured, token-efficient overview that cleanly offloads detail to one real reference file, but it sacrifices in-body actionability and workflow sequencing by delegating nearly everything to the guide.

Suggestions

Add a minimal quick-start snippet (e.g. `bun init` / `bun run`) so the body has at least one concrete executable step.

Inline a brief high-level workflow with an explicit validation checkpoint rather than only referencing it as mandatory.

Drop the redundant blockquote that repeats the frontmatter description to tighten the opening.

DimensionReasoningScore

Conciseness

The body is lean and mostly navigation, but the blockquote duplicates the description and the Detailed Guide paragraph carries mild padding ("It retains the complete procedure and reference material").

4 / 5

Actionability

The body provides only high-level pointers ("Read the detailed guide") and a use-case list; no concrete code, commands, or executable steps appear in the body itself.

2 / 5

Workflow Clarity

No sequenced workflow appears in the body; steps are delegated to the reference, and while validation is mentioned as mandatory, no checkpoints or sequence are shown inline.

2 / 5

Progressive Disclosure

A clear overview points to a single, well-signaled one-level-deep reference (references/detailed-guide.md, which exists), with content appropriately split and easy navigation.

5 / 5

Total

13

/

20

Passed

Description

48%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 conveys a clear domain and distinct runtime niche but lacks concrete actions and any explicit use-when trigger guidance, leaving it generic on actionability and timing.

Suggestions

Add concrete actions, e.g. "bundle, test, and run JS/TS projects with Bun".

Append an explicit trigger clause such as "Use when starting or migrating JS/TS projects to the Bun runtime".

Include natural user phrasings and synonyms (e.g. "Bun", "Bun runtime", ".bun", "Node.js migration") for stronger trigger terms.

DimensionReasoningScore

Specificity

Names the domain ("JavaScript/TypeScript development with the Bun runtime") but offers no concrete actions like bundling, testing, or migrating; "development" is generic.

2 / 5

Completeness

States a clear "what" (Bun-based JS/TS development) but provides no explicit "when/Use when" guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes relevant keywords ("Bun runtime", "JavaScript/TypeScript") but lacks natural user phrasings and synonyms a person would say, and omits a "Use when" trigger.

3 / 5

Distinctiveness Conflict Risk

Bun-specific framing is a fairly distinct niche, though "JavaScript/TypeScript development" broadly overlaps with general Node.js skills, leaving minor conflict risk.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

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