ziniao-assistant

Control Ziniao Browser via the local Ziniao bridge. On skill load or before first invoke, GET /zclaw/tools and treat returned name list as the only allowed t...

This skill appears to do what it says (talk to a local Ziniao bridge), but the SKILL.md expects an API key and a local config file while the registry metadata declares none — that's the main inconsistency. Before installing: - Confirm whether the skill actually needs ZCLAW_API_KEY and whether that key will be read from an env var or from ~/.zclaw/config.json. If so, the metadata should list that config path and env var. - Understand that the skill will call localhost (default http://127.0.0.1:9481). Only install if you trust the local bridge running there — a compromised local service could misuse the skill's ability to invoke tools or accept posted data. - Ask the publisher to update metadata to declare required env vars/config paths, and to document exactly what information is read from ~/.zclaw/config.json. Prefer explicit declared requirements over implicit file reads. - Consider running the agent in a restricted environment (or without the API key) until you confirm behavior. If you must provide ZCLAW_API_KEY, store it securely and consider limiting its privileges. - If you are uncomfortable with the skill reading a file in your home directory or with the documented operations (download_file, get_logs, write-to-Downloads), do not install until the publisher clarifies and the metadata is corrected.

Type: OpenClaw Skill Name: ziniao-assistant Version: 1.0.1 The skill provides extensive browser automation capabilities via a local bridge (defaulting to 127.0.0.1:9481), including executing JavaScript (execute_script) and downloading files (download_file). It also instructs the agent to read and write API keys to a configuration file in the user's home directory (~/.zclaw/config.json). While these actions are aligned with the stated purpose of controlling the Ziniao Browser and include safety constraints like tool allowlisting and 'Stop on Blocker' logic, the combination of filesystem modification and broad browser control constitutes a high-risk capability set.