23 unread: 4 need a reply
4 emails need a reply today, one with a noon deadline. 7 are worth reading later and 12 can wait or go.
Weekday mornings: every unread Outlook email since yesterday, sorted into reply now, read later and ignore, one line each with a link.
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
4 emails need a reply today, one with a noon deadline. 7 are worth reading later and 12 can wait or go.
Thirty unread emails at 8:00 are rarely thirty decisions. Most are notifications, newsletters and threads you are copied on; three or four actually need you. Finding those means opening everything, which is how a morning disappears.
The agent reads the subject, sender and preview of each unread message through Microsoft Graph and sorts them into three piles. Reply now gets a line on what the sender wants; read later gets a line on what it is; ignore gets a count. Each line links to the message in Outlook on the web, and nothing is marked read.
GET /me/mailFolders/inbox/messages?$filter=receivedDateTime ge <yesterday 08:00> and isRead eq false&$orderby=receivedDateTime desc&$select=from,subject,bodyPreview,receivedDateTime,importance,inferenceClassification,toRecipients,ccRecipients,webLink&$top=100. On Mondays, start from Friday 08:00.
Reply now: from a person, addressed to you, with a question, request or deadline. Read later: FYIs, reports, threads where you are in Cc. Ignore: notifications, newsletters, and mail Focused Inbox put in Other.
If a reply-now preview is too short to say what is asked, read that message with GET /me/messages/{id}?$select=body and the header Prefer: outlook.body-content-type="text". Everything else is judged from the preview.
Reply now first, one line each with sender, the ask and the webLink; then read later in one line each; then the ignore count by type. Do not change any message.
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/outlook-inbox-triage-digest/install | shAsk Claude Code:
promptRun the outlook-inbox-triage-digest skillOr paste the prompt instead of installing:
promptUsing Microsoft Graph (or the Microsoft 365 connector), list unread messages in my Outlook inbox received since yesterday 08:00 (since Friday 08:00 on Mondays), with sender, subject, bodyPreview, importance, inferenceClassification and webLink. Sort them into reply now (from a person, to me, with a question, request or deadline), read later (FYIs, reports, threads where I am in Cc) and ignore (notifications, newsletters, Other). For reply now, say what is asked in one line, opening the full body only when the preview is not enough. Give counts, then reply now with links, then read later, then the ignore count by type. Do not mark anything read.Weekdays at 8:00, from cron on any machine where Claude Code is signed in:
crontab0 8 * * 1-5 claude -p "Run the outlook-inbox-triage-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: outlook-inbox-triage-digest
description: "Weekday mornings: every unread Outlook email since yesterday, sorted into reply now, read later and ignore, one line each with a link. Use when the user asks for this, or when it runs on a schedule."
---
# Outlook inbox triage digest
Weekday mornings: every unread Outlook email since yesterday, sorted into reply now, read later and ignore, one line each with a link.
Thirty unread emails at 8:00 are rarely thirty decisions. Most are notifications, newsletters and threads you are copied on; three or four actually need you. Finding those means opening everything, which is how a morning disappears.
The agent reads the subject, sender and preview of each unread message through Microsoft Graph and sorts them into three piles. Reply now gets a line on what the sender wants; read later gets a line on what it is; ignore gets a count. Each line links to the message in Outlook on the web, and nothing is marked read.
## 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
- Claude's Microsoft 365 connector for work or school accounts, or a Microsoft Graph app with delegated `Mail.Read` (previews and bodies need more than `Mail.ReadBasic`).
If something is missing, say what and stop; do not invent numbers.
### Steps
1. **Read unread mail** (Outlook): `GET /me/mailFolders/inbox/messages?$filter=receivedDateTime ge <yesterday 08:00> and isRead eq false&$orderby=receivedDateTime desc&$select=from,subject,bodyPreview,receivedDateTime,importance,inferenceClassification,toRecipients,ccRecipients,webLink&$top=100`. On Mondays, start from Friday 08:00.
2. **Sort into three piles**: Reply now: from a person, addressed to you, with a question, request or deadline. Read later: FYIs, reports, threads where you are in Cc. Ignore: notifications, newsletters, and mail Focused Inbox put in Other.
3. **Open only what needs it** (Outlook): If a reply-now preview is too short to say what is asked, read that message with `GET /me/messages/{id}?$select=body` and the header `Prefer: outlook.body-content-type="text"`. Everything else is judged from the preview.
4. **Post the digest**: Reply now first, one line each with sender, the ask and the `webLink`; then read later in one line each; then the ignore count by type. Do not change any message.
## Route B: the browser
### What you need
- Signed in to Outlook on the web as the mailbox owner, with 2FA already done. Reading pane set to **Hide** (View > Layout) stops messages being marked read as the agent moves through the list.
If something is missing, say what and stop; do not invent numbers.
### Steps
Start at https://outlook.office.com/mail/inbox. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.
1. **Show only unread mail since yesterday**: Open the inbox (work or school at outlook.office.com; personal at outlook.live.com). Click **Filter > Unread**, and search `received>=<yesterday>` (Friday on Mondays) to narrow the list. Check both **Focused** and **Other** if Focused Inbox is on.
2. **Read from the list, not the message**: The message list shows sender, subject and a preview line for each item without opening it, so nothing gets marked read. Judge each one from there.
3. **Sort into three piles**: Reply now: a person writing to you with a question, request or deadline. Read later: FYIs, reports and threads where you are in Cc. Ignore: notifications, newsletters and everything in Other unless it is clearly a person asking you something.
4. **Open only what you must, then restore unread**: If a reply-now preview is too short, open the message; Outlook marks it read, so afterwards right-click it and choose **Mark as unread**. Copy the link from the address bar while it is open.
5. **Write the digest**: Counts first, then reply now with sender, the ask in one line and the link, then read later in one line each, then the ignore count by type.
Note: The list preview is one line, shorter than the API's `bodyPreview`, so the agent opens more messages than the API route does and has to restore unread on each. Outlook on the web shows at most a page at a time; with more than about 100 unread messages the API route is faster.
## The report
- **Counts** for each pile.
- **Reply now**: sender, the ask in one line, and a link.
- **Read later**: sender and what it is, in one line.
- **Ignore**: a count by type (notifications, newsletters, other).
## 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": "outlook-inbox-triage-digest/<date of this run, e.g. 2026-10-16>",
"item_key": "outlook-inbox-triage-digest",
"project": "Inbox",
"source": "Outlook inbox triage digest skill",
"kind": "update",
"title": "23 unread: 4 need a reply",
"summary": "**4 emails** need a reply today, one with a **noon deadline**. 7 are worth reading later and 12 can wait or go.",
"widget": [
{
"type": "Table",
"props": {
"columns": [
"From",
"Needs",
"Received"
],
"align": [
"left",
"left",
"right"
],
"rows": [
[
"Finance team",
"Approve the Q4 software budget by noon",
"07:40"
],
[
"Jon Weber, Halcyon",
"Confirm the liability cap wording",
"Yesterday"
],
[
"Priya Nair",
"Two numbers for the board deck",
"Yesterday"
],
[
"Recruiting",
"Pick an interview slot for Thursday",
"06:55"
]
]
}
},
{
"type": "Badges",
"props": {
"items": [
{
"label": "Reply now 4",
"tone": "warn"
},
{
"label": "Read later 7",
"tone": "info"
},
{
"label": "Ignore 12"
}
]
}
}
]
}
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 8:00 (`0 8 * * 1-5`). From cron, with the agent signed in on that machine:
```bash
0 8 * * 1-5 claude -p "Run the outlook-inbox-triage-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/outlook-inbox-triage-digest#schedule
Source: https://briefkin.dev/skills/outlook-inbox-triage-digest
Claude's Microsoft 365 connector for work or school accounts, or a Microsoft Graph app with delegated Mail.Read (previews and bodies need more than Mail.ReadBasic).
Mail.Read, Calendars.Read and offline_access, allow public client flows, sign in once with the device code flow, and store MS_TENANT_ID, MS_CLIENT_ID and MS_REFRESH_TOKEN. This route also works for personal Outlook.com accounts through the consumers tenant.Mail.ReadBasic is enough when a report needs only senders, subjects and dates, not message bodies. If you use application permissions for a shared mailbox, limit the app to that mailbox with RBAC for Applications in Exchange Online.
No. Listing messages and reading previews does not change their read state, and the skill never sets isRead. Opening a full body through the API does not mark it read either.
It reads Outlook's own classification (inferenceClassification) as one signal: mail in Other goes to ignore unless it is clearly from a person asking you something. If you have Focused Inbox turned off, every message is classified as focused and the skill sorts by content alone.
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 Outlook pages themselves: the agent opens outlook.office.com/mail/inbox 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.