/digest

description: "NOTE: this skill requires connected ~~chat / ~~email / ~~project-tracker / ~~docs MCPs, which are typically only present in Cowork — the Code variant exists for parity but most users will want the Cowork variant. Cross-tool rollup of what's pending, what shipped, and what's blocked across chat / email / project tracker / docs. Use when user says '/digest', 'weekly digest', 'cross-tool rollup', 'what's pending across my tools', 'summarize this week', 'standup digest'. Probes all 4 ~~categories and degrades gracefully — produces a digest even with only 1-2 MCPs connected, surfacing which categories were unavailable. (Code port — ADR-094.)"

/digest — Cross-Tool Weekly Rollup

Synthesize a digest of activity across connected MCPs into `intake/digests/{YYYY-MM-DD}.md`. Pulls from `~~chat` + `~~email` + `~~project tracker` + `~~docs` to produce a "what's pending / what shipped / what's blocked" rollup. Composite of all 4 categories — the most cross-tool of the v2.18.0 skills.

Step 0: Resolve Config

Read `~/.gemini/antigravity/aria-knowledge.local.md` and extract `knowledge_folder`. If the file doesn't exist, stop: "aria-knowledge is not configured. Run /setup to get started."

Lazily create `{knowledge_folder}/intake/digests/` if it doesn't exist.

Step 1: Probe Connected MCPs (all 4 categories)

Check Claude's available tool list for each `~~category`. The digest runs with ANY non-zero set of connected MCPs — gather from whichever are connected, surface gaps for the rest.

| Category | MCP options | Status | |---|---|---| | `~~chat` | slack, ms365 | <connected: list / not connected> | | `~~email` | gmail, ms365 | <connected: list / not connected> | | `~~project tracker` | linear, asana, atlassian, monday, clickup, notion | <connected: list / not connected> | | `~~docs` | notion, atlassian, box, egnyte, google docs | <connected: list / not connected> |

If NO MCPs in ANY category are connected, output the standard fallback notice and stop:

> No required MCPs connected for `/digest`. Connect at least one of: Slack/MS365 (~~chat), Gmail/MS365 (~~email), Linear/Asana/etc. (~~project tracker), or Notion/Confluence/etc. (~~docs) via Claude Code's MCP config (or Cowork Settings → Connectors). See [CONNECTORS.md](../../CONNECTORS.md). Skipping this run.

Per ADR-015 (`{knowledge_folder}/projects/aria-cowork/decisions/015-capability-probe-pattern.md`) — degrade gracefully for missing categories; don't fabricate.

Step 2: Parse Time Window

Determine the digest window from args:

| Arg | Window | |---|---| | (none) or `--week` | Last 7 days (today minus 7) | | `--since YYYY-MM-DD` | From that date to today | | `--since YYYY-MM-DD --until YYYY-MM-DD` | Closed range | | `--month` | Last 30 days | | `--quarter` | Last 90 days |

Default: 7-day window. State the window explicitly in the digest header.

Step 3: Gather per Connected Category

For each CONNECTED category, run the appropriate fetch. Skip disconnected categories (note as gaps in the digest output).

3a. `~~chat` (if connected)

For Slack: search for messages where the user is mentioned (`@user`) OR is the author, in the time window. Also fetch unresolved threads (the user posted and got no response after 24+ hours).

For MS365 Teams: similar — channel mentions + direct messages.

Gather:

• Mention count per channel
• Top 5-10 threads ranked by reply count or recency
• Threads where the user owes a response (last message is not theirs + question mark or @-mention)

3b. `~~email` (if connected)

For Gmail or MS365: search inbox for unread messages in the window, sent items in the window, and emails flagged/starred.

Gather:

• Top 10 sent emails by reply-count (active threads the user drove)
• Unread count by sender
• Flagged / starred items

3c. `~~project tracker` (if connected)

For Linear / Asana / Atlassian / Monday / ClickUp / Notion-as-tracker: query for issues assigned to the user with status changes in the window.

Gather (per tool, format-normalized):

• **Pending:** open issues assigned, sorted by priority + last-update
• **Shipped:** issues moved to Done/Closed/Shipped in the window
• **Blocked:** issues with Blocked status, or stale (no update in 7+ days while still Open)
• **Mentions:** issues where the user was mentioned in comments

3d. `~~docs` (if connected)

For Notion / Confluence / etc.: list docs touched by the user (created OR edited) in the window. List docs the user was @-mentioned in.

Gather:

• Recently touched (top 10, ordered by edit time)
• Mentions / pages the user was tagged in

Step 4: Synthesize the Digest

Compose a unified narrative from the gathered data. Sections:

1. **Window & sources** — explicit time window + which MCPs were available + which were not 2. **What's pending** — open items needing the user's action (from project tracker + threads owed responses + unread flagged emails) 3. **What shipped** — closed/completed/moved items in the window (from project tracker + sent emails noting completion + docs marked done) 4. **What's blocked** — items in Blocked status, stale items, threads waiting on others 5. **Cross-tool patterns** — observations that span sources (e.g., "3 mentions of Project Phoenix across chat + tracker but no doc in `~~docs` for it; consider creating one") 6. **Gaps surfaced** — categories that weren't connected + what would be added by connecting them

Be conservative: rank by signal, not volume. A digest with 12 strong items beats 47 noisy ones.

Step 5: Write + Report

Filename: `intake/digests/{YYYY-MM-DD}.md`. Use today's date (the digest's *creation* date, not the window's end date). If a file with that name exists, append `-2`, `-3` for multiple digests in one day.

Body template:

---
date: <YYYY-MM-DD>
window_start: <YYYY-MM-DD>
window_end: <YYYY-MM-DD>
sources_connected: [<list of connected MCP names>]
sources_unavailable: [<list of disconnected categories>]
tags: [digest, weekly|monthly|quarterly]
---

#