Email Webhook
v2.6.0Receive incoming emails via JSON webhooks and wake the agent. Built for AI Commander.
⭐ 2· 944·5 current·5 all-time
byCoder AI@lksrz
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill's stated purpose (receive emails via JSON webhooks and wake an agent) matches the code's functionality, but the declared registry metadata is incomplete: the runtime actually requires OPENCLAW_AGENT_ID (the server exits if it's missing) and optionally reads OPENCLAW_GATEWAY_TOKEN, yet the registry only lists WEBHOOK_SECRET. The code also invokes the openclaw CLI (expected) and calls openssl to generate a self-signed certificate (openssl is not declared as a required binary). These undeclared requirements are disproportionate to what the registry claims.
Instruction Scope
SKILL.md and the runtime disagree in several places: SKILL.md says the server fires `openclaw system event --mode now`, but the code actually spawns `openclaw agent --agent ... --message ... --deliver`. SKILL.md documents CLOUD/PORT values inconsistently (mentions 2082 then 2083). The runtime writes full email bodies and metadata to a local inbox.jsonl, generates/writes SSL cert files under ../ssl, and performs outgoing network checks (calls api.ipify.org and attempts to fetch its own public IP:port). SKILL.md does not fully document the external network calls or the optional OPENCLAW_GATEWAY_TOKEN usage. While most actions align with the stated purpose, these undocumented/contradictory instructions are scope creep and merit attention.
Install Mechanism
The install spec only adds an npm dependency (express@4.21.2), which is proportional and expected. There are no downloads from arbitrary URLs or extract operations. However, the runtime uses the system openssl binary via execSync to create certificates; openssl is not in the install or required-binaries list, so the environment may fail at runtime unless openssl is present.
Credentials
WEBHOOK_SECRET is a reasonable primary credential. However, the code requires OPENCLAW_AGENT_ID (exit if missing) but this is not declared in the registry metadata; that's a notable mismatch. The code also optionally reads OPENCLAW_GATEWAY_TOKEN and will pass it to the openclaw CLI if present — this is a potentially sensitive token that is not documented in the registry. The number and sensitivity of environment variables (gateway token, agent ID) is higher than the registry declares and should be justified.
Persistence & Privilege
The skill does not request always:true and does not modify other skills. It writes local files (inbox.jsonl and generated SSL files in ../ssl) and spawns the openclaw CLI to notify the agent. Writing its own inbox and certs is expected for a webhook server, but you should be aware it will create files under the server working directory and attempt to open a public port, which has operational and privacy implications.
What to consider before installing
This skill appears to implement an email webhook server, but there are several mismatches you should review before installing:
- Environment variables: the code requires OPENCLAW_AGENT_ID (and optionally OPENCLAW_GATEWAY_TOKEN) but only WEBHOOK_SECRET is declared in the registry. Confirm you are comfortable providing an agent ID and, if used, a gateway token (sensitive) to this process.
- Binaries: the script calls `openssl` to generate a self-signed cert. Ensure openssl is available on the host or the startup will fail; the registry didn't list openssl as required.
- Wake behavior mismatch: SKILL.md says it triggers `openclaw system event`, but the code runs `openclaw agent ... --message ... --deliver`. Verify that this wake mechanism aligns with your expectations and permissions for the agent CLI.
- Network behavior: on startup the server calls an external IP service (api.ipify.org) and attempts to reach back to its public IP:port. This leaks the host's public IP to a third party and probes your port; review whether you accept that behavior.
- Data storage & exposure: incoming emails (raw body and metadata) are appended to a local inbox.jsonl file and a self-signed certificate is stored under ../ssl. Ensure the host filesystem and backups are acceptable places for potentially sensitive email content and that firewall/Cloudflare setup is configured safely.
Recommendation: if you plan to install, (1) request the skill author to update the registry metadata to declare OPENCLAW_AGENT_ID and optional OPENCLAW_GATEWAY_TOKEN and to list openssl as a required binary, (2) audit the openclaw CLI invocation and confirm the gateway token scope, (3) run the server in a restricted environment (dedicated host or container), set a strong WEBHOOK_SECRET, and ensure firewall/Cloudflare settings restrict exposure. If you cannot verify those items, treat the skill as suspicious and do not deploy it on a sensitive/shared host.Like a lobster shell, security has layers — review code before you run it.
latestvk97cms15y8rm3zbasevr4w438981d9cy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsnode, openclaw
EnvWEBHOOK_SECRET
Primary envWEBHOOK_SECRET
Install
Install Webhook dependencies
npm i -g express@4.21.2