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

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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.

Highly actionable content with strong, well-gated workflows, but it is token-heavy: a massive inlined API reference and repeated deploy disclaimers violate both conciseness and progressive-disclosure principles. Moving the API reference into a separate file would address the two lowest dimensions at once.

Suggestions

Move the ~620-line 'TypeScript SDK (windmill-client)' API reference into a separate file (e.g. references/windmill-client-api.md) and replace it with a one-line pointer plus the handful of most-used helpers; this fixes progressive disclosure and sharply cuts conciseness cost.

State the 'only deploy when the user explicitly asks to deploy/publish/push' rule once in the Deploying section and reference it from the other sections instead of restating it four times (lines 15, 19, 26, 45).

Tighten 'Keep metadata in sync after editing': it currently re-explains the hash-drift mechanism and the offer-vs-run-silently guidance twice; collapse to a single crisp edit→generate-metadata→diff→report sequence.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose: the same deploy-only-when-explicitly-asked rule is restated four times (lines 15, 19, 26, 45) and the 'Keep metadata in sync' prose repeats its points, plus a ~620-line inlined API reference consumes the token budget — padding that could be tightened or moved out. Not a 1 because the prose is not patronizing and the API block is compact signatures rather than concept explanation.	2 / 5
Actionability	Fully executable guidance throughout: copy-paste main/resource/import/preprocessor/S3 code samples, concrete commands (`wmill script preview`, `generate-metadata --dry-run`, `generate-metadata rehash`, `resource-type list --schema`), and exact function signatures covering the common cases. No pseudocode or vague direction.	5 / 5
Workflow Clarity	Clear sequences with real checkpoints — the metadata flow offers a `--dry-run` inspection step, a diff-and-report step to catch unwanted version bumps before deploying, and explicit gating that deploying requires an explicit user request. Stays at 4 rather than 5 because these validations are distributed across prose sections rather than staged as one explicitly-marked validate→fix→retry checklist, and the destructive-deploy guard is stated as a rule rather than a numbered validation step.	4 / 5
Progressive Disclosure	No bundle/reference files exist at all, and the ~620-line windmill-client API reference (lines 174-793) is inlined directly into SKILL.md — the textbook 'content that clearly belongs in separate files is inlined' case. Section headers keep it above a 1, but the complete absence of any one-level-deep reference split leaves it below a 3.	2 / 5
	Total	13 / 20 Passed

Description

73%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 tightly written, highly distinct trigger description that excels at 'when to use' and conflict avoidance but only implies 'what it does'. It is concise, third-person, and free of fluff.

Dimension	Reasoning	Score
Specificity	Names the domain ('TypeScript script specifically requires the Deno runtime') and concrete technical signals ('Deno stdlib or deno.land URL imports'), but states a selection criterion rather than listing the actions the skill performs (write/edit/run), so it is not the multiple-concrete-actions of a 4.	3 / 5
Completeness	The 'when' is explicit and strong ('Use ONLY when ... requires the Deno runtime', plus the 'use write-script-bun instead' exclusion), but the 'what' is only implied (it never says 'write/create Deno TypeScript scripts'), so it does not clearly and explicitly answer both what and when as a 5 requires.	4 / 5
Trigger Term Quality	Good natural-term coverage — 'TypeScript', 'Deno runtime', 'Deno stdlib', 'deno.land URL imports' are phrases a developer would say — but a few natural variations (e.g. 'Deno script', '.ts') are absent, stopping short of the comprehensive synonym/extension coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	A clear narrow niche (Deno-runtime-only TypeScript) with an explicit disambiguating exclusion ('For all other TypeScript, use write-script-bun instead'), giving minimal conflict risk with the sibling Bun skill.	5 / 5
	Total	16 / 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 (793 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
Commit: 7915540

Reviewed: 3 days 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.