Home
Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.
...Expand allAbout digest
The digest command scans recent activity across all connected data sources and produces a structured summary of what matters. It is aimed at catching up after time away, starting the day with a rundown of mentions and action items, or reviewing a week of decisions and document updates grouped by project.
The time window is controlled by flags: --daily covers the last 24 hours (the default), --weekly covers the last 7 days, and a custom --since value accepts inputs like yesterday, Monday, or a date. It first checks which MCP sources are connected (chat, email, cloud storage, project tracker, CRM, and knowledge base) and guides the user to connect at least one when none are available. Activity is then gathered per source, such as mentions and threads in chat, inbox replies in email, modified or shared documents in cloud storage, assigned tasks in the project tracker, opportunity and account updates in the CRM, and updated wiki pages in the knowledge base.
Gathered items are categorized into action items, decisions, mentions, and updates, then grouped by topic or project rather than by source, with related cross-source activity merged and deduplicated so the same decision appearing in chat and email counts once. The output leads with action items, followed by decisions, topic groups, mentions, and document updates, and closes with summary stats. If a source is unreachable the digest still generates from the sources that succeeded and notes which were skipped, and it can use a memory system such as CLAUDE.md to decode people and project references.
FAQ
What time windows does the digest support?
Use --daily for the last 24 hours (the default), --weekly for the last 7 days, or --since with a value like yesterday, Monday, or a specific date.
Which sources can it pull activity from?
Any connected MCP sources, including chat, email, cloud storage, a project tracker, a CRM, and a knowledge base.
What happens if one source is unreachable?
The digest is still generated from the sources that succeeded and notes which one could not be reached; a single failed source never blocks the whole digest.
How is the output organized?
By topic or project rather than by source, leading with action items, then decisions, topic groups, mentions, and document updates, ending with summary stats.
Does it avoid listing the same event twice?
Yes, cross-source activity is deduplicated, so a decision that appears in both chat and email is reported as a single entry.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Scan recent activity across all connected sources and generate a structured digest highlighting what matters.
Instructions
1. Parse Flags
Determine the time window from the user's input:
--daily— Last 24 hours (default if no flag specified)--weekly— Last 7 days
The user may also specify a custom range:
--since yesterday--since Monday--since 2025-01-20
2. Check Available Sources
Identify which MCP sources are connected (same approach as the search command):
- ~~chat — channels, DMs, mentions
- ~~email — inbox, sent, threads
- ~~cloud storage — recently modified docs shared with user
- ~~project tracker — tasks assigned, completed, commented on
- ~~CRM — opportunity updates, account activity
- ~~knowledge base — recently updated wiki pages
If no sources are connected, guide the user:
To generate a digest, you'll need at least one source connected.Check your MCP settings to add ~~chat, ~~email, ~~cloud storage, or other tools.3. Gather Activity from Each Source
~~chat:
- Search for messages mentioning the user (
to:me) - Check channels the user is in for recent activity
- Look for threads the user participated in
- Identify new messages in key channels
~~email:
- Search recent inbox messages
- Identify threads with new replies
- Flag emails with action items or questions directed at the user
~~cloud storage:
- Find documents recently modified or shared with the user
- Note new comments on docs the user owns or collaborates on
~~project tracker:
- Tasks assigned to the user (new or updated)
- Tasks completed by others that the user follows
- Comments on tasks the user is involved with
~~CRM:
- Opportunity stage changes
- New activities logged on accounts the user owns
- Updated contacts or accounts
~~knowledge base:
- Recently updated documents in relevant collections
- New documents created in watched areas
4. Identify Key Items
From all gathered activity, extract and categorize:
Action Items:
- Direct requests made to the user ("Can you...", "Please...", "@user")
- Tasks assigned or due soon
- Questions awaiting the user's response
- Review requests
Decisions:
- Conclusions reached in threads or emails
- Approvals or rejections
- Policy or direction changes
Mentions:
- Times the user was mentioned or referenced
- Discussions about the user's projects or areas
Updates:
- Status changes on projects the user follows
- Document updates in the user's domain
- Completed items the user was waiting on
5. Group by Topic
Organize the digest by topic, project, or theme rather than by source. Merge related activity across sources:
## Project Aurora- ~~chat: Design review thread concluded — team chose Option B (#design, Tuesday)- ~~email: Sarah sent updated spec incorporating feedback (Wednesday)- ~~cloud storage: "Aurora API Spec v3" updated by Sarah (Wednesday)- ~~project tracker: 3 tasks moved to In Progress, 2 completed## Budget Planning- ~~email: Finance team requesting Q2 projections by Friday- ~~chat: Todd shared template in #finance (Monday)- ~~cloud storage: "Q2 Budget Template" shared with you (Monday)6. Format the Digest
Structure the output clearly:
# [Daily/Weekly] Digest — [Date or Date Range]Sources scanned: ~~chat, ~~email, ~~cloud storage, [others]## Action Items (X items)- [ ] [Action item 1] — from [person], [source] ([date])- [ ] [Action item 2] — from [person], [source] ([date])## Decisions Made- [Decision 1] — [context] ([source], [date])- [Decision 2] — [context] ([source], [date])## [Topic/Project Group 1][Activity summary with source attribution]## [Topic/Project Group 2][Activity summary with source attribution]## Mentions- [Mention context] — [source] ([date])## Documents Updated- [Doc name] — [who modified, what changed] ([date])7. Handle Unavailable Sources
If any source fails or is unreachable:
Note: Could not reach [source name] for this digest.The following sources were included: [list of successful sources].Do not let one failed source prevent the digest from being generated. Produce the best digest possible from available sources.
8. Summary Stats
End with a quick summary:
---[X] action items · [Y] decisions · [Z] mentions · [W] doc updatesAcross [N] sources · Covering [time range]Notes
- Default to
--dailyif no flag is specified - Group by topic/project, not by source — users care about what happened, not where it happened
- Action items should always be listed first — they are the most actionable part of a digest
- Deduplicate cross-source activity (same decision in ~~chat and email = one entry)
- For weekly digests, prioritize significance over completeness — highlight what matters, skip noise
- If the user has a memory system (CLAUDE.md), use it to decode people names and project references
- Include enough context in each item that the user can decide whether to dig deeper without clicking through
Install digest
Download and extract the skill files to your .claude/skills/ directory.
Download ZIPClone the repository and copy the skill files to your project.
git clone https://github.com/anthropics/knowledge-work-plugins/blob/main/enterprise-search/skills/digest/SKILL.md # Copy SKILL.md to your .claude/skills/ directory
Copy
