Recruit Email Monitor

招聘邮件监控系统 - 自动检查邮箱、记录到表格、飞书通知、每日简报

Do NOT install or enable the cron jobs without reviewing and editing the scripts. Immediate actions to take before use: - Remove any hard-coded email accounts/passwords from scripts; configure your own accounts via a secure mechanism (environment variables or a protected config file), not inline constants. - Search both scripts for Feishu target IDs (e.g., 'ou_8de0...') and replace them with your own target or require a configurable value; otherwise notifications will go to the repository author's account. - Verify the 'openclaw message send' calls and ensure the OpenClaw CLI and Feishu plugin are trusted and configured correctly; consider replacing with direct API integration that uses your secrets stored securely. - Update EXCEL_PATH and PROCESSED_FILE to safe locations and inspect file permissions. - Prefer storing secrets in a secrets manager or environment variables and avoid committing credentials into code. If the included credentials are real, treat them as compromised and do not reuse them. If you are not comfortable auditing and editing the Python scripts yourself, do not install this skill.

Type: OpenClaw Skill Name: recruit-email-monitor Version: 1.0.0 The skill bundle contains hardcoded sensitive credentials, including email authorization codes for QQ and 163 accounts, and a hardcoded Feishu recipient ID (ou_8de02604ccd510eeb4897ffd70d96c1d) in both 'scripts/email-heartbeat-check.py' and 'scripts/email-daily-briefing.py'. While the documentation instructs users to replace these, the default configuration would exfiltrate the user's recruitment data to the author's Feishu account if not properly updated. Additionally, the scripts rely on hardcoded absolute paths tied to a specific local user ('/home/erhao/'), which is a significant security and portability flaw.