5 emails you sent got no reply
Want follow-up drafts? Each goes into its original thread for you to edit; nothing is sent.
5 threads where you wrote last are still quiet. The Q1 pilot proposal to Northwind has waited 6 days.
Weekday mornings: Gmail threads where you wrote last, 3 or more days ago, to someone who has not replied, with an offer to draft follow-ups.
Reads
You get
The card on the right is a sample. Yours shows your own numbers and updates in place every run.
What lands on your board
Want follow-up drafts? Each goes into its original thread for you to edit; nothing is sent.
5 threads where you wrote last are still quiet. The Q1 pilot proposal to Northwind has waited 6 days.
Proposals, intros, invoice reminders and "does Thursday work?" all share a failure mode: you send them, the other side gets busy, and nothing happens. Gmail's nudges catch some of these, but only when you open the inbox, and never in a list you can work through.
This skill looks at your sent mail from the last three weeks and keeps the threads where you still have the last word after three days. It drops the ones that did not expect an answer, ranks the rest by how much they matter, and asks which to follow up. Follow-ups are written as drafts in the original threads; nothing is sent.
Call users.threads.list with q: "in:sent older_than:3d newer_than:21d". A match only means one of your messages fits; who wrote last is checked next.
users.threads.get with format: metadata and metadataHeaders From, To, Cc and Subject. Keep the thread when its last message is from you (your address and users.settings.sendAs.list aliases) and was sent 3 or more days ago.
Skip messages only to yourself or your own domain (unless you want internal follow-ups), closing notes such as "thanks, all set", calendar replies, and automated sends. Keep messages that ask a question, request a decision or carry a proposal or invoice.
Rank by what is at stake (proposal, payment, intro, scheduling), then days waiting. Show up to 10 with recipient, subject and the ask in one line, and ask which to follow up. Drafts go into each thread with users.drafts.create and its threadId.
With BRIEFKIN_TOKEN set, the agent sends the result as one card that updates in place every run. Without it, you get the report in the chat.
Pick your agent, where the data comes from and how to schedule it; the commands below follow.
One command. It puts the SKILL.md in ~/.claude/skills and in ~/.agents/skills, which Codex, Cursor, Gemini CLI, Copilot CLI and OpenCode read too.
shellcurl -fsSL https://briefkin.dev/skills/gmail-sent-emails-no-reply/install | shAsk Claude Code:
promptRun the gmail-sent-emails-no-reply skillOr paste the prompt instead of installing:
promptSearch my Gmail for threads matching in:sent older_than:3d newer_than:21d. Keep only threads where the last message is from me (my address or a send-as alias) and is at least 3 days old. Drop messages only to myself, closing notes like "thanks, all set", calendar replies and automated mail; keep ones that ask a question, request a decision, or carry a proposal or invoice. Rank them by what is at stake, then by days waiting, and show up to 10 with recipient, subject, what I asked for in one line and days since I sent it. Ask me which ones to follow up, and only then create drafts in the original threads. Never send anything.Weekdays at 10:00, from cron on any machine where Claude Code is signed in:
crontab0 10 * * 1-5 claude -p "Run the gmail-sent-emails-no-reply skill"Add it with crontab -e. A laptop asleep at that time runs it when it wakes if you use launchd or Task Scheduler instead; GitHub Actions works for the API route.
Connect Briefkin once with curl -fsSL https://briefkin.dev/install | sh and every run lands on your board as a question for you. How setup works
SKILL.md---
name: gmail-sent-emails-no-reply
description: "Weekday mornings: Gmail threads where you wrote last, 3 or more days ago, to someone who has not replied, with an offer to draft follow-ups. Use when the user asks for this, or when it runs on a schedule."
---
# Gmail sent emails with no reply
Weekday mornings: Gmail threads where you wrote last, 3 or more days ago, to someone who has not replied, with an offer to draft follow-ups.
Proposals, intros, invoice reminders and "does Thursday work?" all share a failure mode: you send them, the other side gets busy, and nothing happens. Gmail's nudges catch some of these, but only when you open the inbox, and never in a list you can work through.
This skill looks at your sent mail from the last three weeks and keeps the threads where you still have the last word after three days. It drops the ones that did not expect an answer, ranks the rest by how much they matter, and asks which to follow up. Follow-ups are written as drafts in the original threads; nothing is sent.
## 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 Gmail API OAuth with `gmail.readonly`, to read sent threads.
- The `gmail.compose` scope as well if the agent should leave follow-up drafts.
If something is missing, say what and stop; do not invent numbers.
### Steps
1. **Find sent threads** (Gmail): Call `users.threads.list` with `q: "in:sent older_than:3d newer_than:21d"`. A match only means one of your messages fits; who wrote last is checked next.
2. **Keep threads where you wrote last** (Gmail): `users.threads.get` with `format: metadata` and `metadataHeaders` From, To, Cc and Subject. Keep the thread when its last message is from you (your address and `users.settings.sendAs.list` aliases) and was sent 3 or more days ago.
3. **Drop what needs no answer**: Skip messages only to yourself or your own domain (unless you want internal follow-ups), closing notes such as "thanks, all set", calendar replies, and automated sends. Keep messages that ask a question, request a decision or carry a proposal or invoice.
4. **Rank and ask**: Rank by what is at stake (proposal, payment, intro, scheduling), then days waiting. Show up to 10 with recipient, subject and the ask in one line, and ask which to follow up. Drafts go into each thread with `users.drafts.create` and its `threadId`.
## Route B: the browser
### What you need
- Signed in to the Gmail or Google Workspace account in the browser, with Conversation view turned on.
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 sent mail**: In the search box at the top, type `in:sent older_than:3d newer_than:21d` and press Enter. Conversation view must be on (Settings > See all settings > Conversation view) so each result is a thread.
2. **Keep threads where you wrote last**: Open each thread and check the last message: keep it when it is from you (or one of your Send mail as addresses) and at least 3 days old. Page through with the arrows at the top right; Gmail shows 50 threads a page by default.
3. **Drop what needs no answer**: Skip messages only to yourself or your own domain, closing notes such as "thanks, all set", calendar replies and automated sends. Keep the ones that ask a question, request a decision or carry a proposal or invoice.
4. **Rank, ask, then draft**: Rank by what is at stake, then days waiting, and show up to 10 with recipient, subject and the ask. After the person picks, open each chosen thread, click **Reply**, write the follow-up and close it; Gmail keeps it in Drafts. Never click Send.
Note: Gmail's search does not know who wrote last, so every result has to be opened; three weeks of sent mail is usually 50 to 200 threads, which is slow but fine once a day. Replies that arrived as a new email rather than in the thread will be missed either way.
## The report
- **Count** of sent emails still without a reply, and the oldest.
- **Per thread**: recipient, subject, what you asked for, days since you sent it.
- The question: which to follow up, with drafts on request.
## 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-sent-emails-no-reply/<date of this run, e.g. 2026-10-16>",
"item_key": "gmail-sent-emails-no-reply",
"project": "Inbox",
"source": "Gmail sent emails with no reply skill",
"kind": "action",
"title": "5 emails you sent got no reply",
"summary": "**5 threads** where you wrote last are still quiet. The Q1 pilot proposal to Northwind has waited **6 days**.",
"action": {
"request": "Want follow-up drafts? Each goes into its original thread for you to edit; nothing is sent.",
"options": [
"Draft all 5",
"Draft the top 3",
"Remind me Monday",
"Let them go"
]
},
"widget": {
"type": "Table",
"props": {
"columns": [
"To",
"Subject",
"Sent"
],
"align": [
"left",
"left",
"right"
],
"rows": [
[
"Maya Chen, Northwind",
"Proposal for the Q1 pilot",
"6 days ago"
],
[
"Accounts payable, Bluepeak",
"Invoice 1042 is 10 days overdue",
"5 days ago"
],
[
"Jon Weber, Halcyon",
"Answers to your pricing questions",
"4 days ago"
],
[
"Ben Ito, Initech",
"Does Thursday at 3 work?",
"3 days ago"
],
[
"Rita Alvarez",
"Intro: you and Sam from Globex",
"3 days ago"
]
]
}
}
}
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 10:00 (`0 10 * * 1-5`). From cron, with the agent signed in on that machine:
```bash
0 10 * * 1-5 claude -p "Run the gmail-sent-emails-no-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-sent-emails-no-reply#schedule
Source: https://briefkin.dev/skills/gmail-sent-emails-no-reply
A Gmail connector or MCP server, or Gmail API OAuth with gmail.readonly, to read sent threads.
The gmail.compose scope as well if the agent should leave follow-up drafts.
https://gmailmcp.googleapis.com/mcp/v1, in developer preview with the other Google Workspace MCP servers. It needs an OAuth client in Google Cloud set up for an AI agent (setup).gmail.readonly scope, and store GMAIL_CLIENT_ID, GMAIL_CLIENT_SECRET and GMAIL_REFRESH_TOKEN. Publish the OAuth app (or make it Internal in Workspace): refresh tokens from an app left in Testing expire after seven days.gmail.readonly can search and read but not send, delete or relabel; add gmail.compose only if you want the agent to leave drafts.
A reply from another address still lands in the same thread when it keeps the subject and references, so the thread drops out of the list. A reply sent as a brand-new email does not; if that happens often with one contact, add their other address to the skill so it checks for it.
After three weeks most unanswered emails are either dead or need a fresh start rather than a nudge. Change newer_than:21d if your sales cycle is slower, and change older_than:3d together with the 3-day check for faster follow-ups.
No. The skill runs with your own agent and gives you the report in the chat. With a Briefkin token set, each run also posts it to your board as a asks you, so you can glance at it instead of asking again.
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Windsurf and Amp all read SKILL.md files. The install command puts it in ~/.claude/skills and ~/.agents/skills, where they look. ChatGPT, the Claude app and Grok take the prompt instead. Pick your agent under "Install and run it" and the commands change to match.
Yes. Switch the data source to "Your browser" and the steps change to the Gmail pages themselves: the agent opens mail.google.com in a browser you are signed in to and reads the numbers off the page. Claude Code, Codex, Cursor, Claude app and ChatGPT can drive a browser out of the box; Gemini CLI, Copilot CLI and OpenCode need a Playwright or Chrome DevTools MCP server first. It is slower than the API and needs you signed in, so it suits a report you run by hand or from a scheduler on your own computer.
Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.
Free during the open beta. No card.