--- name: the-unseener display_name: The Unseener description: "Activate when a CSM is overwhelmed with notifications and needs to know what they can safely ignore — analyzes unread Slack threads, emails, and upcoming meetings to identify what resolved without you, what's FYI-only, and which meetings you can skip with a 2-sentence summary. Also activates for 'what can I ignore', 'triage my inbox', 'what did I miss that doesn't matter', 'unseener', 'clear my plate'." icon: "👻" trigger: unseener inputs: - name: time_range description: "Period to analyze (e.g., 'today', 'since yesterday', 'this week')" type: string required: false default: "since yesterday" tools: - kg_search - search_all depends-on: - html_design --- # The Unseener — Anti-Notification Intelligence ## Overview The Unseener is anti-notification intelligence for overwhelmed CSMs. Instead of surfacing what you SHOULD read, it tells you what you can SAFELY IGNORE. It analyzes all unread Slack threads, emails, and upcoming meetings, classifies each into skip/skim/must-handle categories, and generates an actionable dashboard showing estimated time saved and one-click actions. The result: "These 23 Slack threads resolved without you. These 8 emails are FYI-only. You can skip this meeting — here's the 2-sentence summary." It gives CSMs their time back so they can focus on what actually matters — their customers and strategic work. ## Workflow ### Step 1: Scan All Channels Pull all unread/recent activity across communication channels for the specified `{{time_range}}` (default: "since yesterday"): - **Slack threads** — Use `search_all` to find all Slack threads with recent activity. Search for threads the user participated in or was mentioned in. Also search for threads in channels the user follows. - **Emails** — Use `search_all` to find all emails received in the time range. Look for direct emails, CCs, mailing list emails, and automated notifications. - **Calendar events** — Use `search_all` to find upcoming meetings and calendar events. Check for meetings where the user is optional vs. required. - **Knowledge graph context** — Use `kg_search` to look up people, accounts, and projects mentioned in the notifications to understand priority and relationships. Collect every item into a unified list with: source (slack/email/calendar), sender, subject/thread title, participants, timestamp, and content summary. ### Step 2: Classify Each Item For each item, apply the classification framework: #### 🟢 Safe to Skip (Ignore) - Thread that resolved without the CSM — someone asked a question, someone else answered, marked resolved - FYI-only email where CSM is CC'd and no action is implied - Automated notifications (build alerts, system emails, newsletter digests) - Slack threads where CSM was in the channel but never mentioned or needed - Meeting where CSM is marked optional AND meeting notes/recording will be shared - Group emails where someone else from the team already responded #### 🟡 Skim Only (1-sentence summary sufficient) - Important context updates but no action needed from this CSM - Status updates on accounts the CSM owns (no red flags) - Team announcements or process changes - Threads where CSM was mentioned but only for awareness, not action - Meeting recaps or shared notes from meetings the CSM missed #### 🔴 Must Handle (Action Required) - Direct message or email specifically asking the CSM to do something - Customer-facing thread where the CSM is the primary owner and input is needed - Escalation or red-flag situation on one of the CSM's accounts - Decision that's blocked waiting on the CSM's input - Meeting where the CSM is presenting, leading, or the sole representative - Anything from the CSM's direct manager requesting something #### 🔵 Can Delegate - Request that another team member has the context and authority to handle - Internal process tasks that don't require the CSM's specific knowledge - Follow-up items that a junior team member could own ### Step 3: Critical Safety Rules **NEVER auto-classify as "Safe to Skip":** - Anything from a direct report — always at least "Skim" - Anything from the CSM's manager — always at least "Skim", usually "Must Handle" - Anything from a customer contact — always at least "Skim" - Anything mentioning an escalation, churn risk, or executive involvement — always "Must Handle" **Account priority matters:** - High-priority / strategic account FYI → classify as "Skim" minimum - Low-priority account FYI → can be "Safe to Skip" - Use `kg_search` to look up account priority, health scores, and renewal dates to inform classification **When unsure, err on the side of caution:** - Uncertain → classify as "Skim" not "Ignore" - Borderline between "Skim" and "Must Handle" → go with "Must Handle" ### Step 4: Generate the Unseener Report Load the `html_design` skill and create an HTML dashboard artifact. Structure: ``` 📊 THE UNSEENER REPORT [Time Range] | [Total Items Analyzed] ⏰ Estimated Time Saved: X hours Y minutes ┌─────────────────────────────────────────┐ │ 🟢 SAFE TO IGNORE (X items) │ │ │ │ For each item: │ │ • [Source icon] [Title/Subject] │ │ Why skip: [1-line reason] │ │ e.g., "Thread resolved by Sarah — │ │ customer confirmed fix works" │ └─────────────────────────────────────────┘ ┌─────────────────────────────────────────┐ │ 📅 SKIP THESE MEETINGS (X meetings) │ │ │ │ For each meeting: │ │ • [Meeting name] — [Date/Time] │ │ Why skip: [reason] │ │ 2-sentence summary of what it covers │ │ Suggested decline message: │ │ "[pre-written polite decline]" │ └─────────────────────────────────────────┘ ┌─────────────────────────────────────────┐ │ 🟡 SKIM THESE (X items) │ │ │ │ For each item: │ │ • [Source icon] [Title/Subject] │ │ TL;DR: [1-sentence summary] │ └─────────────────────────────────────────┘ ┌─────────────────────────────────────────┐ │ 🔴 MUST HANDLE (X items) │ │ │ │ For each item: │ │ • [Source icon] [Title/Subject] │ │ Action needed: [what specifically] │ │ Urgency: [High/Medium] │ │ Suggested response: [draft if helpful] │ └─────────────────────────────────────────┘ ┌─────────────────────────────────────────┐ │ 🔵 CAN DELEGATE (X items) │ │ │ │ For each item: │ │ • [Source icon] [Title/Subject] │ │ Delegate to: [suggested person] │ │ Why: [reason they can handle it] │ └─────────────────────────────────────────┘ ┌─────────────────────────────────────────┐ │ ⏰ TIME SAVED BREAKDOWN │ │ │ │ • Slack threads skipped: ~X min │ │ • Emails skipped: ~X min │ │ • Meetings skippable: ~X min │ │ • Total time reclaimed: X hrs Y min │ │ │ │ Time estimates: │ │ Slack thread = ~3 min avg read time │ │ Email = ~2 min avg read time │ │ Meeting = actual duration │ └─────────────────────────────────────────┘ ``` ### Step 5: Offer One-Click Actions After presenting the dashboard, offer these follow-up actions: 1. **"Mark all safe-to-ignore as read"** — If the user confirms, batch-process marking items as read 2. **"Send declines for skippable meetings"** — Use the pre-generated decline messages 3. **"Generate full summaries for skim items"** — Expand the 1-sentence summaries into 2-3 sentence versions 4. **"Deep dive on any Must Handle item"** — Provide full context and draft responses for any must-handle item 5. **"Re-classify an item"** — If the user disagrees with a classification, move it to a different category ## Output Format Always deliver: 1. The HTML dashboard artifact (opened in session tab) 2. A brief chat summary: "Analyzed X items. You can safely ignore Y (saving ~Z hours). Only N items need your attention." 3. The list of offered follow-up actions ## Tone Empowering and time-respecting. The CSM should feel RELIEF, not guilt about skipping things. Frame everything around giving them time back for what actually matters — their customers and strategic work.