Bee Push Email
v1.5.3Monitors email in real-time via IMAP IDLE and triggers the OpenClaw agent to notify users through active channels like Telegram or Discord.
⭐ 2· 186·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill's files and installer implement IMAP IDLE watching, use himalaya/imapclient to read messages, and trigger the OpenClaw agent and Telegram bot commands — all of which are consistent with 'Bee Push Email' functionality. The installer creates a non-root system user, venv, systemd unit, and uses the openclaw CLI as described. Note: registry metadata shown to you (no required binaries/env) does not match the SKILL.md and included installer scripts; the SKILL.md frontmatter and packaged scripts are where the real requirements live.
Instruction Scope
Runtime instructions and scripts perform root-level installation steps (useradd, writing /opt, /etc/systemd/system, /usr/local/bin), read local OpenClaw configuration files to find a Telegram bot token and gateway token, and call external endpoints (api.telegram.org and GitHub releases). These actions are within the skill's stated scope but are sensitive (see credential notes). The SKILL.md explicitly requires user consent before install which is appropriate.
Install Mechanism
There is no remote arbitrary install spec in the registry, but the packaged installer will optionally download the himalaya binary from GitHub Releases using 'curl | tar' into /usr/local/bin. GitHub releases is a known host (lower risk than unknown servers) but curl|tar extraction into system binary paths is moderately risky and requires root; the rest of the code is bundled with the skill so no other external code downloads are performed.
Credentials
The skill requires IMAP credentials (expected) and reads OpenClaw configuration to locate a Telegram bot token (used to register bot commands) and an OpenClaw gateway token. Reading the bot token is reasonable for registering commands and the bot token is not stored by the skill, but the installer will store the OpenClaw gateway token into /opt/imap-watcher/watcher.conf (chmod 600) so the non-root service can call 'openclaw agent --deliver'. Persistently storing that gateway token expands the service's long-term access to the user's OpenClaw gateway and is a sensitive and material permission — the user must consent and consider rotating or restricting the token scope if possible.
Persistence & Privilege
The skill installs a persistent systemd service that runs on boot as a dedicated non-root 'imap-watcher' user and restarts automatically. This persistence is required for continuous IMAP IDLE functionality and is coherent with purpose, but it is a lasting system-level presence and therefore higher-privilege (requires root to install). The SKILL.md instructs obtaining explicit user approval before installation, which is appropriate.
Assessment
What to consider before installing:
- This skill performs a system-wide install (creates /opt/imap-watcher, a systemd unit at /etc/systemd/system/, and a system user) and requires root to run the installer — only install on machines you control and trust.
- You will need to provide IMAP credentials (email + password or app-specific password) at install time — use an app-specific password where possible.
- The installer will attempt to read your OpenClaw configuration to obtain a Telegram bot token (used only to register bot commands) and a gateway token. The bot token is read but not stored; the OpenClaw gateway token may be written to /opt/imap-watcher/watcher.conf (chmod 600) so the non-root service can call 'openclaw agent --deliver'. This stored gateway token grants the service ongoing ability to invoke your OpenClaw gateway — only proceed if you accept that.
- The installer may download the 'himalaya' binary from GitHub Releases via curl|tar into /usr/local/bin; verify this is acceptable for your environment.
- Auto-reply is disabled by default, but if you enable auto-reply (auto_reply_mode = 'true') the agent may reply to email senders — keep it off or 'ask' if you want safer behavior.
- Practical steps: review the packaged scripts (setup.py, imap_watcher.py, telegram_commands.py, uninstall.sh) yourself or with a sysadmin; back up any tokens and rotate them after install if concerned; run the installer interactively and verify the agent prompts for explicit consent as the SKILL.md requires; consider running this on an isolated host or VM if you are unsure.
Why I marked this 'benign (medium confidence)': the implementation, files, and instructions match the described purpose and the behaviors (systemd service, token reading) have plausible reasons, but the skill reads and persists sensitive local tokens and uses curl|tar installation for a binary — these are elevated actions that warrant explicit user review and consent.Like a lobster shell, security has layers — review code before you run it.
latestvk970zcnv7f0qmwedcyqymyyemx83h43b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
