[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"pack-detail-email-inbox-triage-ai-es":3,"seo:pack:email-inbox-triage-ai:es":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","Nuevo · esta semana","Inbox Triage AI — Tu EA para el correo","Nueve picks para el inbox saturado de un ejecutivo, founder o AE — la capa de agente que clasifica, redacta, hace follow-up, sincroniza la invitación de calendario y vigila los eventos de spam\u002Fbounce en tu lugar. Construido alrededor de un MCP que realmente controla Gmail\u002FCalendar, no un wrapper que finge.",[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":25,"title":95,"metaDescription":96,"h1":97,"tldr":98,"bodyMarkdown":99,"faq":100,"schema":116,"internalLinks":150,"citations":163,"wordCount":176,"generatedAt":177},"pack","Email Inbox Triage AI — 9 Agent-Era Picks to Run Your Inbox Like an EA","Google Workspace MCP, Communication Coach, Sales Automator, Lark Mail CLI, Cal.com, Tempo MCP, Composio, Resend Webhooks, Resend Audiences — the nine-asset stack for the exec or founder whose inbox decides the day. Classify, draft, follow up, sync the calendar, watch spam\u002Fbounce.","Email Inbox Triage AI — Let an Agent Be Your Inbox EA","Nine picks in five layers: classify what landed, draft the reply, schedule the follow-up, sync the calendar invite, and watch the deliverability\u002Fspam side. The MCP that actually owns Gmail and Calendar is non-negotiable — everything else plugs into it.","## What's in this pack\n\nThis is the stack for someone whose **inbox decides the day**: an exec with 200 unread by 9am, a founder doing sales + hiring + investor updates from one address, a single AE running a real pipeline. Not a wishlist of every \"AI email\" product on Product Hunt. Every pick maps to one of the five jobs an executive assistant would do for you: triage, draft, follow up, schedule, and keep the deliverability clean.\n\nThe principle: **the agent must hold the credential, not screenshot the screen**. That's why the spine of this pack is an MCP server with Gmail and Calendar OAuth scope (pick 1), not a browser plugin that watches you type. With the MCP in place, the other eight picks become composable: a coaching agent to tighten tone, a sales automator for the outbound layer, a CLI mail tool for the second account (Feishu\u002FLark), a real scheduling endpoint, and a webhook layer that flags bounces before they cost you a sender reputation.\n\n## Install in this order (classify → draft → follow up → schedule → anti-spam)\n\n### Layer 1 — Classification & inbox ownership\n\n1. **Google Workspace MCP — Gmail\u002FCalendar\u002FDrive for Agents** — the spine. OAuth into Gmail with `messages.list`, `messages.modify`, `drafts.create` scopes and into Calendar with `events.insert`. From here the agent can read what came in, label it (`AI\u002FTriage\u002FReply`, `AI\u002FTriage\u002FArchive`, `AI\u002FTriage\u002FFYI`), and draft into the right thread. Everything below assumes you've done this step.\n\n### Layer 2 — Draft quality\n\n2. **Claude Code Agent: Communication Excellence Coach** — tone calibrator. Once the MCP has drafted a reply, this agent rewrites it to match your voice: \"warm but quick,\" \"firm decline without burning the bridge,\" \"executive bullet response with no preamble.\" Pair as a second pass; never the first.\n3. **Claude Code Agent: Sales Automator** — when the inbound is a lead, not a peer. Cold and warm outbound replies, follow-up sequences, case-study insertions. Use this for the outbound side of the inbox so the Communication Coach can stay focused on internal voice.\n\n### Layer 3 — Multi-account bridge\n\n4. **Lark CLI Skill: Mail — Email Management** — for the second mailbox. Most execs have a Gmail and a Lark\u002FFeishu (or Outlook) account. This Lark CLI gives you draft\u002Fsend\u002Freply\u002Fforward primitives from the agent for the China-side mailbox without spinning up a second OAuth dance.\n\n### Layer 4 — Calendar & scheduling\n\n5. **Cal.com — Open-Source Scheduling Infrastructure** — the public booking endpoint. When the agent replies \"happy to meet, here's my link,\" Cal.com is the link. Self-hostable, webhooks for every booking, conflict checking against the Google Calendar the MCP already owns.\n6. **Tempo MCP — Calendar and Time Tracking for Agents** — the working-hours brain. When the agent goes to propose three slots, Tempo MCP answers \"these are the ones that don't break focus blocks or overlap a deep-work timer.\" Without it the agent proposes 8am Mondays.\n\n### Layer 5 — Outbound deliverability & follow-up\n\n7. **Composio — 250+ Tool Integrations for AI Agents** — the fallback rail. When you need Outlook (no first-class MCP yet), Slack DM as a follow-up channel, or HubSpot\u002FSalesforce write-back from an inbound reply, Composio is the bridge. Don't make it the spine — make it the long tail.\n8. **Resend Webhooks — Email Delivery Events for AI Agents** — the bounce\u002Fspam radar. Every transactional reply the agent sends through a custom domain fires `delivered`\u002F`bounced`\u002F`complained`. Route to a `mailops` channel so a bounced VIP doesn't sit silent for three days.\n9. **Resend Audiences — Manage Email Lists from AI Agents** — the suppression layer. Unsubscribes, hard bounces, and \"please stop emailing me\" replies feed back into a suppression list the agent reads *before* it drafts the next outbound. This is the difference between an agent and a spam cannon.\n\n## How they fit together\n\n```\n     Inbound mail\n          │\n          ▼\n   Google Workspace MCP (1)\n   (read + label + draft)\n          │\n   ┌──────┼──────┐\n   ▼      ▼      ▼\n  Reply  Forward  Archive\n   │\n   ├── internal voice ──► Communication Coach (2)\n   └── outbound lead  ──► Sales Automator (3)\n          │\n          ▼\n   (Lark \u002F Feishu side?)\n          │\n          ▼\n   Lark CLI Mail (4)\n          │\n          ▼\n   Needs a meeting?\n          │\n   ┌──────┴──────┐\n   ▼             ▼\n  Cal.com (5)   Tempo MCP (6)\n  public link   focus-aware slots\n          │\n          ▼\n   Composio (7) — Outlook \u002F Slack \u002F CRM long tail\n          │\n          ▼\n   Resend Webhooks (8) → bounce\u002Fspam alerts\n          │\n          ▼\n   Resend Audiences (9) — suppression list\n          │\n          ▼\n   (next outbound checks here first)\n```\n\nThe non-negotiable join is **the MCP holds the Gmail and Calendar credential, the agent operates through it, and every send writes back to a thread**. Lose the MCP and you're back to copy-pasting from a chat window into a browser tab.\n\n## Tradeoffs you'll hit\n\n- **Privacy — the agent reads every email** — once you grant Gmail read scope to the MCP, anything in the inbox is in the context window the next time the agent runs. Pricing leaks, M&A threads, HR letters. Mitigation: scope the MCP to a child label like `AI\u002FTriage` and a Gmail filter that puts only sender-allowlisted mail there. Don't grant blanket `Inbox` read on day one.\n- **Vendor lock on the scheduling link** — Cal.com is self-hostable, Calendly is not. If you put `calendly.com\u002Fyou` into 300 outbound emails this quarter, switching to Cal.com later means 300 dead links. Stand up Cal.com first, even if you fall back to Calendly during onboarding.\n- **Model tone drift** — the Communication Coach is great until the model gets updated and \"warm but quick\" turns into 6-bullet preambles. Save your last-known-good prompt to git and diff against the model's new output monthly.\n- **Auto-reply risk** — letting the agent send without review on the first day is how an outage notice gets a chipper \"thanks for sharing!\" reply. Run for 30 days in draft-only mode (the agent drafts into Gmail Drafts, you press send). After that, whitelist categories case-by-case — never globally.\n- **Outlook is a second-class citizen here** — Composio bridges it, but there is no first-class Outlook MCP in this pack. If you're on Exchange\u002FOutlook only, the spine flips: Composio becomes pick 1 and Google Workspace MCP drops out. The other seven still apply.\n\n## Common pitfalls\n\n- **The agent auto-replies to a human who hasn't read your inbox** — \"thanks for confirming, see you at 3pm\" lands in the wrong thread because the agent matched on `[Re: tomorrow]`. Fix: every send requires either (a) an explicit `from: agent.allowlist` label or (b) human draft-then-send. The mistake is one model run away.\n- **Misclassification deletes an investor email** — if `AI\u002FTriage\u002FArchive` is a Gmail filter that also marks read, you lose visibility. Use a separate label and a weekly review of `AI\u002FTriage\u002FArchive` for the first month. Auto-archive only after you've validated 200 decisions.\n- **GDPR \u002F CCPA on the read-and-summarize path** — summarizing a customer email through a US-hosted LLM is a data transfer. EU-residency teams need either an EU model endpoint or a PII redaction step before the prompt. Bake the redaction in early; retrofitting after a sub-processor audit is painful.\n- **Multi-account bridge is leaky** — Lark CLI for the Feishu mailbox, Google Workspace MCP for Gmail, Composio for Outlook — three credential paths means three rotation cadences. Document which scope sits where; the alternative is the agent silently failing on the account you forgot you provisioned.\n- **No bounce monitoring = silent deliverability collapse** — the day you ship a misconfigured DKIM, every outbound email starts going to spam. Without Resend Webhooks routing to a chat channel, you'll find out two weeks later when an investor mentions they \"didn't see your update.\" Wire alerts on day one.",[101,104,107,110,113],{"q":102,"a":103},"Is it actually safe to let an AI agent read my entire inbox?","Safe is the wrong word — auditable is the right word. Don't grant the MCP blanket Gmail read scope on day one. Create a Gmail filter that moves only sender-allowlisted mail (your team, known vendors, named investors) into an `AI\u002FTriage` label, and scope the MCP to that label only. Everything else stays unseen by the agent. Expand the allowlist deliberately as you trust each category. Same drill the previous generation of executive assistants got: they didn't get the keys to the personal Gmail on day one either.",{"q":105,"a":106},"Superhuman vs Shortwave vs this stack — why build instead of buy?","Superhuman and Shortwave are real products and will be faster to set up. The reasons to build the agent-MCP version anyway: (1) your agent already lives in Claude Code \u002F Cursor \u002F your CLI, so adding an MCP keeps email in the same context window as your docs and CRM; (2) you control the prompt, the model, and the suppression list — no \"the AI got worse this month\" surprise; (3) the contact graph and the drafts stay in your Gmail, not on a vendor's servers. The honest tradeoff: this pack takes a weekend to wire and a month to tune. Superhuman is one signup. If your time-to-replied is more valuable than control, buy. Otherwise, build.",{"q":108,"a":109},"Auto follow-up vs manual confirmation — where's the line?","Three rules. (1) Outbound first touches: agent drafts, human sends — no exceptions for the first 90 days. (2) Follow-ups inside an existing thread where the prospect already replied: agent can auto-send after 60s delay with the draft visible to you, and a kill switch in Gmail (drag the draft out of Drafts). (3) Calendar confirmations (\"yes, 3pm works\"): agent can auto-send because the action is reversible and the cost of a wrong reply is low. Anything that creates a new outbound to a new recipient gets human review forever. The pattern: reversibility on one axis, novelty on the other; auto-send only when both are low.",{"q":111,"a":112},"Can the agent resolve calendar conflicts automatically?","Yes for low-stakes (internal sync, standing meeting overflow), no for high-stakes (investor pitch, customer demo). The technical path: Tempo MCP exposes \"is this slot a focus block,\" Google Workspace MCP exposes the events themselves, the agent compares and proposes. The policy path: have a `vip_calendar_priority` allowlist of attendee domains that the agent will never reschedule without asking. Without that allowlist you will, eventually, move a board meeting to make room for a coffee chat.",{"q":114,"a":115},"Can this manage multiple email accounts at once?","Yes, but each account is its own credential and its own MCP instance. Concretely: Gmail goes through Google Workspace MCP (pick 1), Feishu\u002FLark goes through Lark CLI Skill: Mail (pick 4), Outlook routes through Composio (pick 7). The agent picks the right tool based on the `account` parameter you pass. The harder problem is unified triage across them — for that you either route everything into a single Gmail via forwarding (simplest) or have the agent run three triage passes in sequence (more honest, more rate-limit risk). Start with the forward; graduate to the multi-pass when one account stops being canonical.",{"@context":117,"@type":118,"name":119,"description":120,"numberOfItems":121,"inLanguage":25,"itemListElement":122},"https:\u002F\u002Fschema.org","ItemList","Email Inbox Triage AI","Nine AI-era picks for the high-volume inbox of execs, founders, and AEs: classify, draft, follow up, sync the calendar, and watch deliverability through an MCP that actually owns Gmail and Calendar.",9,[123,127,130,133,136,139,142,145,148],{"@type":124,"position":125,"name":20,"url":126},"ListItem",1,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fgoogle-workspace-mcp-gmail-calendar-drive-for-agents-07565199",{"@type":124,"position":128,"name":32,"url":129},2,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fclaude-code-agent-communication-excellence-coach-aadd0579",{"@type":124,"position":131,"name":42,"url":132},3,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fclaude-code-agent-sales-automator-46b405be",{"@type":124,"position":134,"name":49,"url":135},4,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Flark-cli-skill-mail-email-management-196351b6",{"@type":124,"position":137,"name":57,"url":138},5,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fcal-com-open-source-scheduling-infrastructure-0bb26dc7",{"@type":124,"position":140,"name":65,"url":141},6,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Ftempo-mcp-calendar-time-tracking-agents-b84b96fd",{"@type":124,"position":143,"name":72,"url":144},7,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fcomposio-250-tool-integrations-ai-agents-cf74621a",{"@type":124,"position":146,"name":79,"url":147},8,"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fresend-webhooks-email-delivery-events-for-ai-agents-e60ca183",{"@type":124,"position":121,"name":87,"url":149},"https:\u002F\u002Ftokrepo.com\u002Fen\u002Fworkflows\u002Fresend-audiences-manage-email-lists-from-ai-agents-d826f667",[151,155,159],{"url":152,"anchor":153,"reason":154},"\u002Fen\u002Fai-tools-for\u002Femail","AI email tools","This pack is the flagship inbox-management entry in the email tools collection",{"url":156,"anchor":157,"reason":158},"\u002Fen\u002Fai-tools-for\u002Fautomation","Automation tools for AI agents","Inbox triage is a canonical agent-driven automation use case",{"url":160,"anchor":161,"reason":162},"\u002Fen\u002Ffeatured","Featured assets on TokRepo","These nine picks live alongside the broader curated catalog of agent-ready assets",[164,168,172],{"claim":165,"source_name":166,"source_url":167},"Cal.com is an open-source scheduling infrastructure","Cal.com official site","https:\u002F\u002Fcal.com\u002F",{"claim":169,"source_name":170,"source_url":171},"Resend exposes delivery webhooks for delivered, bounced, complained events","Resend webhooks docs","https:\u002F\u002Fresend.com\u002Fdocs\u002Fdashboard\u002Fwebhooks\u002Fintroduction",{"claim":173,"source_name":174,"source_url":175},"Model Context Protocol (MCP) lets agents call hosted tools with scoped credentials","Anthropic MCP introduction","https:\u002F\u002Fmodelcontextprotocol.io\u002Fintroduction",920,"2026-05-23T12:00:00Z"]