[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"pack-detail-email-inbox-triage-ai-zh":3,"seo:pack:email-inbox-triage-ai:zh":93},{"code":4,"message":5,"data":6},200,"操作成功",{"pack":7},{"slug":8,"icon":9,"tone":10,"status":11,"status_label":12,"title":13,"description":14,"items":15,"install_cmd":92},"email-inbox-triage-ai","📧","#0EA5E9","new","本周新建","AI 收件箱管家 — 让 AI 当你的邮箱 EA","九件资产，给每天收上百封邮件的高管 \u002F 创业者 \u002F 销售 — 让 agent 帮你分类、起草、跟进、同步日历、监控反垃圾事件。围绕一个真正掌管 Gmail\u002F日历的 MCP 搭建，不是套壳。",[16,28,38,45,53,61,68,75,83],{"id":17,"uuid":18,"slug":19,"title":20,"description":21,"author_name":22,"view_count":23,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3146,"07565199-d466-4fdf-83f7-3e12f339a8b7","google-workspace-mcp-gmail-calendar-drive-for-agents","Google Workspace MCP — Gmail\u002FCalendar\u002FDrive for Agents","Google Workspace MCP exposes Gmail, Calendar, and Drive actions as MCP tools so agents can summarize inboxes and manage schedules with minimal scopes.","MCP Hub",77,0,"en","mcp","MCP",{"id":29,"uuid":30,"slug":31,"title":32,"description":33,"author_name":34,"view_count":35,"vote_count":24,"lang_type":25,"type":36,"type_label":37},4295,"aadd0579-94e1-4e7f-8054-c8b99590565a","claude-code-agent-communication-excellence-coach-aadd0579","Claude Code Agent: Communication Excellence Coach","Communication specialist providing email refinement, tone calibration, roleplay practice for difficult conversations, and presentation feedback with research-backed suggestions","TokRepo精选",27,"skill","Skill",{"id":39,"uuid":40,"slug":41,"title":42,"description":43,"author_name":34,"view_count":44,"vote_count":24,"lang_type":25,"type":36,"type_label":37},4307,"46b405be-441e-4d57-90f5-d6a386fe6591","claude-code-agent-sales-automator-46b405be","Claude Code Agent: Sales Automator","Sales automation and outreach specialist. Use PROACTIVELY for cold email campaigns, follow-up sequences, proposal templates, case studies, sales scripts, and conversion...",34,{"id":46,"uuid":47,"slug":48,"title":49,"description":50,"author_name":51,"view_count":52,"vote_count":24,"lang_type":25,"type":36,"type_label":37},184,"196351b6-820d-4fab-b416-8995ffe4479e","lark-cli-skill-mail-email-management-196351b6","Lark CLI Skill: Mail — Email Management","Lark\u002FFeishu CLI skill for email. Draft, send, reply, forward emails. Manage drafts, folders, labels, contacts, and attachments.","Lark \u002F Feishu",144,{"id":54,"uuid":55,"slug":56,"title":57,"description":58,"author_name":59,"view_count":60,"vote_count":24,"lang_type":25,"type":36,"type_label":37},454,"0bb26dc7-d062-455a-a33b-a4c29beff8b0","cal-com-open-source-scheduling-infrastructure-0bb26dc7","Cal.com — Open-Source Scheduling Infrastructure","The open Calendly alternative. Embed scheduling in any app with APIs and webhooks. Self-hostable. 40K+ GitHub stars.","AI Open Source",146,{"id":62,"uuid":63,"slug":64,"title":65,"description":66,"author_name":22,"view_count":67,"vote_count":24,"lang_type":25,"type":26,"type_label":27},806,"b84b96fd-0fc2-439d-9f29-4fb564bc2ded","tempo-mcp-calendar-time-tracking-agents-b84b96fd","Tempo MCP — Calendar and Time Tracking for Agents","MCP server that gives AI agents calendar awareness and time tracking. Tempo MCP integrates with Google Calendar and Toggl for scheduling, time logging, and availability checks.",131,{"id":69,"uuid":70,"slug":71,"title":72,"description":73,"author_name":22,"view_count":74,"vote_count":24,"lang_type":25,"type":26,"type_label":27},698,"cf74621a-0188-4222-8c9b-285873183b56","composio-250-tool-integrations-ai-agents-cf74621a","Composio — 250+ Tool Integrations for AI Agents","Connect AI agents to 250+ tools (GitHub, Slack, Gmail, Jira, etc.) with managed auth and natural language actions. Works with LangChain, CrewAI, and OpenAI.",85,{"id":76,"uuid":77,"slug":78,"title":79,"description":80,"author_name":81,"view_count":82,"vote_count":24,"lang_type":25,"type":36,"type_label":37},2981,"e60ca183-5be1-4d16-ae96-2b7b3bedba46","resend-webhooks-email-delivery-events-for-ai-agents","Resend Webhooks — Email Delivery Events for AI Agents","Resend webhooks fire on delivery, open, click, bounce, complaint. Route to your agent for follow-ups, deliverability monitoring, cleanup.","Resend",72,{"id":84,"uuid":85,"slug":86,"title":87,"description":88,"author_name":81,"view_count":89,"vote_count":24,"lang_type":25,"type":90,"type_label":91},2982,"d826f667-d0f9-4ded-895e-19ed5d774b47","resend-audiences-manage-email-lists-from-ai-agents","Resend Audiences — Manage Email Lists from AI Agents","Resend Audiences API lets agents add, remove, segment, unsubscribe email recipients. Tag-based segments. Compliant unsubscribe built in.",82,"script","Script","tokrepo install pack\u002Femail-inbox-triage-ai",{"pageType":94,"pageKey":8,"locale":95,"title":96,"metaDescription":97,"h1":98,"tldr":99,"bodyMarkdown":100,"faq":101,"schema":117,"internalLinks":152,"citations":165,"wordCount":178,"generatedAt":179},"pack","zh","AI 收件箱管家 — 让 AI 当你的邮箱 EA 的 9 件资产","Google Workspace MCP \u002F Communication Coach \u002F Sales Automator \u002F Lark CLI Mail \u002F Cal.com \u002F Tempo MCP \u002F Composio \u002F Resend Webhooks \u002F Resend Audiences — 给收件箱决定一天的高管 \u002F 创业者 \u002F 销售，九件资产覆盖分类、起草、跟进、日程同步、反垃圾五层。","AI 收件箱管家 — 让 agent 当你的邮箱 EA","九件资产五个层：先把进来的邮件分类，再起草回复，再调度跟进，再同步日程邀请，最后盯反垃圾和投递事件。**真正掌管 Gmail 和日历的 MCP 是非协商项**，其它八件都插它身上。","## 这个 pack 包含什么\n\n这是给**收件箱决定一天**的人准备的栈：早上 9 点还有 200 封未读的高管，一个邮箱同时跑销售 + 招聘 + 投资人 update 的 founder，独苗 AE 在管真实 pipeline。不是 Product Hunt 上「AI email」产品的许愿清单。每件资产对应一名行政助理本该替你做的五件事中的一件：triage、起草、跟进、排日程、保投递质量。\n\n核心原则：**agent 必须握住凭据，而不是去截屏**。所以这个 pack 的脊柱是一个拿到 Gmail + Calendar OAuth scope 的 MCP server（第 1 件），不是一个看你打字的浏览器插件。MCP 在位后其它八件就可组合：一个 coaching agent 收紧语气，一个 sales automator 跑 outbound 层，一个 CLI 邮件工具管第二个账号（飞书 \u002F Lark），一个真正的排程入口，一个在你 sender reputation 被毁之前就 flag bounce 的 webhook 层。\n\n## 推荐安装顺序（分类 → 起草 → 跟进 → 排日程 → 反垃圾）\n\n### 第一层 — 分类 & 收件箱所有权\n\n1. **Google Workspace MCP — Gmail\u002FCalendar\u002FDrive for Agents** — 脊柱。给 Gmail 拿到 `messages.list`、`messages.modify`、`drafts.create` 权限，给 Calendar 拿到 `events.insert`。从这里开始，agent 能读进来什么、打 label（`AI\u002FTriage\u002FReply`、`AI\u002FTriage\u002FArchive`、`AI\u002FTriage\u002FFYI`）、把草稿写进对的那条会话。下面所有事都假设你做了这一步。\n\n### 第二层 — 草稿质量\n\n2. **Claude Code Agent: Communication Excellence Coach** — 语气校准器。MCP 起草完回复，这个 agent 把它改写成你的声音：「热情但快」、「干脆拒绝但不烧桥」、「执行层 bullet 回应，零前奏」。当**第二遍**用，绝不是第一遍。\n3. **Claude Code Agent: Sales Automator** — 当进来的是 lead 不是同行。冷暖外联回复、跟进序列、案例插入。outbound 那一侧用它，让 Communication Coach 专心管内部声音。\n\n### 第三层 — 多账号桥接\n\n4. **Lark CLI Skill: Mail — Email Management** — 给第二个邮箱用。多数高管有一个 Gmail 加一个 Lark\u002F飞书（或 Outlook）账号。这个 Lark CLI 给中国侧邮箱提供 agent 用的 draft\u002Fsend\u002Freply\u002Fforward 原语，不用再走一遍 OAuth。\n\n### 第四层 — 日历 & 排程\n\n5. **Cal.com — Open-Source Scheduling Infrastructure** — 对外的预约入口。当 agent 回「乐意见，这是我的链接」时，Cal.com 就是那个链接。可自托管、每次预订都有 webhook、和 MCP 已经掌管的 Google Calendar 自动查冲突。\n6. **Tempo MCP — Calendar and Time Tracking for Agents** — 工作时段大脑。agent 准备 propose 三个时间槽时，Tempo MCP 回答「这三个不打断 focus block 也不和深度工作计时器冲突」。没它 agent 会把周一早 8 点丢给你。\n\n### 第五层 — 外发投递 & 跟进\n\n7. **Composio — 250+ Tool Integrations for AI Agents** — 兜底轨。当你需要 Outlook（还没有一线 MCP）、用 Slack DM 做跟进渠道，或者 inbound 回复要回写 HubSpot\u002FSalesforce 时，Composio 是桥。**别**把它当脊柱用，把它当长尾用。\n8. **Resend Webhooks — Email Delivery Events for AI Agents** — bounce\u002Fspam 雷达。每封 agent 用自定义域名发的事务邮件都触发 `delivered`\u002F`bounced`\u002F`complained`。路由到一个 `mailops` 频道，免得 VIP 的 bounce 静默三天没人发现。\n9. **Resend Audiences — Manage Email Lists from AI Agents** — 抑制名单层。退订、硬 bounce、「请别再发邮件给我」的回复都喂回一个抑制名单，agent 在起草下一封外发**之前**先读它。这是 agent 和喷垃圾炮台之间的区别。\n\n## 它们怎么协同\n\n```\n     收件\n      │\n      ▼\n  Google Workspace MCP (1)\n  （读 + label + 起草）\n      │\n  ┌───┼───┐\n  ▼   ▼   ▼\n 回复 转发 归档\n  │\n  ├─ 内部语气 ─► Communication Coach (2)\n  └─ 外联 lead ─► Sales Automator (3)\n      │\n      ▼\n   飞书 \u002F Lark 那一侧?\n      │\n      ▼\n   Lark CLI Mail (4)\n      │\n      ▼\n   要约会议？\n      │\n  ┌───┴───┐\n  ▼       ▼\n Cal.com  Tempo MCP\n  (5)     (6)\n 对外链接 焦点感知时段\n      │\n      ▼\n   Composio (7) — Outlook \u002F Slack \u002F CRM 长尾\n      │\n      ▼\n   Resend Webhooks (8) → bounce\u002Fspam 告警\n      │\n      ▼\n   Resend Audiences (9) — 抑制名单\n      │\n      ▼\n   （下一次外发先查这里）\n```\n\n非协商的连接是 **MCP 握住 Gmail 和 Calendar 凭据、agent 通过它操作、每次发送都回写会话**。MCP 丢了，你又退回到从聊天窗口往浏览器 tab 复制粘贴。\n\n## 你会遇到的取舍\n\n- **隐私 — agent 读了每一封邮件** — 一旦给 MCP 授了 Gmail 读权限，收件箱里的任何东西都在 agent 下次运行时进 context window。定价泄漏、M&A 线程、HR 信件。缓解：把 MCP scope 在 `AI\u002FTriage` 这种子 label 上，再用 Gmail filter 只把发件人白名单的邮件丢进去。第一天**不要**给全收件箱读权限。\n- **排程链接的厂商锁** — Cal.com 可自托管，Calendly 不行。这季度往 300 封外发里塞了 `calendly.com\u002Fyou`，以后换 Cal.com 就是 300 条死链。哪怕入职期间走 Calendly 兜底，先把 Cal.com 立起来。\n- **模型语气漂移** — Communication Coach 一开始很好，直到模型版本一升、「热情但快」变成 6 个 bullet 前奏。把上一次确认好的 prompt 存 git，每月和模型新输出 diff 一次。\n- **自动回复的风险** — 第一天就让 agent 不审就发，是「故障通告」收到一句「谢谢分享！」的回复方式。先跑 30 天 draft-only 模式（agent 写进 Gmail Drafts，你按发送）。之后再分类放开 — 永远不要一次全开。\n- **Outlook 在这里是二等公民** — Composio 桥接得了，但本 pack 里没有一线 Outlook MCP。只在 Exchange\u002FOutlook 上的话，脊柱反过来：Composio 变第 1 件，Google Workspace MCP 下架。其它七件照样适用。\n\n## 常见踩坑\n\n- **agent 自动回了一封人没读的邮件** — 「谢谢确认，3pm 见」落到错的会话，因为 agent 是按 `[Re: tomorrow]` 匹配的。修复：每一次发送必须满足 (a) 显式 `from: agent.allowlist` label 或 (b) 人审起草再发。这个错离你只有一次模型运行。\n- **误分类删了一封投资人邮件** — 如果 `AI\u002FTriage\u002FArchive` 是同时标记已读的 Gmail filter，可见性就没了。用独立 label，前一个月每周复盘 `AI\u002FTriage\u002FArchive`。验证过 200 次决策再开自动归档。\n- **GDPR \u002F CCPA 在「读 + 摘要」路径上的合规** — 用美区 LLM 摘要客户邮件是一次跨境数据传输。在欧盟需要要么 EU 模型 endpoint，要么 prompt 之前先 PII 脱敏。早做；事后过 sub-processor 审计补救很痛。\n- **多账号桥接漏** — Lark CLI 管飞书、Google Workspace MCP 管 Gmail、Composio 管 Outlook — 三条凭据路径就是三套轮换节奏。文档化每个 scope 在哪；不然 agent 会在你忘了的那个账号上静默失败。\n- **没有 bounce 监控 = 投递率静默崩溃** — DKIM 配错那天，所有外发开始进垃圾箱。没接 Resend Webhooks 到聊天频道，你会两周后才从投资人那句「你那条 update 我没看到」里知道。第一天就把告警接上。",[102,105,108,111,114],{"q":103,"a":104},"让 AI agent 读整个收件箱真的安全吗？","「安全」是错的词，「可审计」才是对的词。第一天**别**给 MCP 全 Gmail 读权限。建一条 Gmail filter，只把发件人白名单（你团队、已知供应商、点名的投资人）的邮件移进 `AI\u002FTriage` label，MCP 只 scope 到这个 label。其余 agent 看不到。随着每类逐步放心，再有意识地扩白名单。上一代行政助理也不是第一天就拿到你私人 Gmail 钥匙的，同一套流程。",{"q":106,"a":107},"Superhuman vs Shortwave 和这套栈，为啥不直接买？","Superhuman 和 Shortwave 是真产品，搭起来更快。还是建议自己搭 agent-MCP 版的理由：(1) agent 已经活在 Claude Code \u002F Cursor \u002F 你的 CLI 里，加个 MCP 让邮件和你的文档、CRM 同处一个 context window；(2) prompt、模型、抑制名单都你控 — 不会有「AI 这个月变差了」的惊喜；(3) 联系人图谱和草稿留在你 Gmail，不在厂商服务器。诚实代价：这套 pack 周末搭、一个月调；Superhuman 一次注册搞定。「回复时间」比「掌控权」更值钱就买；否则自己搭。",{"q":109,"a":110},"自动跟进 vs 手动确认 — 界限在哪？","三条规则。(1) 外联首触：agent 起草、人发送 — 前 90 天无一例外。(2) 对方已经回了的现有会话内跟进：agent 可以延迟 60 秒自动发，草稿对你可见，Gmail 里把草稿拖出 Drafts 就是 kill switch。(3) 日历确认（「行，3pm 可以」）：agent 可以自动发，因为动作可逆、错答代价低。任何**给新收件人创建新外发**的动作永远要人审。规律：可逆性一轴，新颖度一轴，只在两者都低时自动发。",{"q":112,"a":113},"agent 能自动解决日历冲突吗？","低风险能（内部 sync、固定会议溢出），高风险不能（投资人 pitch、客户 demo）。技术路径：Tempo MCP 暴露「这个时段是不是 focus block」、Google Workspace MCP 暴露事件本身、agent 对比后 propose。策略路径：维护一个 `vip_calendar_priority` 与会人域名白名单，agent 不问就绝不改这些会的时间。没这白名单的话，迟早有一天你会发现「为了腾出咖啡聊天的位置，董事会被挪了」。",{"q":115,"a":116},"能同时管多个邮箱吗？","能，但每个账号都是自己的凭据自己的 MCP 实例。具体：Gmail 走 Google Workspace MCP（第 1 件）、飞书\u002FLark 走 Lark CLI Skill: Mail（第 4 件）、Outlook 走 Composio（第 7 件）。Agent 按你传的 `account` 参数选对的工具。更难的问题是跨账号统一 triage — 要么把所有邮件转发到一个 Gmail（最简单），要么 agent 顺序跑三次 triage（更诚实、更容易撞 rate limit）。先从转发起步，等单一账号不再权威时再升级到多轮 pass。",{"@context":118,"@type":119,"name":120,"description":121,"numberOfItems":122,"inLanguage":123,"itemListElement":124},"https:\u002F\u002Fschema.org","ItemList","AI 收件箱管家","九件 AI 时代的资产，给收件箱决定一天的高管 \u002F 创业者 \u002F 销售：通过真正掌管 Gmail 和 Calendar 的 MCP 完成分类、起草、跟进、日程同步、投递监控。",9,"zh-CN",[125,129,132,135,138,141,144,147,150],{"@type":126,"position":127,"name":20,"url":128},"ListItem",1,"https:\u002F\u002Ftokrepo.com\u002Fzh\u002Fworkflows\u002Fgoogle-workspace-mcp-gmail-calendar-drive-for-agents-07565199",{"@type":126,"position":130,"name":32,"url":131},2,"https:\u002F\u002Ftokrepo.com\u002Fzh\u002Fworkflows\u002Fclaude-code-agent-communication-excellence-coach-aadd0579",{"@type":126,"position":133,"name":42,"url":134},3,"https:\u002F\u002Ftokrepo.com\u002Fzh\u002Fworkflows\u002Fclaude-code-agent-sales-automator-46b405be",{"@type":126,"position":136,"name":49,"url":137},4,"https:\u002F\u002Ftokrepo.com\u002Fzh\u002Fworkflows\u002Flark-cli-skill-mail-email-management-196351b6",{"@type":126,"position":139,"name":57,"url":140},5,"https:\u002F\u002Ftokrepo.com\u002Fzh\u002Fworkflows\u002Fcal-com-open-source-scheduling-infrastructure-0bb26dc7",{"@type":126,"position":142,"name":65,"url":143},6,"https:\u002F\u002Ftokrepo.com\u002Fzh\u002Fworkflows\u002Ftempo-mcp-calendar-time-tracking-agents-b84b96fd",{"@type":126,"position":145,"name":72,"url":146},7,"https:\u002F\u002Ftokrepo.com\u002Fzh\u002Fworkflows\u002Fcomposio-250-tool-integrations-ai-agents-cf74621a",{"@type":126,"position":148,"name":79,"url":149},8,"https:\u002F\u002Ftokrepo.com\u002Fzh\u002Fworkflows\u002Fresend-webhooks-email-delivery-events-for-ai-agents-e60ca183",{"@type":126,"position":122,"name":87,"url":151},"https:\u002F\u002Ftokrepo.com\u002Fzh\u002Fworkflows\u002Fresend-audiences-manage-email-lists-from-ai-agents-d826f667",[153,157,161],{"url":154,"anchor":155,"reason":156},"\u002Fzh\u002Fai-tools-for\u002Femail","AI 邮件工具集","本 pack 是邮件工具目录里的旗舰收件箱管理入口",{"url":158,"anchor":159,"reason":160},"\u002Fzh\u002Fai-tools-for\u002Fautomation","AI 自动化工具集","收件箱 triage 是 agent 驱动自动化的经典用例",{"url":162,"anchor":163,"reason":164},"\u002Fzh\u002Ffeatured","TokRepo 精选资产","这九件资产是更大的 agent-ready 精选目录的一部分",[166,170,174],{"claim":167,"source_name":168,"source_url":169},"Cal.com 是开源的排程基础设施","Cal.com 官网","https:\u002F\u002Fcal.com\u002F",{"claim":171,"source_name":172,"source_url":173},"Resend 暴露 delivered \u002F bounced \u002F complained 的投递 webhook","Resend webhook 文档","https:\u002F\u002Fresend.com\u002Fdocs\u002Fdashboard\u002Fwebhooks\u002Fintroduction",{"claim":175,"source_name":176,"source_url":177},"Model Context Protocol (MCP) 让 agent 用受控凭据调用托管工具","Anthropic MCP 介绍","https:\u002F\u002Fmodelcontextprotocol.io\u002Fintroduction",980,"2026-05-23T12:00:00Z"]