Launches Windmill dev servers to preview flows, scripts, and apps in a browser or embedder.
npx skills add https://github.com/kma-core/windmill --skill preview-kma-core
Please help me install this Agent Skill. Skill: preview Source: https://github.com/kma-core/windmill/tree/main/system_prompts/auto-generated/skills/preview Command: npx skills add https://github.com/kma-core/windmill --skill preview-kma-core
wmill dev server in the right mode and hands you a working preview URL, handling the differences between browser tabs, IDE preview panes, and MCP-based preview tools. ## Core Features & Use Cases - Mode selection: Chooses between direct mode (remote HTTPS dev page) and proxy mode (localhost URL) based on what the embedder accepts. - Server startup: Spawns wmill dev or wmill app dev in the background and captures the printed URL, or writes a per-target .claude/launch.json entry when an mcp__Claude_Preview__* tool is available. - Non-visual alternative: Runs wmill flow preview or wmill script preview for programmatic job-result testing without deploying. - Use Case: You just wrote a flow at f/test/my_flow and want to see it. The Skill starts wmill dev --path f/test/my_flow --no-open in the background and gives you the dev page URL to open in your browser. ## Quick Start Ask the assistant to preview the flow at f/test/my_flow and it will start the Windmill dev server and return a URL to open.High-intent search queries and answers about installing and using this skill.
Run `wmill dev --path <wmill_path> --no-open` in the background and open the URL it prints. For apps, run `wmill app dev --no-open --port 4000` from the app's `__raw_app` directory and use the printed dev server URL.
Use proxy mode (`--proxy-port <port>`) only when the embedder displaying the preview requires a localhost URL, such as IDE or chat preview panes. Use direct mode for regular browser tabs, where the remote HTTPS dev page loads directly.
Yes. Run `wmill flow preview <path> -d '<args>'` for flows or `wmill script preview <path> -d '<args>'` for scripts. Both print the job result directly and do not deploy anything.
This happens when you construct a `/dev?path=...` URL yourself instead of using `http://localhost:<port>/`. The proxy's root redirect is what appends the workspace ID and auth token, so always use the root URL.
Only when an `mcp__Claude_Preview__*` MCP tool is available in your tool list, since that runtime reads launch.json to start the server. Otherwise nothing reads the file and you should spawn `wmill dev` yourself.
vpzed-devReference Windmill CLI commands for managing scripts, flows, apps, jobs, and workspace resources.
windmill-labsManage Windmill apps, flows, scripts, and resources via the wmill CLI.
vpzed-devLaunches Windmill dev servers to preview flows, scripts, and apps visually.
thenslsRegister NSLS automations in the Automation Tracker and link builders as owners.