Token导航 LogoToken导航TokenDH.com
效率需要联网clawhub未标认证来源可访问clear审计通过

bee-push-email-skill蜜蜂推送邮件技巧

Agent Skill

bee-push-email-skill 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

7,944

周安装

331

GitHub Stars

2

下载量

2,648
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:bee-push-email-skill(蜜蜂推送邮件技巧)
来源仓库:https://github.com/canihojr/bee-push-email-skill
安装命令:
openclaw skills install bee-push-email-skill
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install bee-push-email-skill

简介

通过 IMAP IDLE 实时监控电子邮件,并触发 OpenClaw 代理通过 Telegram 或 Discord 等活动渠道通知用户。

SKILL.md

name
bee-push-email
description
Push email notifications via IMAP IDLE + Himalaya + OpenClaw agent. Detects new emails in real-time and triggers the agent to process and notify the user. Use when: setting up email push notifications, configuring IMAP watcher, installing bee-push-email system, testing email connectivity, checking system dependencies, viewing email-push config, troubleshooting IMAP IDLE watcher, or managing the imap-watcher systemd service. Also handles uninstall/cleanup of the bee-push-email system. Trigger on beemail commands: /beemail, /beemail_start, /beemail_stop, /beemail_status, /beemail_test, /beemail_reply, /beemail_reply_off, /beemail_reply_ask, /beemail_reply_on. Also: start watcher, stop watcher, watcher status, email push status, registrar comandos, comandos no aparecen, beemail no funciona en telegram.
emoji
📧
requirements
bins

Email Push — IMAP IDLE → OpenClaw Agent → User Notification

Real-time email monitoring: IMAP IDLE detects new emails, triggers OpenClaw agent to process and notify the user via their active channel.

Security & Permissions

The agent MUST explicitly inform the user of all actions below and obtain approval before starting installation. Do not proceed without confirmed user consent.

What this skill installs (requires root)

ActionPath / TargetNotes
System userimap-watcher (useradd -r)Service runs as this non-root user
Python venv/opt/imap-watcher/Isolated env, not system-wide
pip packageimapclient (inside venv only)Not installed system-wide
Watcher script/opt/imap-watcher/imap_watcher.pyCopied from skill directory
systemd unit/etc/systemd/system/imap-watcher.serviceEnabled + started, restarts on boot
Config file/opt/imap-watcher/watcher.confchmod 600, owner imap-watcher only
Log file/var/log/imap-watcher.logchmod 640, owner imap-watcher

External downloads (requires user awareness)

WhatFromCondition
himalaya binarygithub.com/pimalaya/himalaya/releases/latest/Only if not already installed
Method`curl \tar into /usr/local/bin/`Writes a system binary

Credentials accessed

CredentialSourceUsage
IMAP email passwordProvided by user at install timeIMAP IDLE connection
Telegram botTokenRead from ~/.openclaw/openclaw.jsonRegisters /beemail* commands via Telegram API (setMyCommands)

The bot token is never stored by this skill.

Auto-reply behaviour

By default, the agent is instructed not to reply to email senders. This prevents exposing that the system is active and avoids phishing/spam risks. The allow_auto_reply field in watcher.conf controls this:

ValueBehaviour
false (default)Agent notifies you via Telegram only. Never replies to senders.
askAgent asks you for explicit approval via Telegram before replying.
trueAgent may reply to senders if it deems appropriate (least safe).

Configured interactively during install. Change anytime with --reconfigure + systemctl restart imap-watcher.

If auto_reply_mode is missing from an existing install, the watcher logs [SECURITY] WARNING on startup and notifies the agent to alert you. The safe default false is applied until you run --reconfigure. It is read once per operation and used only to call api.telegram.org. The agent must inform the user that their bot token will be used to modify the bot's command menu.

Persistence

This skill installs a persistent background service (Restart=always, starts on boot). It maintains a continuous IMAP connection. The service runs as the dedicated imap-watcher user, not as root.

Uninstall removes everything: service, systemd unit, /opt/imap-watcher/, log file, system user, and Telegram bot commands.

Install Flow (4 stages)

Stage 1: Dependencies (--deps)

python3 /root/.openclaw/workspace/skills/bee-push-email/scripts/setup.py --deps

Stage 2: Test Connection (--test)

echo '{"host":"...","port":993,"ssl":true,"email":"...","password":"..."}' | python3 /root/.openclaw/workspace/skills/bee-push-email/scripts/setup.py --test

Stage 3: Install (only if Stage 1+2 passed)

echo '{"host":"...","port":993,"ssl":true,"email":"...","password":"..."}' | python3 /root/.openclaw/workspace/skills/bee-push-email/scripts/setup.py

Stage 4: Verify (automatic)

Other Modes

Register Bot Commands (after update)

python3 /root/.openclaw/workspace/skills/bee-push-email/scripts/setup.py --register-commands

Reconfigure (after update)

After running clawhub update bee-push-email, new config fields may be available. Run:

python3 /root/.openclaw/workspace/skills/bee-push-email/scripts/setup.py --reconfigure

This detects fields missing from your existing /opt/imap-watcher/watcher.conf and asks about each one interactively — without touching your existing values. Restart the service after: systemctl restart imap-watcher.

Force Reinstall

echo '{...}' | python3 /root/.openclaw/workspace/skills/bee-push-email/scripts/setup.py --force

Show Config / Uninstall

python3 /root/.openclaw/workspace/skills/bee-push-email/scripts/setup.py --show
bash /root/.openclaw/workspace/skills/bee-push-email/scripts/uninstall.sh --yes

Telegram Bot Commands

<details> <summary>Click to expand command details</summary>

/beemail_status

  1. systemctl is-active imap-watcher + systemctl status imap-watcher --no-pager -l
  2. Last 10 log lines: journalctl -u imap-watcher -n 10 --no-pager
  3. UID state: cat /opt/imap-watcher/last_seen_uids.json
  4. Report: status, uptime, last email, IMAP state

/beemail_start

  1. systemctl start imap-watcher → wait 3s → verify active → show last 5 log lines

/beemail_stop

  1. systemctl stop imap-watcher → verify inactive → report

/beemail_test

  1. Check service active → read target email from config → tell user to send test email
  2. Optionally run: setup.py --test

/beemail

Quick summary: service active? + last email processed + one-liner health

/beemail_reply

Show current auto-reply mode:

  1. Run python3 <skill_dir>/scripts/setup.py --reply-status
  2. Report current mode with label: DISABLED / ASK / ENABLED

/beemail_reply_off

Disable auto-reply immediately:

  1. Run python3 <skill_dir>/scripts/setup.py --reply-off
  2. Service restarts automatically
  3. Confirm: "🔒 Auto-reply DISABLED"

/beemail_reply_ask

Set approval-required mode:

  1. Run python3 <skill_dir>/scripts/setup.py --reply-ask
  2. Service restarts automatically
  3. Confirm: "❓ Auto-reply set to ASK"

/beemail_reply_on

Enable auto-reply — warn the user first:

  1. Inform user: "⚠️ Enabling auto-reply exposes system activity to all senders including spam/phishing. Confirm?"
  2. Only proceed if user confirms
  3. Run python3 <skill_dir>/scripts/setup.py --reply-on
  4. Service restarts automatically
  5. Confirm: "⚠️ Auto-reply ENABLED"

</details>

Telegram Bot Commands Troubleshooting

If /beemail* commands don't appear in the Telegram menu after install:

  1. Verify registration:
   python3 /root/.openclaw/workspace/skills/bee-push-email/scripts/setup.py --register-commands
  1. Manual registration via BotFather:

- Open @BotFather in Telegram - Send /setcommands - Select your bot - Add each command: - beemail — Email push status & recent emails - beemail_start — Start IMAP email watcher - beemail_stop — Stop IMAP email watcher - beemail_status — Detailed watcher service status - beemail_test — Send test email to verify push

  1. If bot token not found: The setup reads botToken from ~/.openclaw/openclaw.json. Check that the Telegram channel is configured.
  1. Commands registered but agent doesn't respond: The agent needs this skill installed to handle the commands. Verify with clawhub list.

Troubleshooting

  • Logs: journalctl -u imap-watcher -f
  • Status: systemctl status imap-watcher
  • Restart: systemctl restart imap-watcher
  • Config: /opt/imap-watcher/watcher.conf (JSON, chmod 600)
  • State: /opt/imap-watcher/last_seen_uids.json

Architecture

  1. imap_watcher.py maintains persistent IMAP IDLE connection
  2. On new email, resolves active OpenClaw session (with 60s cache)
  3. Triggers openclaw agent --deliver to process and notify user
  4. Uses Himalaya for email operations (read, move, reply)
  5. Runs as systemd service as dedicated imap-watcher user with auto-reconnect, exponential backoff, and health checks

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

82.37%
按下载量换算2,181

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills