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

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

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

Highly actionable with a well-sequenced, guarded workflow, but its token efficiency suffers from a massive inlined SDK reference and padded prose, and its progressive disclosure is undermined by keeping that reference inline rather than in a separate file.

Suggestions

Move the ~600-line windmill-client SDK signature block into a separate `references/windmill-client-api.md` and link to it from SKILL.md to improve both conciseness and progressive disclosure.

Tighten the 'Keep metadata in sync' and 'After writing' prose by trimming inferred rationale (e.g. why pushing-to-test is bad) to the essential rule and the command.

If the SDK reference must stay inline, add a short navigational table of contents at the top of that section so callers can jump to the relevant helper instead of scanning 600 lines.

Dimension	Reasoning	Score
Conciseness	The ~600-line verbatim windmill-client SDK signature block is inlined directly into SKILL.md and competes heavily with context, and several metadata-sync prose blocks are padded with rationale Claude can infer, landing 'noticeably verbose' rather than merely 'could be tightened'.	2 / 5
Actionability	Concrete commands (`wmill script preview <path>`, `wmill generate-metadata --dry-run`, `wmill resource-type list --schema`), complete executable code samples, and full typed API signatures make the guidance copy-paste ready across the common cases.	5 / 5
Workflow Clarity	The write -> sync-metadata -> preview -> deploy-only-on-explicit-request sequence is clear with explicit guardrails and checkpoints (`--dry-run` to inspect stale items, diff `.lock` files to report dependency bumps before deploy, preview validates before deploy), with only minor validation gaps keeping it off the top anchor.	4 / 5
Progressive Disclosure	Section headers and inline signals to `AGENTS.wmill.md` and sibling skills give some structure, but no bundle files exist and the large SDK API reference is inlined in SKILL.md rather than split into a separate one-level-deep reference file, fitting the 'structure present but content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

82%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 focused, well-voiced (third person) description that clearly states the trigger and the runtime-selection rule with low conflict risk. Its only weak spot is specificity, since it states one decision rule rather than enumerating several concrete capabilities.

Dimension	Reasoning	Score
Specificity	It names the domain (TypeScript scripts, Bun runtime) and a concrete decision rule ('pick it for TypeScript unless the script specifically needs Deno'), but does not enumerate several specific actions, matching the '1-2 concrete actions' anchor rather than the 'lists several specific actions' level above.	3 / 5
Completeness	It explicitly answers both 'what' (use Bun as the default/preferred TypeScript runtime) and 'when' ('MUST use when writing TypeScript scripts') with a concrete trigger phrase, matching the top anchor.	5 / 5
Trigger Term Quality	Natural user-facing terms like 'writing TypeScript scripts', 'Bun', 'Deno', and 'TypeScript runtime' are present and would plausibly be said, but lighter on synonyms/extensions (e.g. 'TS', '.ts'), fitting the 'good coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	The 'MUST use when writing TypeScript scripts' trigger plus the specific Bun/Deno runtime niche gives it a clear, low-conflict scope unlikely to fire for unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (783 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
Commit: 74af4ed

Reviewed: about 19 hours ago

Table of Contents

Discovery Implementation Validation

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.