resources

Create and manage Windmill resource files storing credentials and service configurations.

Updated May 28, 2026
One-click install
npx skills add https://github.com/kma-core/windmill --skill resources-kma-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resources
Source: https://github.com/kma-core/windmill/tree/main/system_prompts/auto-generated/skills/resources
Command: npx skills add https://github.com/kma-core/windmill --skill resources-kma-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing credentials and connection configurations for external services in Windmill requires correctly structured resource files, and this Skill provides the exact file formats, schemas, and reference syntax needed to define them without guesswork. ## Core Features & Use Cases - Resource File Creation: Defines {path}.resource.json files with the required value and resource_type fields for services like PostgreSQL, MySQL, Slack, S3, Kafka, NATS, and MQTT. - Variable and Resource References: Supports $var: syntax for referencing global, user, and folder variables, and $res: syntax for referencing other resources, keeping secrets out of plain text. - Custom Resource Types: Creates custom resource type definitions with JSON Schema validation saved as .resource-type.json files. - Use Case: When setting up a new PostgreSQL connection for a Windmill workspace, generate a properly structured f/databases/postgres_prod.resource.json file that references the password via $var:g/all/db_password instead of hardcoding it. ## Quick Start Create a Windmill resource file for a PostgreSQL database that references its password from a global variable.

Frequently Asked Questions about resources

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Windmill resource file for a database?

Create a file named `{path}.resource.json` containing a `value` object with connection fields and a `resource_type` field naming the type, such as "postgresql". Include host, port, user, password, and dbname inside the value object.

How to reference variables in Windmill resource values?

Use the `$var:` prefix followed by the variable path inside resource values. Formats include `$var:g/all/name` for global variables, `$var:u/username/name` for user variables, and `$var:f/folder/name` for folder variables.

What resource types does Windmill support?

Windmill supports common types including postgresql, mysql, slack, s3, http, kafka, nats, and mqtt. You can also define custom resource types with JSON Schema saved as `.resource-type.json` files.

Can Windmill resources reference other resources?

Yes, use the `$res:` prefix followed by the resource path, such as `$res:f/databases/postgres`, inside a resource's value object. This lets one resource embed another resource's configuration.

How do OAuth resources work in Windmill?

OAuth resources are managed through the Windmill UI and marked with `is_oauth: true` and an `account` field. Windmill automatically refreshes OAuth tokens, so no manual token handling is required.

How do I push Windmill resources to a workspace?

Run `wmill sync push` from the CLI to push local resource files to your Windmill workspace. You can also list resources with `wmill resource list` and inspect type schemas with `wmill resource-type list --schema`.