Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build automation workflows and internal tools with Windmill's code-first platform.
Build automation workflows and internal tools with Windmill's code-first platform.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Main function signature determines input schema โ Windmill infers from type hints, wrong types break the UI form Return value is the script output โ forgetting to return means downstream steps get nothing Python dependencies go in inline requirements.txt comment โ not a global file, each script is isolated TypeScript runs on Bun โ Node.js-specific APIs may not work
results.step_name fails if step hasn't run yet โ conditional branches cause undefined access errors Parallel branches need explicit configuration โ default is sequential, not concurrent Suspend steps wait forever without timeout โ set explicit timeout or flow hangs indefinitely Error handlers only catch step failures โ script syntax errors bypass handlers
Timezone defaults to server timezone โ set explicitly or jobs fire at unexpected times Concurrent execution allowed by default โ add mutex lock if jobs shouldn't overlap Schedules attach to scripts/flows โ no standalone schedule entities, delete script = delete schedule
Secrets cannot be read back from UI after creation โ store originals securely elsewhere Variables are plaintext and visible โ never put sensitive data in variables, only secrets Path format matters โ u/username/secret for user, f/folder/secret for shared
PostgreSQL is the only state โ workers are stateless, back up only the database Single container includes workers โ fine for small loads, separate workers for scale Worker count determines parallelism โ one worker = one concurrent script execution
Each script/flow gets unique webhook URL โ changes if you rename the script Webhook payload becomes script input โ schema must match expected arguments No built-in auth on webhooks โ validate tokens in script logic or use reverse proxy
Testing flows without testing scripts first โ debug scripts individually Expecting state between runs โ use variables or external storage for persistence Hardcoding paths โ use wmill.get_resource() for portability between workspaces
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.