Openclaw Web Automation

Automates web interactions for public site checks or authenticated flows with credential references and optional iMessage notifications.

This skill is coherent with a web-automation purpose, but exercise caution before installing or running it: - Audit and run in an isolated environment: `pip install -e .` can execute project build hooks and will import local code. Use a disposable virtualenv or container before trusting it on a workstation with sensitive data. - Inspect the full OpenClaw Automation Kit code (especially openclaw_automation.cli, AutomationEngine, and parse_query_to_run) before use — the runner delegates runtime behavior to those modules and they could run arbitrary scripts or access local files. - Be aware of repo-root discovery: the script searches the current working directory and parents for a manifest; running it from an unexpected directory could cause it to pick up and execute a different automation repo. - Network access is unrestricted (network_domains: ["*"]). If you need strict boundaries, run the skill in a network-restricted sandbox. - Do not provide credentials to this skill: although SKILL.md says no credentials are required, nothing in the code enforces that at runtime. If you need login-required checks, obtain a clearly scoped skill that explicitly requires and documents those credentials. If you want to proceed safely: review the automation package source code, run the skill only in a sandboxed environment, and set OPENCLAW_AUTOMATION_ROOT explicitly to the intended repository path before invoking.

Type: OpenClaw Skill Name: openclaw-web-automation Version: 1.0.7 The skill bundle is classified as benign. The `SKILL.md` instructions do not contain any prompt injection attempts, and the `scripts/run_query.py` script safely handles user input by passing arguments as a list to `subprocess.run`, preventing shell injection. The `runner.py` entrypoint delegates core functionality to the `openclaw_automation` library, which is a standard practice for platform skills. While `manifest.json` grants broad `network_domains: ["*"]` permissions, this is necessary for its stated purpose of "public-site automation" against arbitrary websites, and there is no code within the provided files that indicates an intent to misuse this permission for data exfiltration or other malicious activities.