pm-inbox-triagelisted

# PM inbox triage The inbox is where stakeholder relationships live or die. Most PMs let it become noise; this skill turns it back into signal. The skill reads recent threads, classifies them, drafts replies for the ones that need substantive responses, and surfaces the threads going stale. The user reviews, edits drafts, and decides what to send. Nothing leaves the agent. ## When to use - As part of `pm-morning-brief`'s inbox section (called implicitly) - When the inbox has grown past 20 unread and the user feels backed up - After being out for a few days - At end-of-day to clear the slate before tomorrow Don't use when: - The inbox is mostly social / personal (this skill is for work threads) - The user wants the agent to auto-send replies (the skill refuses) - The Gmail MCP server is not connected — surface that and stop ## How to apply ### 1. Chain to `pm-context-loader` Load `you.md`, the active project list, cross-project stakeholders. ### 2. Pull recent threads Use the Gmail MCP to pull threads: - Inbox folder, unread or recent (last 48 hours by default) - Filter out automated newsletters, GitHub notifications, calendar invites, and other non-work noise - Group by thread (a thread of replies is one item, not many) For each thread, capture: - Sender(s) - Subject - Last message date - Body of the most recent message (the agent's classifier needs the content) - Whether the user is on the To: line or just CC'd ### 3. Classify each thread Four categories: - *