digest
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.
Security Assessment
About 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.
Install digest
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
anthropics/knowledge-work-plugins