digest

/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 v1.0.0 skills.

Runtime Gate (per ADR-094)

Canonical resolution: This is the Claude Cowork variant — namespaced-only. When both plugin-claude-code and plugin-claude-cowork are loaded in the same session (most common in Claude Desktop), bare /digest resolves to aria-knowledge's variant — Code is the canonical owner of all 24 dual-port skills per ADR-094 §Part 1. To reach this skill, use the namespaced form: /aria-cowork:digest. Do NOT match bare /digest — that belongs to aria-knowledge.

Before Step 0: Check whether the Bash tool is available in this session. If Bash IS available (you are running in Claude Code or another runtime with shell access), surface the following notification and wait for explicit user confirmation:

⚠️ Runtime mismatch — you invoked aria-cowork's /digest from a runtime with shell access.

This skill is Cowork-native because the 4-category MCP set (chat / email / project tracker / docs) is typically only connected in Cowork. If you're in Code and DO have these MCPs configured there, fine to proceed; otherwise the canonical aria-knowledge variant at /digest will at least surface the same gate.

Use /digest instead? (y / n)

Wait for an explicit reply:

• y / yes — Use the Skill tool to invoke digest (the bare-slash canonical, which routes to aria-knowledge when both ports are loaded) with the same arguments the user provided to this invocation. Do not proceed with this skill's steps; the aria-knowledge variant takes over and runs to completion. This is the default-yes path — auto-redirect is the helpful action.
• n / no — Proceed with this (aria-cowork) variant anyway despite the runtime mismatch. The user has explicitly opted in.
• No response / any other reply — Treat as "do not proceed" and exit cleanly without running either variant.

This gate applies even when mode = auto per ADR-094 §Part 3. Auto mode's "implicit-yes on all gates" rule is suspended for the runtime-mismatch check — auto trusts that the user invoked the correct variant, and this gate enforces that precondition. All other auto-mode gates remain bypassed. The friction cost is now low: on y, the auto-redirect runs the correct variant with the original args.

If Bash is NOT available (normal Cowork runtime), proceed to Step 0.

Step 0: Resolve config

The default knowledge folder is ~/Projects/knowledge/ (expand ~ to your home directory's absolute path). Read <knowledge_folder>/aria-config.md and extract knowledge_folder (the absolute path).

If aria-config.md doesn't exist, stop with: "aria-cowork is not configured. Run /aria-setup to get started."

Lazily create <knowledge_folder>/intake/digests/ if it doesn't exist.

For all subsequent file operations in this skill, use the absolute path from knowledge_folder directly. Cowork resolves absolute paths via the persistent grant from claude_desktop_config.json per ADR-008. aria-knowledge in Code uses the same absolute path to reach the same files.

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 Cowork Settings → Connectors (or Claude Code's .mcp.json for the Code surface). See [CONNECTORS.md](../../CONNECTORS.md). Skipping this run.

Per ADR-015 — 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: [<l