27 feedback emails: 12 requests, 9 bugs, 6 praise
27 customer emails this week. The most asked-for feature is two-way calendar sync (5 customers). One bug report describes duplicate invoices and has no reply yet.
Every Friday: the customer feedback that arrived by email this week, sorted into feature requests, bugs and praise, with short quotes.
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
27 customer emails this week. The most asked-for feature is two-way calendar sync (5 customers). One bug report describes duplicate invoices and has no reply yet.
Not every customer opens a ticket. Plenty reply to an onboarding email, write to the founder directly, or answer a newsletter with two paragraphs about what annoys them. That feedback lands in Gmail and stays there, out of reach of the product team and of whoever runs the support queue.
Once a week the agent searches the inboxes or aliases you name, skips newsletters and automated mail, and sorts what customers wrote into feature requests, bugs and praise. Each item keeps a short quote and the sender's company, so a PM knows who to follow up with.
Call users.messages.list with a q such as newer_than:7d (to:feedback@example.com OR to:hello@example.com OR label:customer-feedback) -category:promotions -category:social -from:me, paging with pageToken.
Fetch each message with users.messages.get (format: "full"), take the plain text part and drop quoted replies and signatures. Skip auto-replies, receipts and anything with a List-Unsubscribe header.
Sort each email into feature request, bug report, praise or other. Merge emails that ask for the same thing and count how many customers asked for it.
Use users.threads.get to see whether someone on your side already answered in the thread, and note the sender's company from their email domain rather than their address.
Counts per group, then items with the most customers first, each with a quote under 30 words. Anything that sounds like an outage or a billing error goes to the top, whatever its count.
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-customer-feedback-digest/install | shAsk Claude Code:
promptRun the gmail-customer-feedback-digest skillOr paste the prompt instead of installing:
promptSearch my Gmail for customer feedback from the last 7 days: mail to my feedback and hello addresses or labeled customer-feedback, leaving out promotions, social, newsletters (anything with List-Unsubscribe), auto-replies and my own messages. Read the new text of each email, not the quoted part. Sort them into feature requests, bug reports, praise and other; merge emails asking for the same thing and count customers per item. For each item give me a short quote, the sender's company from their domain, and whether we already replied in the thread. Put anything that sounds like an outage or a billing error first.Fridays at 15:00, from cron on any machine where Claude Code is signed in:
crontab0 15 * * 5 claude -p "Run the gmail-customer-feedback-digest 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 report card. How setup works
SKILL.md---
name: gmail-customer-feedback-digest
description: "Every Friday: the customer feedback that arrived by email this week, sorted into feature requests, bugs and praise, with short quotes. Use when the user asks for this, or when it runs on a schedule."
---
# Gmail customer feedback digest
Every Friday: the customer feedback that arrived by email this week, sorted into feature requests, bugs and praise, with short quotes.
Not every customer opens a ticket. Plenty reply to an onboarding email, write to the founder directly, or answer a newsletter with two paragraphs about what annoys them. That feedback lands in Gmail and stays there, out of reach of the product team and of whoever runs the support queue.
Once a week the agent searches the inboxes or aliases you name, skips newsletters and automated mail, and sorts what customers wrote into feature requests, bugs and praise. Each item keeps a short quote and the sender's company, so a PM knows who to follow up with.
## 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
- Read access to the Gmail inbox or shared alias where feedback arrives: a Gmail connector, or an OAuth client with the `gmail.readonly` scope.
- The addresses or label that collect feedback (for example `feedback@` or a `customer-feedback` label).
If something is missing, say what and stop; do not invent numbers.
### Steps
1. **Search the week's mail** (Gmail): Call `users.messages.list` with a `q` such as `newer_than:7d (to:feedback@example.com OR to:hello@example.com OR label:customer-feedback) -category:promotions -category:social -from:me`, paging with `pageToken`.
2. **Read and filter** (Gmail): Fetch each message with `users.messages.get` (`format: "full"`), take the plain text part and drop quoted replies and signatures. Skip auto-replies, receipts and anything with a `List-Unsubscribe` header.
3. **Classify and merge**: Sort each email into feature request, bug report, praise or other. Merge emails that ask for the same thing and count how many customers asked for it.
4. **Check for replies** (Gmail): Use `users.threads.get` to see whether someone on your side already answered in the thread, and note the sender's company from their email domain rather than their address.
5. **Write the digest**: Counts per group, then items with the most customers first, each with a quote under 30 words. Anything that sounds like an outage or a billing error goes to the top, whatever its count.
## Route B: the browser
### What you need
- Signed in to Google in the mailbox that receives feedback, or an account the shared alias is delegated to; delegated mailboxes open from the account menu.
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 week**: Pick the account or shared mailbox where feedback arrives. In the search box type `newer_than:7d (to:feedback@example.com OR to:hello@example.com OR label:customer-feedback) -category:promotions -category:social -from:me` and press Enter.
2. **Open and read each thread**: Open each result, read the newest message from the customer only (click the three dots to expand trimmed quoted text only when the new part is unclear). Skip auto-replies, receipts and newsletters, which show an **Unsubscribe** link next to the sender.
3. **Classify and merge**: Sort each email into feature request, bug report, praise or other. Merge emails that ask for the same thing and count the customers behind each item.
4. **Check for a reply**: In the same thread view, see whether a message from your side follows the customer's. Take the company from the sender's domain (hover over the name to see the address), not from the signature.
5. **Write the digest**: Counts per group, then items with the most customers first, each with a quote under 30 words and the company. Anything that sounds like an outage or a billing error goes to the top.
Note: Gmail shows 50 threads a page by default, so a busy week means paging. The `label:` operator only matches labels on this account; a shared alias forwarded into several inboxes needs the search run in each.
## The report
- **Counts** of feature requests, bug reports and praise this week.
- **Grouped items**, most customers first, with a short quote and the sender's company.
- **Unanswered**: feedback nobody on your side has replied to.
- Bugs that sound like an outage or a billing error, at the top.
## 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-customer-feedback-digest/<date of this run, e.g. 2026-10-16>",
"item_key": "gmail-customer-feedback-digest",
"project": "Acme",
"source": "Gmail customer feedback digest skill",
"kind": "update",
"title": "27 feedback emails: 12 requests, 9 bugs, 6 praise",
"summary": "**27** customer emails this week. The most asked-for feature is **two-way calendar sync** (5 customers). One bug report describes duplicate invoices and has no reply yet.",
"widget": [
{
"type": "Grid",
"props": {
"columns": 3
},
"children": [
{
"type": "Stat",
"props": {
"label": "Feature requests",
"value": 12
}
},
{
"type": "Stat",
"props": {
"label": "Bug reports",
"value": 9,
"tone": "warn"
}
},
{
"type": "Stat",
"props": {
"label": "Praise",
"value": 6,
"tone": "ok"
}
}
]
},
{
"type": "Table",
"props": {
"columns": [
"Type",
"What they wrote about",
"Customers",
"Replied"
],
"align": [
"left",
"left",
"right",
"right"
],
"rows": [
[
"Bug",
"Duplicate invoices after a plan change",
1,
"0 of 1"
],
[
"Request",
"Two-way calendar sync",
5,
"3 of 5"
],
[
"Bug",
"Mobile app logs out every day",
4,
"2 of 4"
],
[
"Praise",
"The new onboarding checklist",
4,
"4 of 4"
],
[
"Request",
"Export reports to PDF",
3,
"1 of 3"
],
[
"Bug",
"Reminders show the wrong time zone",
3,
"3 of 3"
],
[
"Request",
"More granular user roles",
2,
"2 of 2"
],
[
"Request",
"Dark mode",
2,
"0 of 2"
],
[
"Praise",
"A support reply from Aisha",
2,
"2 of 2"
],
[
"Bug",
"Search misses archived items",
1,
"1 of 1"
]
]
}
},
{
"type": "Callout",
"props": {
"text": "\"We were charged twice after upgrading and both invoices went to our accountant.\" Lucerne Publishing, no reply yet.",
"tone": "bad"
}
}
]
}
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: Fridays at 15:00 (`0 15 * * 5`). From cron, with the agent signed in on that machine:
```bash
0 15 * * 5 claude -p "Run the gmail-customer-feedback-digest 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-customer-feedback-digest#schedule
Source: https://briefkin.dev/skills/gmail-customer-feedback-digest
Read access to the Gmail inbox or shared alias where feedback arrives: a Gmail connector, or an OAuth client with the gmail.readonly scope.
The addresses or label that collect feedback (for example feedback@ or a customer-feedback label).
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.
It reads mailboxes it is signed in to. If feedback goes to a Google Group, have the group deliver to a mailbox the agent can read, or make that account a member and search with list:feedback@example.com.
No. The card names the customer's company from the email domain and quotes a sentence or two; the full email stays in Gmail. Drop the company as well if your board is shared widely.
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 report card, 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.