What problem does it solve? Managing credentials and connection settings for external services in Windmill requires correctly structured resource files, and hand-writing them risks schema errors, broken variable references, and misconfigured resource types. ## Core Features & Use Cases - Resource File Authoring: Defines the {path}.resource.json format with required value and resource_type fields for services like PostgreSQL, MySQL, Slack, S3, Kafka, NATS, and MQTT. - Variable and Resource References: Supports $var: references to global, user, and folder variables and $res: references to other resources, keeping secrets out of plain configuration. - Custom Resource Types: Creates custom resource types with JSON Schema validation, saved as .resource-type.json files. - Use Case: When adding a new PostgreSQL database connection to a Windmill workspace, generate a f/databases/postgres_prod.resource.json file that references the password via $var:g/all/db_password instead of hardcoding it. ## Quick Start Ask the agent to create a Windmill resource file for a PostgreSQL database that pulls its password from a global variable.
