cli-commandsUse when running `wmill` CLI commands — `script preview/run`, `flow run`, `job get/list/logs`, `workspace`, `version`. Triggers on "run the script", "check the job", "preview vs run", inspecting failures via `wmill job`, "wmill generate-metadata no scripts found", "wmill bootstrap", "wmill --workspa
previewMUST use when opening the Windmill dev page / visual preview of a flow, script, or app. Triggers on words like preview, open, navigate to, visualize, see the flow/app/script, and after writing a flow/script/app for visual verification.
raw-appUse when creating a Windmill **raw app** — single-file HTML/JS UI served from Windmill, not a low-code App Editor app. Triggers on "raw app", "html app in windmill", "single-page app on windmill", custom JS dashboards. NOT for: low-code App Editor apps, flow construction (use write-flow).
resourcesUse when creating, reading, or wiring a Windmill **resource** — typed credential/connection (DB, API, S3, OAuth) stored in the workspace and referenced from scripts/flows. Triggers on "add a resource", "database credentials in windmill", "resource type", `.resource.yaml`, `.resource-type.yaml`, "cha
schedulesUse when configuring a Windmill **schedule** — cron-based or interval trigger that runs a script/flow on a timer. Triggers on "schedule a script", "run every X minutes", "cron in windmill", `.schedule.yaml`, "schedule churns on every push", "perpetual ~ modify diff", "email field reverts", "cron_ver
triggersUse when configuring a Windmill **trigger** — HTTP route, webhook, WebSocket, Postgres CDC, MQTT, or SQS entry point that invokes a script or flow on Hallow's customized-OSS Windmill. Triggers on "webhook in windmill", "http route", "sqs trigger", "websocket trigger", "postgres cdc", `.trigger.yaml`
windmill-aclUse when granting, revoking, or auditing **item-level access** on an existing Windmill entity — narrower than its containing folder's default ACL. Triggers on "who can access this resource", "give X write access to Y", "share this script with just", "narrow this to just the finance team", "revoke ac
windmill-askFront door for any QUESTION about Hallow's self-hosted Windmill — how it works, how to do something, why something behaves a certain way, or where the docs are. Triggers whenever the user mentions windmill, wmill, or windmill.platform.hallow.app and is ASKING rather than requesting a build/debug/set
windmill-buildHelps any Hallow team member get something done on the self-hosted Windmill instance — and first decides whether a tool even needs to be built. Triggers when the user wants to automate something, build a tool, make a button, send themselves a Slack when something happens, run a thing on a schedule,
windmill-capture-learningCapture a Windmill behavior, gotcha, or plugin-doc-contradiction discovered during development. Writes both a memory entry (tag windmill-plugin-update) and a scratchpad bullet in WINDMILL_LEARNINGS.md. Use after any session where Windmill behavior surprised you, a doc was wrong, or a CLI/API quirk n
windmill-debugDiagnoses Windmill tool failures in plain language. Triggers when the user says their script/flow/app failed, errored, crashed, didn't run, returned nothing, hung, timed out, ran but did the wrong thing, "my tool is broken", "Windmill is throwing an error", "the job failed", "nothing happens when I
windmill-discoverCatalogs existing Windmill tools so users can reuse instead of rebuild — and flags when no tool is needed at all. Triggers when the user asks what tools exist, what's already built, is there something that does X, does anyone have a script for Y, what's in the toolbox, "show me available tools", "li
windmill-onboardingReference and discovery skill for Hallow's Windmill onboarding. Loads when a new engineer says they want to set up Windmill, install wmill, connect to windmill.platform.hallow.app, mint a Windmill token, configure the Windmill MCP, get started with Hallow's Windmill instance, or asks any "I'm new an
windmill-patternsReference skill for Hallow Windmill usage and development patterns. Loads when an engineer is creating or modifying a Windmill script, flow, app, trigger, schedule, or resource in the Hallow `dev` workspace, asking about shared atoms (slack_post, error_to_slack, assert_principal), the `f/platform_se
write-flowUse when creating a Windmill **flow** — multi-step orchestration of scripts via `flow.yaml`, with branches, loops, suspends, approvals, error handlers. Triggers on "build a flow", "chain scripts", "windmill workflow", `flow.yaml`, "tag fargate", "S3 step in flow", "AccessDenied cyclic structures", "
write-script-bunUse when writing a Windmill TypeScript script on the **Bun runtime** with full npm ecosystem and `windmill-client` available. Default TS choice for fastest execution + npm imports (Hallow's primary script language, 63+ in production). Triggers on "windmill ts script", "bun script", uses `import` fro
write-script-duckdbUse when writing a Windmill DuckDB script — in-process analytical SQL via the `duckdb` runtime. Triggers on "duckdb query", local-file analytics, CSV/Parquet inspection, "DuckLake catalog", "ATTACH ducklake", "duckdb $name bind", "duckdb %%name%% literal substitution", "DuckDB rejected bucket name w
write-script-postgresqlUse when writing a Windmill PostgreSQL script — SQL targeting Postgres via the `postgresql` runtime. Triggers on "postgres query", "pg script", `RETURNING *`, `::jsonb`, `$1` param markers. Covers parameter binding, resource auth, and JSONB handling.
write-script-python3Use when writing a Windmill Python script (`.py`, python3 runtime). Triggers on "python script in windmill", `def main(...)`, `import wmill`, pip requirements in script header. Covers main signature, wmill SDK usage, dependency pinning, and wmill CLI lifecycle.
write-workflow-as-codeUse when writing or modifying a Windmill **Workflow-as-Code** (WAC) script — TS/Python scripts that orchestrate steps using `@workflow`, `@task`, `step`, `sleep`, `task_script`, `task_flow` decorators instead of `flow.yaml`. Triggers on `workflow()`, `@task`, `taskScript(...)`, `task_flow(...)`, che