Automate Zero Native
Inspect and drive a running zero-native WebView shell—list windows, snapshot state, reload, and capture screenshots—without manual clicking.
Overview
Automate zero-native is an agent skill for the Ship phase that inspects and controls running zero-native WebView apps through the built-in file-based automation CLI.
Install
npx skills add https://github.com/vercel-labs/zero-native --skill automate-zero-nativeWhat is this skill?
- File-based IPC via `.zig-cache/zero-native-automation/` against a compile-time gated automation server
- CLI commands: list, snapshot, screenshot (optional path), reload via `zig-out/bin/zero-native automate`
- Requires `-Dautomation=true` at build time; builds without the flag ignore automation files
- Screenshot output is a placeholder PPM; DOM interaction is explicitly out of scope
- 4 automate subcommands: list, snapshot, screenshot, reload
Adoption & trust: 4 installs on skills.sh; 4.1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a zero-native WebView app running locally but lack a quick, scriptable way to confirm windows, reload the view, or capture proof it rendered.
Who is it for?
Builders testing zero-native macOS WebView examples who want agent-driven smoke checks without full browser automation.
Skip if: Apps built without `-Dautomation=true`, deep WebView DOM scripting, or teams not using the zero-native Zig stack.
When should I use this skill?
User asks to test the app, list windows, take a screenshot, inspect a snapshot, reload the WebView, or verify a running zero-native example.
What do I get? / Deliverables
You can list automation targets, read snapshots, trigger reloads, and write screenshot artifacts from the CLI after an automation-enabled build.
- Automation snapshot of window and WebView source
- Optional screenshot artifact (placeholder PPM)
- Reload confirmation via automation IPC
Recommended Skills
Journey fit
Commands are for verifying a running native WebView app, which fits shipping and QA more than greenfield ideation. Testing is the canonical shelf for automate list/snapshot/reload/screenshot workflows against a live build.
How it compares
Native shell inspection via Zig CLI—not Playwright-style browser E2E or a hosted device farm.
Common Questions / FAQ
Who is automate-zero-native for?
Solo developers using zero-native who need to test, inspect, and reload running WebView shell apps from the terminal or an agent.
When should I use automate-zero-native?
In Ship (testing) when the user asks to test the app, list windows, snapshot, screenshot, reload, or verify a running zero-native example with automation enabled.
Is automate-zero-native safe to install?
It runs local Zig binaries and writes cache/automation files; review the Security Audits panel on this page and only enable automation on builds you control.
SKILL.md
READMESKILL.md - Automate Zero Native
# Automate zero-native apps zero-native has a built-in automation system for inspecting running WebView shell apps. It works through file-based IPC in `.zig-cache/zero-native-automation/`. ## Prerequisites Run an app with automation enabled: ```bash zig build run-webview -Dplatform=macos -Dautomation=true ``` ## Commands ```bash zig build zig-out/bin/zero-native automate list zig-out/bin/zero-native automate snapshot zig-out/bin/zero-native automate screenshot [path] zig-out/bin/zero-native automate reload ``` ## Workflow 1. Start the app with automation enabled. 2. Run `zig-out/bin/zero-native automate snapshot` to confirm the window and WebView source. 3. Use `zig-out/bin/zero-native automate reload` to request a reload. 4. Use `zig-out/bin/zero-native automate screenshot [path]` when a placeholder screenshot artifact is enough. ## Notes - Automation is compile-time gated: apps built without `-Dautomation=true` ignore automation files. - The current screenshot artifact is a placeholder PPM. - WebView DOM interaction is intentionally out of scope for this file-based automation layer.