What problem does it solve? Writing Windmill scripts that depend on the Deno runtime requires knowing the correct script structure, import conventions, CLI commands, and metadata synchronization steps, and getting any of these wrong produces stale locks, spurious git diffs, or accidental deploys. ## Core Features & Use Cases - Deno-specific script authoring: Produces scripts exporting an async main function, using npm: prefixed imports, Deno standard library URL imports, and the RT namespace for typed Windmill resources. - Correct CLI workflow: Distinguishes wmill script preview for local iteration from wmill script run for deployed versions, and keeps .lock, .script.yaml, and wmill-lock.yaml in sync via wmill generate-metadata after edits. - Full windmill-client SDK reference: Includes the complete API surface for resources, variables, state, S3 object operations, job orchestration, approvals, and workflow-as-code primitives like step, taskScript, and waitForApproval. - Use Case: A user needs a Windmill script that serves HTTP using deno.land/std; this Skill writes the script, previews it locally with sample args, and regenerates metadata so the lockfile and input schema stay consistent. ## Quick Start Write a Deno TypeScript Windmill script that fetches data from an external API and stores the result in S3, then preview it locally.