gateway-notify
v1.0.5Set up automatic notifications when OpenClaw gateway restarts. Use when user wants to be notified of gateway startup events via any messaging channel (iMessa...
⭐ 1· 613·7 current·7 all-time
byDeemo@deemoartisan
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (notify on gateway startup) align with the files and script. The setup script only creates a hook under ~/.openclaw/hooks/gateway-restart-notify, generates HOOK.md and handler.ts, enables the hook, and asks the user to restart the gateway. No unrelated cloud credentials or global config paths are requested.
Instruction Scope
SKILL.md and setup script stay within the described scope: they write to the skill's hook directory, enable the hook, and the handler only collects timestamp and a hardcoded port. The handler executes external CLI commands (imsg, wacli, openclaw message) to send notifications — this is expected for a notification skill but means the skill will invoke local binaries. The script performs input validation and attempts to escape single quotes before embedding the address into handler.ts.
Install Mechanism
Instruction-only skill with no install spec; the only code written to disk is created by the provided setup script in the user's home directory. No remote downloads or archive extraction are performed by the skill itself.
Credentials
No environment variables, secrets, or external credentials are requested. The messaging address is provided by the user at setup. The handler does not read OpenClaw config files (project changelog/SECURITY.md explicitly documents removal of config reads).
Persistence & Privilege
The skill does not request always: true and does not modify other skills. It enables a hook via the OpenClaw CLI (openclaw hooks enable) which is the expected mechanism for registering event handlers.
Assessment
This skill appears coherent with its purpose. Before installing: (1) inspect scripts/setup_gateway_notify.sh yourself — it creates files under ~/.openclaw/hooks and writes handler.ts; (2) ensure the messaging CLIs it will call (imsg, wacli, openclaw message) are the official/trusted binaries on your system — a malicious replacement binary with one of those names could be invoked; (3) optionally open the generated handler.ts after running the setup script to confirm the embedded address and command look correct; (4) if you are concerned about command injection, test with a dummy address and review the SAFE_ADDRESS escaping in the setup script. No extra credentials are requested by this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk976vxsyt5bppst61gzg9gfyhd82kq6d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.