Skip to content

CSlawyer1985/legal-skillhub / skills/agent-email

agent-email

Verified

Agent 专用邮箱统一管理:让 Claude Code、Codex 等平台的 Agent 用一套命令收发邮件、整理收件箱、分发任务。支持网易 ClawEmail(claw.163.com)和腾讯 Agent Mail(QQ 邮箱,agent.qq.com)两家后端,通过 MAIL_PROVIDER 切换。当用户提到收发邮件、看收件箱、搜索邮件、回复转发邮件、下载附件、整理邮件、给其他 Agent 派邮件任务、配置 Agent 邮箱、腾讯 QQ 邮箱 Agent、网易 ClawEmail 时使用此 skill。

scripts/.env.example

View on GitHub
# Agent Email 环境配置
# 复制为 .env 并填入实际值。真实 .env 已被根 .gitignore 忽略(**/.env)。

# ═══ 默认后端 ═══
# claw    网易 ClawEmail(@clawemail/mail-cli,API Key 认证,零 token)
# agently 腾讯 Agent Mail / QQ 邮箱(@tencent-qqmail/agently-cli,OAuth 认证)
# 切换:export MAIL_PROVIDER=agently  即可让所有 mail_* 走腾讯
MAIL_PROVIDER=claw

# ═══ 网易 ClawEmail 字段(MAIL_PROVIDER=claw 时使用)═══
# Agent 邮箱地址
AGENT_EMAIL=your-agent@claw.163.com
# 发件人显示名称(对方收到邮件时看到的名称;claw_send/mail_send 据此构造 --from)
DISPLAY_NAME="Your Agent Name"
# 邮箱前缀(用于 clawemail 子邮箱管理)
CLAW_PREFIX=your-agent
# mail-cli Profile 名(默认 default;多账号用 --profile 区分)
CLAW_PROFILE=default
# 文件夹 ID(网易约定:1=收件箱, 3=已发送)
INBOX_FID=1
SENT_FID=3

# ═══ 腾讯 Agent Mail 字段(MAIL_PROVIDER=agently 时使用)═══
# agently-cli 的 OAuth 凭据由 CLI 自管(agently_login 后存本机),.env 不持有。
# AGENTLY_EMAIL 仅作记录用,mail_login/agently_login +me 会返回实际地址。
# AGENTLY_EMAIL=your-agent@qq.com

# ═══ 常用联系人(发任务 / 收发材料时直接引用,两家后端通用)═══
# 格式: AGENT_<NAME> 或 CONTACT_<NAME>
# source scripts/mail-ops.sh 后即可 $AGENT_MANUS / $CONTACT_163 引用
# AGENT_MANUS=manus@manus.bot
# CONTACT_163=you@163.com
# CONTACT_GMAIL=you@gmail.com
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexUnverifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall