--- name: gmail-emails-waiting-on-reply description: "Weekday afternoons: Gmail threads where someone else wrote last over two days ago, ranked by how long they have waited, with an offer to draft replies. Use when the user asks for this, or when it runs on a schedule." --- # Gmail threads waiting on your reply Weekday afternoons: Gmail threads where someone else wrote last over two days ago, ranked by how long they have waited, with an offer to draft replies. The emails that hurt are not the ones you decided to ignore. They are the ones you read on your phone, meant to answer properly, and then lost below the fold. Two days later the sender has followed up, or quietly given up. This skill looks for exactly that shape: a thread where the last message is from someone else, a real person, and older than 48 hours. It ranks them by how long they have waited and offers to draft replies into each thread for you to edit and send. ## Two ways to get the data Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used. ## Route A: API or MCP server ### What you need - A Gmail connector or MCP server, or a Google OAuth client with `gmail.readonly`, to find the threads. - The `gmail.compose` scope as well if the agent should write drafts into them. If something is missing, say what and stop; do not invent numbers. ### Steps 1. **Search for candidates** (Gmail): Call `users.threads.list` with `q: "in:inbox older_than:2d newer_than:30d -category:promotions -category:social -category:forums -category:updates"`. A thread matches if any of its messages fits, so the real test is the next step. 2. **Check who wrote last** (Gmail): For each thread, `users.threads.get` with `format: metadata` and take the last message. Keep the thread if its `From` is not you (your address from `users.getProfile`, aliases from `users.settings.sendAs.list`) and its `internalDate` is more than 48 hours old. 3. **Drop automated mail**: Skip messages with a `List-Unsubscribe` header, senders like `noreply@` or `notifications@`, calendar invitations, and threads where you are only in Cc. 4. **Rank and ask** (Gmail): Order by hours waiting, read the last message to state the ask in one line, and ask which ones to draft. Drafts go into the thread with `users.drafts.create` and the thread's `threadId`; nothing is sent. ## Route B: the browser ### What you need - Signed in to Gmail in the browser, with Drafts allowed (it is by default). The person checks each draft in Drafts before sending. If something is missing, say what and stop; do not invent numbers. ### Steps Start at https://mail.google.com/. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears. 1. **Search the candidates**: In the search box type `in:inbox older_than:2d newer_than:30d -category:promotions -category:social -category:forums -category:updates` and press Enter. The list shows the thread's last sender and the date, which is enough to skip most threads. 2. **Check who wrote last**: Open each thread where the last sender shown is not you and the date is more than two days old. Confirm the final message is from someone else and that you are in **To**, not Cc (open **Show details** under the sender). Your own aliases are listed under **Settings > See all settings > Accounts > Send mail as**. 3. **Drop the automated ones**: Skip anything with an **Unsubscribe** link by the sender name, `noreply` or `notifications` addresses, and calendar invitations. 4. **Rank and offer drafts**: Read the last message and write the ask in one line, order by days waiting and ask which to answer. On a yes, click **Reply** inside the thread, write the draft and click away; Gmail saves it to Drafts in that thread. Never click **Send**. Note: The search returns threads where any message matches the dates, so the agent has to open borderline threads to be sure. Drafts written in the browser land in the thread the same way the API route's do; check them under Drafts before sending. ## The report - How many threads are waiting on you, and the age of the oldest. - Per thread: sender, subject, the ask in one line, days waiting. - The question: draft replies for all, some or none. ## Post it to Briefkin When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on. ```bash [ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \ -H "authorization: Bearer $BRIEFKIN_TOKEN" \ -H "content-type: application/json" \ -d @- <<'JSON' { "v": 1, "event_id": "gmail-emails-waiting-on-reply/", "item_key": "gmail-emails-waiting-on-reply", "project": "Inbox", "source": "Gmail threads waiting on your reply skill", "kind": "action", "title": "4 threads waiting on your reply, oldest 6 days", "summary": "**4** people are waiting on you. Hannah Cole asked about pilot pricing **6 days** ago.", "action": { "request": "Want me to draft replies? Drafts go into each thread and nothing is sent.", "options": [ "Draft all 4", "Draft the 2 oldest", "Remind me tomorrow", "They are handled" ] }, "widget": { "type": "Table", "props": { "columns": [ "From", "Subject", "Waiting" ], "align": [ "left", "left", "right" ], "rows": [ [ "Hannah Cole", "Pilot pricing for 40 seats", "6 days" ], [ "Marco Bianchi", "Podcast interview, November dates", "4 days" ], [ "Aisha Karim", "Reference check for J. Park", "3 days" ], [ "Tom Reyes", "Can we move our 1:1?", "2 days" ] ] } } } JSON ``` Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report. ## Run it on a schedule Suggested: Weekdays at 16:00 (`0 16 * * 1-5`). From cron, with the agent signed in on that machine: ```bash 0 16 * * 1-5 claude -p "Run the gmail-emails-waiting-on-reply skill" # Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run ``` Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/gmail-emails-waiting-on-reply#schedule Source: https://briefkin.dev/skills/gmail-emails-waiting-on-reply