CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-bun

MUST use when writing TypeScript scripts. Bun is the default and preferred TypeScript runtime — pick it for TypeScript unless the script specifically needs Deno.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./system_prompts/auto-generated/skills/write-script-bun/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 operational guidance is outstanding — exact commands, executable code, and genuinely thoughtful validation loops (dry-run inspection, lock diffs, intent-based preview/run selection). The skill's structure undermines it: a ~640-line SDK API reference is inlined into SKILL.md with no bundle files at all, bloating every context load with material needed only occasionally.

Suggestions

Move the entire 'TypeScript SDK (windmill-client)' API listing (lines ~200–837) into a references/ file (e.g. references/windmill-client.md), keeping only the import line, the prefer-client-over-fetch rule, and 3–4 most-used helpers inline with a clearly signaled pointer.

Break the dense run-on bullets (e.g. the custom resource-type paragraph) into short scannable rules; each currently packs 4–5 decisions into one sentence.

Consider splitting the CLI/metadata-sync operational sections into their own reference or tightening them, so SKILL.md reads as an overview (structure, resources, preview/deploy intent) with one-level-deep pointers to detail.

DimensionReasoningScore

Conciseness

Roughly 640 of the ~837 lines are an inlined windmill-client SDK API dump ('The full windmill-client API reference (every exported function and its signature) is included below'), material that should live in a references file and be consulted on demand. Some sections are exemplary (preview-vs-run intent rules, metadata sync), but the dense run-on paragraphs (e.g. the custom resource-type bullet) and the reference wall make this noticeably verbose. It is above 1 because most content is non-obvious Windmill-specific fact rather than explanation of concepts Claude already knows, but the sheer padding of the inline reference keeps it at 2.

2 / 5

Actionability

Guidance is fully executable throughout: exact CLI commands with intent-mapped usage ('wmill script preview <script_path>', 'wmill generate-metadata --dry-run', 'wmill generate-metadata f/foo'), copy-paste-ready code for main()/RT/S3 operations, and per-database placeholder syntax ('$1 for PostgreSQL, ? for MySQL/Snowflake, @P1 for MSSQL'). Not score 4: the common cases (structure, resources, client import, S3 read/write) are each covered by concrete runnable examples.

5 / 5

Workflow Clarity

The operate/test/deploy workflow is clearly sequenced with real checkpoints: choose preview vs. run by intent, offer to test after writing, dry-run metadata regeneration to inspect stale items before narrowing, and diff regenerated locks to report dependency version changes. Not 5: the script-authoring half is a collection of principles rather than a sequenced flow with an explicit validate-before-deploy checklist, and validation depends on the model choosing preview; not 3 because validation steps (dry-run, lock diff, preview gating) are explicit and well placed.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), yet the body inlines a ~640-line API reference — a near-verbatim match for the score-2 anchor '[300 lines of API reference that should be in a separate file with no section headers]'. External pointers that do exist (AGENTS.wmill.md, the preview and write-script-bunnative skills, rt.d.ts) are clearly signaled and one level deep, which keeps it above 1, but the failure to split the SDK reference into a separate file dominates the score.

2 / 5

Total

13

/

20

Passed

Description

70%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.

A tight, explicit, well-triggered description whose 'when' clause is a model of clarity. Its weakness is that the stated 'what' captures only the Bun-over-Deno runtime rule, underselling the skill's actual scope as a full Windmill script-writing guide, which also leaves its action list thin.

Suggestions

Expand the 'what' beyond the runtime rule, e.g. 'Write TypeScript (Bun) scripts for Windmill: main() structure, resource-typed parameters, windmill-client usage, S3 operations, and metadata/lock hygiene. MUST use when writing TypeScript scripts — Bun is the default runtime; pick Deno only when the script specifically needs it.'

Add natural trigger variations such as 'TS', '.ts', or 'bun script' to broaden keyword coverage without adding vagueness.

DimensionReasoningScore

Specificity

The description names the domain ('writing TypeScript scripts') and one concrete action/rule ('Bun is the default and preferred TypeScript runtime — pick it for TypeScript unless the script specifically needs Deno'), but coverage is minimal: it conveys only the runtime-selection rule and omits the skill's actual capabilities (script structure, resources, metadata sync, CLI commands). It is above score 2 because it does state a concrete, actionable rule rather than a generic domain label, but below score 4 because there is no list of several specific actions.

3 / 5

Completeness

The 'when' is fully explicit ('MUST use when writing TypeScript scripts'), and a 'what' is present ('Bun is the default and preferred TypeScript runtime — pick it for TypeScript unless the script specifically needs Deno'). It does not reach 5 because the stated 'what' covers only the runtime-preference rule and never conveys what the skill actually delivers (a Windmill TypeScript/Bun script-writing guide), and score 3 is ruled out by the explicit, unmissable use-when clause.

4 / 5

Trigger Term Quality

Natural trigger phrases are present — 'writing TypeScript scripts', 'TypeScript', 'Bun', 'Deno' — which are exactly what a user would say when this skill is needed. It falls short of 5 because common variations like 'TS', 'bun script', or file extensions (.ts) are absent, and it is stronger than 3 because the core phrases are the natural user vocabulary, not jargon.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (TypeScript scripts on Bun vs. Deno) with distinct trigger terms, so it is mostly distinguishable. It does not score 5 because the trigger 'writing TypeScript scripts' fires on all TypeScript script writing — including cases that the companion 'write-script-bunnative' skill (referenced in the body) covers — creating minor overlap risk with closely related skills.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository

windmill-labs/windmill

Path

system_prompts/auto-generated/skills/write-script-bun/SKILL.md

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.