Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
What Just Happened
v1.1.0When the gateway comes back online, check recent logs and post a short message about what happened (restart, SIGUSR1, auth change, reconnect). User sees the...
⭐ 0· 267·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the code: scripts probe the local gateway, read OpenClaw gateway logs (and optional workspace .overstory logs), summarize recent restarts/reloads, and invoke the OpenClaw CLI to deliver messages. One minor inconsistency: the install script expects a LaunchAgent plist file (com.openclaw.what-just-happened.plist) under scripts/, but that plist file is not present in the manifest — installing via the provided script will fail unless the plist is added. Otherwise the requested operations (reading logs, calling openclaw agent --deliver, installing a local watcher) are appropriate for the described purpose.
Instruction Scope
SKILL.md and the scripts confine actions to the stated task: they probe 127.0.0.1 on the gateway port, read files under OPENCLAW_HOME/logs and optional workspace .overstory/logs, and call the local openclaw CLI to deliver messages. There are no calls to external URLs or hidden endpoints in the code. The watcher writes a small state file under OPENCLAW_HOME/logs and attempts to run the openclaw CLI; it does not read unrelated system files or environment secrets beyond OpenClaw-related paths.
Install Mechanism
This is an instruction-only skill (no remote downloads), but the included install script modifies the user's environment by writing a LaunchAgent into ~/Library/LaunchAgents and loading it with launchctl. That is expected for a persistent watcher but is a privileged change the user must approve. The install script uses only local files (no remote fetch); however, as noted above, the expected plist source file is not present in the package, so the install script will exit early unless the user provides the plist.
Credentials
The skill declares no required env vars, but the code relies on OPENCLAW_HOME (with a sensible default ~/.openclaw), optionally OPENCLAW_BIN, and may look for OVERCLAW_WORKSPACE / OPENCLAW_WORKSPACE / WORKSPACE when locating .overstory logs. Those environment variables are proportional to the skill's function. The scripts do not request unrelated credentials, and they do not appear to read gateway.auth or other secret files directly (they only search logs).
Persistence & Privilege
The skill is not always:true and is user-invocable by default. Persistent behavior only occurs if the user explicitly runs the install script, which installs and loads a LaunchAgent that runs every 15s. That persistent watcher will autonomously trigger the OpenClaw agent to deliver messages when the gateway goes from down→up. This is expected for the feature but increases blast radius (the service will run in the background and cause outbound deliveries via the configured OpenClaw channels).
Assessment
This package appears to do what it says: watch the local gateway, scan recent gateway logs, and announce a short summary via the OpenClaw delivery mechanism. Before installing, review and consider the following: (1) installing the watcher will write and load a LaunchAgent in ~/Library/LaunchAgents and run every 15s — only run the install script if you want that persistent background process; (2) the install script references a plist (com.openclaw.what-just-happened.plist) which is not included in the manifest — the install will fail unless you provide or obtain that plist; (3) the watcher will call your local openclaw CLI to deliver messages, so confirm openclaw is the expected binary and properly configured (it will deliver to whichever channels OpenClaw is configured for, e.g., Telegram — check that log snippets are acceptable to post); (4) logs can contain sensitive information, so inspect the log-snippet selection logic if you are concerned about accidentally posting secrets; (5) if you prefer not to run a persistent LaunchAgent, use the cron/manual invocation option instead. Overall the package is coherent with its stated purpose; exercise normal caution when enabling background services and automatic deliveries.Like a lobster shell, security has layers — review code before you run it.
latestvk971npawzccmwk6b1wp7v9r06h82her2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.