What problem does it solve? Writing PostgreSQL scripts for Windmill requires knowing the platform's parameter binding syntax, metadata regeneration workflow, and the correct CLI commands for previewing versus deploying — mistakes here cause stale locks, spurious git diffs, or accidental deploys of untested code. ## Core Features & Use Cases - Parameterized SQL scripts: Bind arguments with $1::{type} placeholders and named comment headers, including S3Object parameters decoded via jsonb_to_recordset. - Correct CLI workflow: Distinguishes wmill script preview (local iteration) from wmill script run (deployed version) and wmill generate-metadata (lock/schema sync), preventing accidental deploys. - Result streaming to S3: Streams large query result sets directly to S3 in JSON, Parquet, or CSV format using the -- s3 directive. - Use Case: You need a Windmill script that queries a users table by name and age. The Skill produces the correctly parameterized SQL, then previews it locally with sample arguments before any deploy. ## Quick Start Write a Windmill PostgreSQL script that selects users by name and age, then preview it locally with sample arguments.