CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-deno

Use ONLY when a TypeScript script specifically requires the Deno runtime (Deno stdlib or deno.land URL imports). For all other TypeScript, use write-script-bun instead.

Quality

68%

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-deno/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, platform-specific guide with excellent command-level and API-level detail, real validation feedback loops in the metadata-sync workflow, and correct risk gating around deploys. Its weaknesses are repetition of the deploy-gating rule across sections and a monolithic structure that inlines the entire SDK API reference instead of splitting it into a references/ file.

Suggestions

Move the ~640-line 'TypeScript SDK (windmill-client)' API reference into references/windmill-client.md and keep only the most-used helpers (getResource, runScriptByPath, S3 helpers) inline with a clearly signaled pointer.

Consolidate the deploy-gating guidance (repeated in CLI Commands, Preview vs run, and After writing sections) into a single 'Deploying' subsection stated once.

Tighten the very long multi-clause sentences in General Principles into short imperative bullets so each rule is scannable.

DimensionReasoningScore

Conciseness

Mostly efficient platform-specific content Claude cannot know (wmill CLI semantics, windmill-client API, S3 conventions), but the deploy-gating rule is repeated four times ("Only suggest/run a deploy when the user explicitly asks", "Do NOT push... pushing is a deploy", "Only use sync push when the user explicitly asks to deploy", "do it only when the user explicitly asks to deploy/publish/push") and "it is not a deploy" recurs across the metadata sections. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened'; it is not 4 because the duplication is substantial rather than minor, and not 2 because nearly all content is genuinely novel, not concepts Claude already knows.

3 / 5

Actionability

Fully executable guidance throughout: exact commands (`wmill script preview <script_path>`, `wmill generate-metadata --dry-run`, `wmill generate-metadata rehash`, `wmill resource-type list --schema`), complete runnable TypeScript examples (async main, preprocessor event typing, S3 load/write), and copy-paste-ready SDK signatures with usage examples covering the common cases. It cannot exceed 5, and nothing pulls it to 4 since no pseudocode or missing key details were found.

5 / 5

Workflow Clarity

Clear sequences with real validation checkpoints: preview-vs-run is decided by explicit intent rules, and the metadata-sync workflow has genuine feedback loops — `--dry-run` lists stale items with reasons before changing anything, and after regenerating you diff the lock files and report version bumps before deploying. It falls short of 5 because the write-edit-test-deploy workflow is scattered across three overlapping sections (CLI Commands, Preview vs run, Keep metadata in sync) with no single coherent sequence or checklist, leaving minor gaps in how the steps stitch together.

4 / 5

Progressive Disclosure

The body has real section structure, but ~640 lines of the windmill-client SDK API reference are inlined directly in SKILL.md with no bundle files at all (references/, scripts/, assets/ do not exist) — exactly anchor 3's pattern ('content that should be separate is inline', like '200 lines of API reference that could be in a separate file'). It is not 2 because headers and clear section boundaries exist (unlike anchor 2's 'no section headers'), and not 4 because the SDK reference is the bulk of the file and clearly belongs in a one-level-deep reference file.

3 / 5

Total

15

/

20

Passed

Description

51%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 sharply-scoped routing description that excels at when-to-use precision and sibling-skill disambiguation, but entirely omits what the skill does. Adding one clause naming the capability (e.g. writing Windmill scripts in TypeScript on the Deno runtime) would lift specificity and completeness substantially.

Suggestions

State the 'what': lead with what the skill does, e.g. "Writes Windmill scripts in TypeScript for the Deno runtime (npm: imports plus Deno stdlib). Use ONLY when...".

Add natural trigger phrasings users would say, such as "Deno script" or "Deno standard library", to broaden keyword coverage.

Keep the write-script-bun contrast — it is the strongest part of the description.

DimensionReasoningScore

Specificity

The description states no actions at all — it only names the domain ("a TypeScript script specifically requires the Deno runtime") and routing guidance, matching the anchor 'Names the domain but actions are minimal or generic'. It never says what the skill does (e.g. write Windmill Deno scripts), so it cannot reach 3, which requires 1-2 concrete actions; it is above 1 because the domain and scope conditions are concrete, not pure abstraction.

2 / 5

Completeness

Only the 'when' is present ('Use ONLY when a TypeScript script specifically requires the Deno runtime') with no 'what' — the description never states what the skill actually does, exactly matching anchor 2 ('only when is present without what', like 'Use when working with documents'). Not 3 because anchor 3 requires a clear 'what' with weak 'when'; not 1 because the 'when' clause is explicit and specific rather than extremely vague.

2 / 5

Trigger Term Quality

Natural terms users would say are present — "TypeScript", "Deno runtime", "Deno stdlib", "deno.land URL imports" — giving good keyword coverage for this niche, matching 'Good keyword coverage; a few natural terms missing'. It falls short of 5 because it lacks common variations like 'Deno script', 'Deno module', or 'write a script in Deno' phrasing a user might naturally use.

4 / 5

Distinctiveness Conflict Risk

The routing is maximally distinct: 'Use ONLY when a TypeScript script specifically requires the Deno runtime (Deno stdlib or deno.land URL imports). For all other TypeScript, use write-script-bun instead.' explicitly fences this skill off from its nearest sibling skill, giving a clear niche with minimal conflict risk. It cannot be 4 ('minor overlap risk') because the description actively resolves the one overlap that exists.

5 / 5

Total

13

/

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 (839 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

windmill-labs/windmill

Path

system_prompts/auto-generated/skills/write-script-deno/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.