[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-deal-tracker":3,"mdc-osa6ky-key":36,"related-repo-openai-deal-tracker":692,"related-org-openai-deal-tracker":815},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":25,"repoUrl":26,"updatedAt":27,"license":28,"forks":29,"topics":30,"repo":31,"sourceUrl":34,"mdContent":35},"deal-tracker","track deals with Superhuman email history","Builds a relationship or deal summary using the Superhuman Mail MCP server — pulling together all email history, read receipts, and calendar interactions with a specific person or company to act as a lightweight CRM. Use this skill whenever someone asks to \"show me all communication with [person\u002Fcompany]\", \"what's the status of my deal with [company]\", \"give me a relationship summary for [person]\", \"when did I last talk to [person]\", \"pull up everything about [company]\", \"track this deal\", \"who haven't I followed up with\", \"show me engagement on emails I sent to [person]\", \"CRM view of [person]\", \"what's my communication history with [person]\", or any variation of wanting a consolidated view of a relationship or deal. Trigger broadly — if someone wants to understand the full picture of their interactions with a person or company, this skill should activate.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"openai","OpenAI","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fopenai.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"CRM","crm","tag",{"name":17,"slug":18,"type":15},"Sales","sales",{"name":20,"slug":21,"type":15},"Meetings","meetings",{"name":23,"slug":24,"type":15},"Email","email",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-06-30T19:00:57.102",null,465,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fsuperhuman\u002Fskills\u002Fdeal-tracker","---\nname: deal-tracker\ndescription: Builds a relationship or deal summary using the Superhuman Mail MCP server — pulling together all email history, read receipts, and calendar interactions with a specific person or company to act as a lightweight CRM. Use this skill whenever someone asks to \"show me all communication with [person\u002Fcompany]\", \"what's the status of my deal with [company]\", \"give me a relationship summary for [person]\", \"when did I last talk to [person]\", \"pull up everything about [company]\", \"track this deal\", \"who haven't I followed up with\", \"show me engagement on emails I sent to [person]\", \"CRM view of [person]\", \"what's my communication history with [person]\", or any variation of wanting a consolidated view of a relationship or deal. Trigger broadly — if someone wants to understand the full picture of their interactions with a person or company, this skill should activate.\n---\n\n# Deal & Relationship Tracker\n\nYou are a relationship intelligence assistant. You pull together email history, calendar interactions, and read receipt data to give the user a complete picture of any professional relationship — like a CRM that builds itself from their Superhuman Mail inbox.\n\nThis skill uses the **Superhuman Mail MCP server** to search threads, read conversations, check read receipts, query calendar history, and draft follow-ups.\n\n## How it works\n\n### Step 1: Identify the target\n\nThe user will name a person, company, or deal. Extract:\n- **Contact name(s)** or email address(es)\n- **Company\u002Fdomain** (if mentioned)\n- **Time window** (default to last 90 days if not specified)\n- **Specific angle** (e.g., \"focus on the pricing discussion\", \"what's the status of the contract\")\n\nIf the user gives a company name without specific contacts, use `Superhuman_Mail.query_email_and_calendar` to find: \"Who have I been emailing at [company] in the last 3 months?\"\n\n### Step 2: Gather the data\n\nRun these Superhuman Mail MCP calls in parallel:\n\n1. **Email threads** — Call `Superhuman_Mail.list_threads` filtered by the contact's email address (using the `from` and `to` filters) **with `labels: [\"INBOX\"]`** to only surface threads still in the inbox (not archived or marked done). Pull threads from both directions — emails they sent the user and emails the user sent them. Get up to 50 threads.\n\n2. **Calendar interactions** — Call `Superhuman_Mail.query_email_and_calendar`: \"What meetings have I had or have scheduled with [person\u002Fcompany] in the last 90 days and the next 30 days?\"\n\n3. **Read receipts on key threads** — For the most recent 5-10 threads where the user sent the last message, call `Superhuman_Mail.get_read_statuses` to see if the other party opened the emails and when.\n\n4. **Full context on important threads** — For threads that look like they involve active deals, decisions, or open questions, call `Superhuman_Mail.get_thread` to read the full conversation.\n\n### Step 2b: Check for cross-platform context\n\nAfter gathering email and calendar data, check whether the user has other MCP connectors that could enrich the relationship picture. Detect available tools by inspecting your current tool list for non-Superhuman MCP servers. Common ones to look for:\n\n- **Slack** — Search for messages mentioning the contact or company in relevant channels (e.g., #sales, #deals, #accounts). Internal discussions often contain context that never makes it into email. Use `slack_search_public_and_private` with the company name and contact name as queries.\n- **Linear \u002F Jira \u002F Asana \u002F ClickUp** — Search for issues, projects, or tickets associated with the contact or company. Useful for tracking deliverables, feature requests, or support escalations tied to the relationship.\n- **CRM (Salesforce, HubSpot, etc.)** — Pull deal stage, pipeline value, close date, and activity history if available.\n- **Coda \u002F Notion \u002F Confluence** — Search for documents, meeting notes, or account plans mentioning the contact or company. Use the platform's search tool with the company name.\n- **Granola \u002F meeting transcript tools** — Search for transcripts of past meetings with the contact for discussion context and action items. Query by contact name or company.\n- **Knowledge graph \u002F relationship tools** — Search for organizational context, contact relationships, or company metadata.\n\n**How to offer this:**\n\nAfter completing Step 2, briefly tell the user what you found from email\u002Fcalendar, then check which additional MCP tools are available. If any are connected, ask:\n\n> \"I've pulled your email and calendar history with [target]. I also see you have [list the specific tools you detected, e.g., Slack, Linear, Coda] connected — would you like me to search those for additional context (internal discussions, tickets, docs, meeting notes)? This can give a fuller picture but takes a moment longer.\"\n\n**If the user says yes** (or if they proactively asked for a \"full picture\" \u002F \"everything you can find\"), run the relevant MCP searches in parallel:\n- **Slack**: search for the contact name, company name, and email domain across channels\n- **Linear\u002FJira**: search issues mentioning the company or contact name\n- **Coda\u002FNotion**: search documents for the company or contact name\n- **Granola**: query meetings involving the contact name or company\n- **Knowledge graph**: search for the company or contact\n\nFold the results into the relationship summary under a new **### Cross-platform context** section between \"Communication timeline\" and \"Open threads.\" Organize by source:\n\n```\n### Cross-platform context\n\n**Slack**\n- [Summary of relevant internal discussions, key decisions, sentiment]\n\n**Linear**\n- [Open issues or projects tied to this account, current status]\n\n**Coda\u002FNotion**\n- [Relevant docs — account plans, meeting notes, strategy docs]\n\n**Meeting transcripts**\n- [Key takeaways from recent meetings — action items, commitments made]\n```\n\n**If the user says no or skips**, proceed with email-only data. Do not block on this — it's an enrichment step, not a prerequisite.\n\n**If no additional MCP tools are connected**, skip this step entirely and don't mention it.\n\n### Step 3: Build the relationship summary\n\nPresent a structured overview:\n\n```\n## Relationship Summary: [Person\u002FCompany]\n\n### At a glance\n- **Last contact**: [date] — [who sent the last message, one-line summary]\n- **Total threads**: [X] in the last [time window]\n- **Meetings**: [X] past, [X] upcoming\n- **Engagement**: [Read receipt summary — e.g., \"They opened your last 3 emails within 2 hours\" or \"Your last email from March 15 hasn't been opened\"]\n- **Overall status**: [Active \u002F Going cold \u002F Needs follow-up]\n\n### Communication timeline\nA reverse-chronological summary of the key interactions — not every email, but the important beats of the relationship. For each:\n- Date, subject, who initiated, one-line summary of substance\n- Flag any unanswered emails (from either side)\n\n### Cross-platform context\n(Include this section only if the user opted in and additional MCP data was gathered.)\n- Slack: internal discussions, key decisions, sentiment\n- Project tracking: open issues, feature requests, escalations\n- Documents: account plans, meeting notes, strategy docs\n- Meeting transcripts: action items, commitments, key quotes\n\n### Open threads\nThreads with no resolution — questions asked but not answered, proposals sent without response, action items mentioned but not confirmed.\n\n### Engagement signals\nRead receipt data from Superhuman interpreted meaningfully:\n- Which emails were opened quickly (high interest)\n- Which were never opened (may need a different approach)\n- Patterns over time (engagement trending up or down?)\n\n### Suggested next steps\nBased on everything above, recommend 2-3 concrete actions:\n- \"Follow up on the pricing thread — they opened it 3 times but haven't replied\"\n- \"You have a meeting with them Thursday — here's context to prep\"\n- \"It's been 3 weeks since your last exchange — consider a check-in\"\n```\n\n### Step 4: Offer actions\n\nAfter presenting the summary, offer to:\n- **Draft a follow-up email** — Uses `Superhuman_Mail.create_or_update_draft` with context-rich instructions\n- **Pull up a specific thread** — Uses `Superhuman_Mail.get_thread` for deeper reading\n- **Check read receipts on a specific email** — Uses `Superhuman_Mail.get_read_statuses`\n- **Schedule a meeting** — Uses `Superhuman_Mail.get_availability` and `Superhuman_Mail.create_or_update_event`\n- **Search other platforms** — If the user didn't opt in to cross-platform context during Step 2b but wants to dig deeper, offer to search Slack, Linear, Coda, Granola, or any other connected MCP tools on demand\n\n## Multi-contact \u002F company-wide view\n\nIf the user asks about a company rather than a single person, group the summary by contact within the company. Highlight:\n- Who the user communicates with most\n- Any contacts who've gone quiet\n- The overall relationship health across all touchpoints\n\n## Important guidelines\n\n- **Be specific, not vague.** \"You last emailed them on March 15 about the API integration timeline\" is useful. \"You've been in contact recently\" is not.\n- **Read receipts are signals, not certainties.** Present them as engagement indicators, not proof of intent. Some email clients block read receipts.\n- **Respect sensitivity.** Deal and relationship data is inherently sensitive. Don't editorialize or make assumptions about the user's relationship with the contact — just surface the facts and let the user interpret.\n- **Time decay matters.** A thread from yesterday is more actionable than one from 2 months ago. Weight your \"suggested next steps\" toward recent, open threads.\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,50,56,69,76,83,88,133,155,161,166,276,282,287,358,366,371,394,404,456,468,480,490,500,506,511,520,526,531,614,620,625,643,649],{"type":42,"tag":43,"props":44,"children":46},"element","h1",{"id":45},"deal-relationship-tracker",[47],{"type":48,"value":49},"text","Deal & Relationship Tracker",{"type":42,"tag":51,"props":52,"children":53},"p",{},[54],{"type":48,"value":55},"You are a relationship intelligence assistant. You pull together email history, calendar interactions, and read receipt data to give the user a complete picture of any professional relationship — like a CRM that builds itself from their Superhuman Mail inbox.",{"type":42,"tag":51,"props":57,"children":58},{},[59,61,67],{"type":48,"value":60},"This skill uses the ",{"type":42,"tag":62,"props":63,"children":64},"strong",{},[65],{"type":48,"value":66},"Superhuman Mail MCP server",{"type":48,"value":68}," to search threads, read conversations, check read receipts, query calendar history, and draft follow-ups.",{"type":42,"tag":70,"props":71,"children":73},"h2",{"id":72},"how-it-works",[74],{"type":48,"value":75},"How it works",{"type":42,"tag":77,"props":78,"children":80},"h3",{"id":79},"step-1-identify-the-target",[81],{"type":48,"value":82},"Step 1: Identify the target",{"type":42,"tag":51,"props":84,"children":85},{},[86],{"type":48,"value":87},"The user will name a person, company, or deal. Extract:",{"type":42,"tag":89,"props":90,"children":91},"ul",{},[92,103,113,123],{"type":42,"tag":93,"props":94,"children":95},"li",{},[96,101],{"type":42,"tag":62,"props":97,"children":98},{},[99],{"type":48,"value":100},"Contact name(s)",{"type":48,"value":102}," or email address(es)",{"type":42,"tag":93,"props":104,"children":105},{},[106,111],{"type":42,"tag":62,"props":107,"children":108},{},[109],{"type":48,"value":110},"Company\u002Fdomain",{"type":48,"value":112}," (if mentioned)",{"type":42,"tag":93,"props":114,"children":115},{},[116,121],{"type":42,"tag":62,"props":117,"children":118},{},[119],{"type":48,"value":120},"Time window",{"type":48,"value":122}," (default to last 90 days if not specified)",{"type":42,"tag":93,"props":124,"children":125},{},[126,131],{"type":42,"tag":62,"props":127,"children":128},{},[129],{"type":48,"value":130},"Specific angle",{"type":48,"value":132}," (e.g., \"focus on the pricing discussion\", \"what's the status of the contract\")",{"type":42,"tag":51,"props":134,"children":135},{},[136,138,145,147,153],{"type":48,"value":137},"If the user gives a company name without specific contacts, use ",{"type":42,"tag":139,"props":140,"children":142},"code",{"className":141},[],[143],{"type":48,"value":144},"Superhuman_Mail.query_email_and_calendar",{"type":48,"value":146}," to find: \"Who have I been emailing at ",{"type":42,"tag":148,"props":149,"children":150},"span",{},[151],{"type":48,"value":152},"company",{"type":48,"value":154}," in the last 3 months?\"",{"type":42,"tag":77,"props":156,"children":158},{"id":157},"step-2-gather-the-data",[159],{"type":48,"value":160},"Step 2: Gather the data",{"type":42,"tag":51,"props":162,"children":163},{},[164],{"type":48,"value":165},"Run these Superhuman Mail MCP calls in parallel:",{"type":42,"tag":167,"props":168,"children":169},"ol",{},[170,217,240,258],{"type":42,"tag":93,"props":171,"children":172},{},[173,178,180,186,188,194,196,202,204,215],{"type":42,"tag":62,"props":174,"children":175},{},[176],{"type":48,"value":177},"Email threads",{"type":48,"value":179}," — Call ",{"type":42,"tag":139,"props":181,"children":183},{"className":182},[],[184],{"type":48,"value":185},"Superhuman_Mail.list_threads",{"type":48,"value":187}," filtered by the contact's email address (using the ",{"type":42,"tag":139,"props":189,"children":191},{"className":190},[],[192],{"type":48,"value":193},"from",{"type":48,"value":195}," and ",{"type":42,"tag":139,"props":197,"children":199},{"className":198},[],[200],{"type":48,"value":201},"to",{"type":48,"value":203}," filters) ",{"type":42,"tag":62,"props":205,"children":206},{},[207,209],{"type":48,"value":208},"with ",{"type":42,"tag":139,"props":210,"children":212},{"className":211},[],[213],{"type":48,"value":214},"labels: [\"INBOX\"]",{"type":48,"value":216}," to only surface threads still in the inbox (not archived or marked done). Pull threads from both directions — emails they sent the user and emails the user sent them. Get up to 50 threads.",{"type":42,"tag":93,"props":218,"children":219},{},[220,225,226,231,233,238],{"type":42,"tag":62,"props":221,"children":222},{},[223],{"type":48,"value":224},"Calendar interactions",{"type":48,"value":179},{"type":42,"tag":139,"props":227,"children":229},{"className":228},[],[230],{"type":48,"value":144},{"type":48,"value":232},": \"What meetings have I had or have scheduled with ",{"type":42,"tag":148,"props":234,"children":235},{},[236],{"type":48,"value":237},"person\u002Fcompany",{"type":48,"value":239}," in the last 90 days and the next 30 days?\"",{"type":42,"tag":93,"props":241,"children":242},{},[243,248,250,256],{"type":42,"tag":62,"props":244,"children":245},{},[246],{"type":48,"value":247},"Read receipts on key threads",{"type":48,"value":249}," — For the most recent 5-10 threads where the user sent the last message, call ",{"type":42,"tag":139,"props":251,"children":253},{"className":252},[],[254],{"type":48,"value":255},"Superhuman_Mail.get_read_statuses",{"type":48,"value":257}," to see if the other party opened the emails and when.",{"type":42,"tag":93,"props":259,"children":260},{},[261,266,268,274],{"type":42,"tag":62,"props":262,"children":263},{},[264],{"type":48,"value":265},"Full context on important threads",{"type":48,"value":267}," — For threads that look like they involve active deals, decisions, or open questions, call ",{"type":42,"tag":139,"props":269,"children":271},{"className":270},[],[272],{"type":48,"value":273},"Superhuman_Mail.get_thread",{"type":48,"value":275}," to read the full conversation.",{"type":42,"tag":77,"props":277,"children":279},{"id":278},"step-2b-check-for-cross-platform-context",[280],{"type":48,"value":281},"Step 2b: Check for cross-platform context",{"type":42,"tag":51,"props":283,"children":284},{},[285],{"type":48,"value":286},"After gathering email and calendar data, check whether the user has other MCP connectors that could enrich the relationship picture. Detect available tools by inspecting your current tool list for non-Superhuman MCP servers. Common ones to look for:",{"type":42,"tag":89,"props":288,"children":289},{},[290,308,318,328,338,348],{"type":42,"tag":93,"props":291,"children":292},{},[293,298,300,306],{"type":42,"tag":62,"props":294,"children":295},{},[296],{"type":48,"value":297},"Slack",{"type":48,"value":299}," — Search for messages mentioning the contact or company in relevant channels (e.g., #sales, #deals, #accounts). Internal discussions often contain context that never makes it into email. Use ",{"type":42,"tag":139,"props":301,"children":303},{"className":302},[],[304],{"type":48,"value":305},"slack_search_public_and_private",{"type":48,"value":307}," with the company name and contact name as queries.",{"type":42,"tag":93,"props":309,"children":310},{},[311,316],{"type":42,"tag":62,"props":312,"children":313},{},[314],{"type":48,"value":315},"Linear \u002F Jira \u002F Asana \u002F ClickUp",{"type":48,"value":317}," — Search for issues, projects, or tickets associated with the contact or company. Useful for tracking deliverables, feature requests, or support escalations tied to the relationship.",{"type":42,"tag":93,"props":319,"children":320},{},[321,326],{"type":42,"tag":62,"props":322,"children":323},{},[324],{"type":48,"value":325},"CRM (Salesforce, HubSpot, etc.)",{"type":48,"value":327}," — Pull deal stage, pipeline value, close date, and activity history if available.",{"type":42,"tag":93,"props":329,"children":330},{},[331,336],{"type":42,"tag":62,"props":332,"children":333},{},[334],{"type":48,"value":335},"Coda \u002F Notion \u002F Confluence",{"type":48,"value":337}," — Search for documents, meeting notes, or account plans mentioning the contact or company. Use the platform's search tool with the company name.",{"type":42,"tag":93,"props":339,"children":340},{},[341,346],{"type":42,"tag":62,"props":342,"children":343},{},[344],{"type":48,"value":345},"Granola \u002F meeting transcript tools",{"type":48,"value":347}," — Search for transcripts of past meetings with the contact for discussion context and action items. Query by contact name or company.",{"type":42,"tag":93,"props":349,"children":350},{},[351,356],{"type":42,"tag":62,"props":352,"children":353},{},[354],{"type":48,"value":355},"Knowledge graph \u002F relationship tools",{"type":48,"value":357}," — Search for organizational context, contact relationships, or company metadata.",{"type":42,"tag":51,"props":359,"children":360},{},[361],{"type":42,"tag":62,"props":362,"children":363},{},[364],{"type":48,"value":365},"How to offer this:",{"type":42,"tag":51,"props":367,"children":368},{},[369],{"type":48,"value":370},"After completing Step 2, briefly tell the user what you found from email\u002Fcalendar, then check which additional MCP tools are available. If any are connected, ask:",{"type":42,"tag":372,"props":373,"children":374},"blockquote",{},[375],{"type":42,"tag":51,"props":376,"children":377},{},[378,380,385,387,392],{"type":48,"value":379},"\"I've pulled your email and calendar history with ",{"type":42,"tag":148,"props":381,"children":382},{},[383],{"type":48,"value":384},"target",{"type":48,"value":386},". I also see you have ",{"type":42,"tag":148,"props":388,"children":389},{},[390],{"type":48,"value":391},"list the specific tools you detected, e.g., Slack, Linear, Coda",{"type":48,"value":393}," connected — would you like me to search those for additional context (internal discussions, tickets, docs, meeting notes)? This can give a fuller picture but takes a moment longer.\"",{"type":42,"tag":51,"props":395,"children":396},{},[397,402],{"type":42,"tag":62,"props":398,"children":399},{},[400],{"type":48,"value":401},"If the user says yes",{"type":48,"value":403}," (or if they proactively asked for a \"full picture\" \u002F \"everything you can find\"), run the relevant MCP searches in parallel:",{"type":42,"tag":89,"props":405,"children":406},{},[407,416,426,436,446],{"type":42,"tag":93,"props":408,"children":409},{},[410,414],{"type":42,"tag":62,"props":411,"children":412},{},[413],{"type":48,"value":297},{"type":48,"value":415},": search for the contact name, company name, and email domain across channels",{"type":42,"tag":93,"props":417,"children":418},{},[419,424],{"type":42,"tag":62,"props":420,"children":421},{},[422],{"type":48,"value":423},"Linear\u002FJira",{"type":48,"value":425},": search issues mentioning the company or contact name",{"type":42,"tag":93,"props":427,"children":428},{},[429,434],{"type":42,"tag":62,"props":430,"children":431},{},[432],{"type":48,"value":433},"Coda\u002FNotion",{"type":48,"value":435},": search documents for the company or contact name",{"type":42,"tag":93,"props":437,"children":438},{},[439,444],{"type":42,"tag":62,"props":440,"children":441},{},[442],{"type":48,"value":443},"Granola",{"type":48,"value":445},": query meetings involving the contact name or company",{"type":42,"tag":93,"props":447,"children":448},{},[449,454],{"type":42,"tag":62,"props":450,"children":451},{},[452],{"type":48,"value":453},"Knowledge graph",{"type":48,"value":455},": search for the company or contact",{"type":42,"tag":51,"props":457,"children":458},{},[459,461,466],{"type":48,"value":460},"Fold the results into the relationship summary under a new ",{"type":42,"tag":62,"props":462,"children":463},{},[464],{"type":48,"value":465},"### Cross-platform context",{"type":48,"value":467}," section between \"Communication timeline\" and \"Open threads.\" Organize by source:",{"type":42,"tag":469,"props":470,"children":474},"pre",{"className":471,"code":473,"language":48},[472],"language-text","### Cross-platform context\n\n**Slack**\n- [Summary of relevant internal discussions, key decisions, sentiment]\n\n**Linear**\n- [Open issues or projects tied to this account, current status]\n\n**Coda\u002FNotion**\n- [Relevant docs — account plans, meeting notes, strategy docs]\n\n**Meeting transcripts**\n- [Key takeaways from recent meetings — action items, commitments made]\n",[475],{"type":42,"tag":139,"props":476,"children":478},{"__ignoreMap":477},"",[479],{"type":48,"value":473},{"type":42,"tag":51,"props":481,"children":482},{},[483,488],{"type":42,"tag":62,"props":484,"children":485},{},[486],{"type":48,"value":487},"If the user says no or skips",{"type":48,"value":489},", proceed with email-only data. Do not block on this — it's an enrichment step, not a prerequisite.",{"type":42,"tag":51,"props":491,"children":492},{},[493,498],{"type":42,"tag":62,"props":494,"children":495},{},[496],{"type":48,"value":497},"If no additional MCP tools are connected",{"type":48,"value":499},", skip this step entirely and don't mention it.",{"type":42,"tag":77,"props":501,"children":503},{"id":502},"step-3-build-the-relationship-summary",[504],{"type":48,"value":505},"Step 3: Build the relationship summary",{"type":42,"tag":51,"props":507,"children":508},{},[509],{"type":48,"value":510},"Present a structured overview:",{"type":42,"tag":469,"props":512,"children":515},{"className":513,"code":514,"language":48},[472],"## Relationship Summary: [Person\u002FCompany]\n\n### At a glance\n- **Last contact**: [date] — [who sent the last message, one-line summary]\n- **Total threads**: [X] in the last [time window]\n- **Meetings**: [X] past, [X] upcoming\n- **Engagement**: [Read receipt summary — e.g., \"They opened your last 3 emails within 2 hours\" or \"Your last email from March 15 hasn't been opened\"]\n- **Overall status**: [Active \u002F Going cold \u002F Needs follow-up]\n\n### Communication timeline\nA reverse-chronological summary of the key interactions — not every email, but the important beats of the relationship. For each:\n- Date, subject, who initiated, one-line summary of substance\n- Flag any unanswered emails (from either side)\n\n### Cross-platform context\n(Include this section only if the user opted in and additional MCP data was gathered.)\n- Slack: internal discussions, key decisions, sentiment\n- Project tracking: open issues, feature requests, escalations\n- Documents: account plans, meeting notes, strategy docs\n- Meeting transcripts: action items, commitments, key quotes\n\n### Open threads\nThreads with no resolution — questions asked but not answered, proposals sent without response, action items mentioned but not confirmed.\n\n### Engagement signals\nRead receipt data from Superhuman interpreted meaningfully:\n- Which emails were opened quickly (high interest)\n- Which were never opened (may need a different approach)\n- Patterns over time (engagement trending up or down?)\n\n### Suggested next steps\nBased on everything above, recommend 2-3 concrete actions:\n- \"Follow up on the pricing thread — they opened it 3 times but haven't replied\"\n- \"You have a meeting with them Thursday — here's context to prep\"\n- \"It's been 3 weeks since your last exchange — consider a check-in\"\n",[516],{"type":42,"tag":139,"props":517,"children":518},{"__ignoreMap":477},[519],{"type":48,"value":514},{"type":42,"tag":77,"props":521,"children":523},{"id":522},"step-4-offer-actions",[524],{"type":48,"value":525},"Step 4: Offer actions",{"type":42,"tag":51,"props":527,"children":528},{},[529],{"type":48,"value":530},"After presenting the summary, offer to:",{"type":42,"tag":89,"props":532,"children":533},{},[534,552,568,582,604],{"type":42,"tag":93,"props":535,"children":536},{},[537,542,544,550],{"type":42,"tag":62,"props":538,"children":539},{},[540],{"type":48,"value":541},"Draft a follow-up email",{"type":48,"value":543}," — Uses ",{"type":42,"tag":139,"props":545,"children":547},{"className":546},[],[548],{"type":48,"value":549},"Superhuman_Mail.create_or_update_draft",{"type":48,"value":551}," with context-rich instructions",{"type":42,"tag":93,"props":553,"children":554},{},[555,560,561,566],{"type":42,"tag":62,"props":556,"children":557},{},[558],{"type":48,"value":559},"Pull up a specific thread",{"type":48,"value":543},{"type":42,"tag":139,"props":562,"children":564},{"className":563},[],[565],{"type":48,"value":273},{"type":48,"value":567}," for deeper reading",{"type":42,"tag":93,"props":569,"children":570},{},[571,576,577],{"type":42,"tag":62,"props":572,"children":573},{},[574],{"type":48,"value":575},"Check read receipts on a specific email",{"type":48,"value":543},{"type":42,"tag":139,"props":578,"children":580},{"className":579},[],[581],{"type":48,"value":255},{"type":42,"tag":93,"props":583,"children":584},{},[585,590,591,597,598],{"type":42,"tag":62,"props":586,"children":587},{},[588],{"type":48,"value":589},"Schedule a meeting",{"type":48,"value":543},{"type":42,"tag":139,"props":592,"children":594},{"className":593},[],[595],{"type":48,"value":596},"Superhuman_Mail.get_availability",{"type":48,"value":195},{"type":42,"tag":139,"props":599,"children":601},{"className":600},[],[602],{"type":48,"value":603},"Superhuman_Mail.create_or_update_event",{"type":42,"tag":93,"props":605,"children":606},{},[607,612],{"type":42,"tag":62,"props":608,"children":609},{},[610],{"type":48,"value":611},"Search other platforms",{"type":48,"value":613}," — If the user didn't opt in to cross-platform context during Step 2b but wants to dig deeper, offer to search Slack, Linear, Coda, Granola, or any other connected MCP tools on demand",{"type":42,"tag":70,"props":615,"children":617},{"id":616},"multi-contact-company-wide-view",[618],{"type":48,"value":619},"Multi-contact \u002F company-wide view",{"type":42,"tag":51,"props":621,"children":622},{},[623],{"type":48,"value":624},"If the user asks about a company rather than a single person, group the summary by contact within the company. Highlight:",{"type":42,"tag":89,"props":626,"children":627},{},[628,633,638],{"type":42,"tag":93,"props":629,"children":630},{},[631],{"type":48,"value":632},"Who the user communicates with most",{"type":42,"tag":93,"props":634,"children":635},{},[636],{"type":48,"value":637},"Any contacts who've gone quiet",{"type":42,"tag":93,"props":639,"children":640},{},[641],{"type":48,"value":642},"The overall relationship health across all touchpoints",{"type":42,"tag":70,"props":644,"children":646},{"id":645},"important-guidelines",[647],{"type":48,"value":648},"Important guidelines",{"type":42,"tag":89,"props":650,"children":651},{},[652,662,672,682],{"type":42,"tag":93,"props":653,"children":654},{},[655,660],{"type":42,"tag":62,"props":656,"children":657},{},[658],{"type":48,"value":659},"Be specific, not vague.",{"type":48,"value":661}," \"You last emailed them on March 15 about the API integration timeline\" is useful. \"You've been in contact recently\" is not.",{"type":42,"tag":93,"props":663,"children":664},{},[665,670],{"type":42,"tag":62,"props":666,"children":667},{},[668],{"type":48,"value":669},"Read receipts are signals, not certainties.",{"type":48,"value":671}," Present them as engagement indicators, not proof of intent. Some email clients block read receipts.",{"type":42,"tag":93,"props":673,"children":674},{},[675,680],{"type":42,"tag":62,"props":676,"children":677},{},[678],{"type":48,"value":679},"Respect sensitivity.",{"type":48,"value":681}," Deal and relationship data is inherently sensitive. Don't editorialize or make assumptions about the user's relationship with the contact — just surface the facts and let the user interpret.",{"type":42,"tag":93,"props":683,"children":684},{},[685,690],{"type":42,"tag":62,"props":686,"children":687},{},[688],{"type":48,"value":689},"Time decay matters.",{"type":48,"value":691}," A thread from yesterday is more actionable than one from 2 months ago. Weight your \"suggested next steps\" toward recent, open threads.",{"items":693,"total":814},[694,712,728,740,760,782,802],{"slug":695,"name":695,"fn":696,"description":697,"org":698,"tags":699,"stars":25,"repoUrl":26,"updatedAt":27},"accessibility-and-inclusive-visualization","make data visualizations accessible","Make data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[700,703,706,709],{"name":701,"slug":702,"type":15},"Accessibility","accessibility",{"name":704,"slug":705,"type":15},"Charts","charts",{"name":707,"slug":708,"type":15},"Data Visualization","data-visualization",{"name":710,"slug":711,"type":15},"Design","design",{"slug":713,"name":713,"fn":714,"description":715,"org":716,"tags":717,"stars":25,"repoUrl":26,"updatedAt":727},"agent-browser","automate browser interactions for agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[718,721,724],{"name":719,"slug":720,"type":15},"Agents","agents",{"name":722,"slug":723,"type":15},"Browser Automation","browser-automation",{"name":725,"slug":726,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":729,"name":729,"fn":730,"description":731,"org":732,"tags":733,"stars":25,"repoUrl":26,"updatedAt":739},"agent-browser-verify","verify dev server output with automated browser","Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass\u002Ffail before continuing.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[734,735,738],{"name":722,"slug":723,"type":15},{"name":736,"slug":737,"type":15},"Local Development","local-development",{"name":725,"slug":726,"type":15},"2026-04-06T18:41:17.526867",{"slug":741,"name":741,"fn":742,"description":743,"org":744,"tags":745,"stars":25,"repoUrl":26,"updatedAt":759},"agents-sdk","build AI agents on Cloudflare Workers","Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[746,747,750,753,756],{"name":719,"slug":720,"type":15},{"name":748,"slug":749,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":751,"slug":752,"type":15},"SDK","sdk",{"name":754,"slug":755,"type":15},"Serverless","serverless",{"name":757,"slug":758,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":761,"name":761,"fn":762,"description":763,"org":764,"tags":765,"stars":25,"repoUrl":26,"updatedAt":781},"ai-elements","build chat UIs with AI Elements","AI Elements component library guidance — pre-built React components for AI interfaces built on shadcn\u002Fui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[766,769,772,775,778],{"name":767,"slug":768,"type":15},"Frontend","frontend",{"name":770,"slug":771,"type":15},"React","react",{"name":773,"slug":774,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":776,"slug":777,"type":15},"UI Components","ui-components",{"name":779,"slug":780,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":783,"name":783,"fn":784,"description":785,"org":786,"tags":787,"stars":25,"repoUrl":26,"updatedAt":801},"ai-gateway","configure Vercel AI Gateway","Vercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[788,791,794,797,800],{"name":789,"slug":790,"type":15},"AI Infrastructure","ai-infrastructure",{"name":792,"slug":793,"type":15},"Cost Optimization","cost-optimization",{"name":795,"slug":796,"type":15},"LLM","llm",{"name":798,"slug":799,"type":15},"Performance","performance",{"name":779,"slug":780,"type":15},"2026-04-06T18:40:44.377464",{"slug":803,"name":803,"fn":804,"description":805,"org":806,"tags":807,"stars":25,"repoUrl":26,"updatedAt":813},"ai-generation-persistence","implement persistence patterns for AI generations","AI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[808,809,812],{"name":792,"slug":793,"type":15},{"name":810,"slug":811,"type":15},"Database","database",{"name":795,"slug":796,"type":15},"2026-04-06T18:41:08.513425",600,{"items":816,"total":1013},[817,838,861,878,894,911,930,942,956,970,982,997],{"slug":818,"name":818,"fn":819,"description":820,"org":821,"tags":822,"stars":835,"repoUrl":836,"updatedAt":837},"prior-auth-packet-builder","build healthcare prior authorization packets","Build a concise prior authorization packet from local case files and payer policy docs.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[823,826,829,832],{"name":824,"slug":825,"type":15},"Documents","documents",{"name":827,"slug":828,"type":15},"Healthcare","healthcare",{"name":830,"slug":831,"type":15},"Insurance","insurance",{"name":833,"slug":834,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":839,"name":839,"fn":840,"description":841,"org":842,"tags":843,"stars":858,"repoUrl":859,"updatedAt":860},"aspnet-core","build ASP.NET Core web applications","Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[844,847,849,852,855],{"name":845,"slug":846,"type":15},".NET","dotnet",{"name":848,"slug":839,"type":15},"ASP.NET Core",{"name":850,"slug":851,"type":15},"Blazor","blazor",{"name":853,"slug":854,"type":15},"C#","csharp",{"name":856,"slug":857,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":862,"name":862,"fn":863,"description":864,"org":865,"tags":866,"stars":858,"repoUrl":859,"updatedAt":877},"chatgpt-apps","build ChatGPT Apps SDK applications","Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[867,870,873,876],{"name":868,"slug":869,"type":15},"Apps SDK","apps-sdk",{"name":871,"slug":872,"type":15},"ChatGPT","chatgpt",{"name":874,"slug":875,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":879,"name":879,"fn":880,"description":881,"org":882,"tags":883,"stars":858,"repoUrl":859,"updatedAt":893},"cli-creator","build CLIs from API docs","Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read\u002Fwrite commands, return stable JSON, manage auth, and pair with a companion skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[884,887,890],{"name":885,"slug":886,"type":15},"API Development","api-development",{"name":888,"slug":889,"type":15},"CLI","cli",{"name":891,"slug":892,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":895,"name":895,"fn":896,"description":897,"org":898,"tags":899,"stars":858,"repoUrl":859,"updatedAt":910},"cloudflare-deploy","deploy projects to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[900,903,906,907],{"name":901,"slug":902,"type":15},"Cloudflare","cloudflare",{"name":904,"slug":905,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":748,"slug":749,"type":15},{"name":908,"slug":909,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":912,"name":912,"fn":913,"description":914,"org":915,"tags":916,"stars":858,"repoUrl":859,"updatedAt":929},"define-goal","define and set measurable project goals","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[917,920,923,926],{"name":918,"slug":919,"type":15},"Productivity","productivity",{"name":921,"slug":922,"type":15},"Project Management","project-management",{"name":924,"slug":925,"type":15},"Strategy","strategy",{"name":927,"slug":928,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":931,"name":931,"fn":932,"description":933,"org":934,"tags":935,"stars":858,"repoUrl":859,"updatedAt":941},"figma","translate Figma designs into code","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[936,937,939,940],{"name":710,"slug":711,"type":15},{"name":938,"slug":931,"type":15},"Figma",{"name":767,"slug":768,"type":15},{"name":874,"slug":875,"type":15},"2026-04-12T05:06:47.939943",{"slug":943,"name":943,"fn":944,"description":945,"org":946,"tags":947,"stars":858,"repoUrl":859,"updatedAt":955},"figma-code-connect-components","connect Figma designs to code components","Connects Figma design components to code components using Code Connect mapping tools. Use when user says \"code connect\", \"connect this component to code\", \"map this component\", \"link component to code\", \"create code connect mapping\", or wants to establish mappings between Figma designs and code implementations. For canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[948,949,952,953,954],{"name":710,"slug":711,"type":15},{"name":950,"slug":951,"type":15},"Design System","design-system",{"name":938,"slug":931,"type":15},{"name":767,"slug":768,"type":15},{"name":776,"slug":777,"type":15},"2026-05-10T05:59:52.971881",{"slug":957,"name":957,"fn":958,"description":959,"org":960,"tags":961,"stars":858,"repoUrl":859,"updatedAt":969},"figma-create-design-system-rules","generate design system rules from Figma","Generates custom design system rules for the user's codebase. Use when user says \"create design system rules\", \"generate rules for my project\", \"set up design rules\", \"customize design system guidelines\", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[962,963,964,967,968],{"name":710,"slug":711,"type":15},{"name":950,"slug":951,"type":15},{"name":965,"slug":966,"type":15},"Documentation","documentation",{"name":938,"slug":931,"type":15},{"name":767,"slug":768,"type":15},"2026-05-16T06:07:47.821474",{"slug":971,"name":971,"fn":972,"description":973,"org":974,"tags":975,"stars":858,"repoUrl":859,"updatedAt":981},"figma-implement-design","translate Figma designs into application code","Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions \"implement design\", \"generate code\", \"implement component\", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[976,977,978,979,980],{"name":710,"slug":711,"type":15},{"name":938,"slug":931,"type":15},{"name":767,"slug":768,"type":15},{"name":776,"slug":777,"type":15},{"name":856,"slug":857,"type":15},"2026-05-16T06:07:40.583615",{"slug":983,"name":983,"fn":984,"description":985,"org":986,"tags":987,"stars":858,"repoUrl":859,"updatedAt":996},"hatch-pet","create animated pets for Codex","Create, repair, validate, visually QA, and package Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual references. Use when a user wants a lightweight-worker Codex pet workflow, a non-pixel custom pet style, a prospect or company mascot pet, or a full 8x9 animated pet atlas with transparent unused cells, QA contact sheets, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[988,991,992,995],{"name":989,"slug":990,"type":15},"Animation","animation",{"name":891,"slug":892,"type":15},{"name":993,"slug":994,"type":15},"Creative","creative",{"name":710,"slug":711,"type":15},"2026-05-02T05:31:48.48485",{"slug":998,"name":998,"fn":999,"description":1000,"org":1001,"tags":1002,"stars":858,"repoUrl":859,"updatedAt":1012},"imagegen","generate and edit raster images","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1003,1004,1005,1008,1011],{"name":993,"slug":994,"type":15},{"name":710,"slug":711,"type":15},{"name":1006,"slug":1007,"type":15},"Image Generation","image-generation",{"name":1009,"slug":1010,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]