ProductivityBeginner
Activity Digest Generator
Generate daily or weekly activity digests across all connected platforms
#digest#summary#activity-tracking#productivity
You come back from a day off and spend two hours just figuring out what happened — scrolling through Slack, email, and project boards trying to piece together what you missed.
Who it's for: executives, remote team managers, project managers, consultants juggling multiple clients, distributed team members
Example
"Give me a Monday morning briefing" → A structured digest covering 23 Slack threads, 14 emails, and 6 project updates organized by topic with action items highlighted
CLAUDE.md Template
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Activity Digest Generator
Scan recent activity across all connected sources and generate a structured digest highlighting what matters.
## Instructions
### 1. Parse Time Window
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:
- **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 updates
Across [N] sources · Covering [time range]
```
## Tips
- Default to `--daily` if 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
- Include enough context in each item that the user can decide whether to dig deeper without clicking through
README.md
What This Does
This playbook turns Claude into a personal briefing assistant that scans all your connected platforms -- chat, email, cloud storage, project trackers, and more -- and generates a structured digest organized by topic. It surfaces action items, decisions, mentions, and document updates so you can catch up quickly after time away or start your day with a clear picture.
Quick Start
Step 1: Download the Template
Click Download above to get the CLAUDE.md file.
Step 2: Set Up Your Project
Create a project folder and place the template inside:
mkdir -p ~/Documents/ActivityDigest
mv ~/Downloads/activity-digest-generator.md ~/Documents/ActivityDigest/CLAUDE.md
Step 3: Start Working
cd ~/Documents/ActivityDigest
claude
Say: "Give me a daily digest"
Time Window Options
--daily-- Last 24 hours (the default)--weekly-- Last 7 days--since Monday-- Custom start date--since 2026-01-20-- Specific date
Output Format
The digest is organized by topic and project, not by source. It includes:
- Action Items -- Requests, tasks, and questions needing your response
- Decisions Made -- Conclusions reached across threads and emails
- Topic Groups -- Activity summaries merged across all sources
- Mentions -- Where you were referenced or discussed
- Documents Updated -- Recent changes to files you care about
A summary line at the end gives you the counts at a glance.
Tips
- Action items come first -- they are the most actionable part of any digest
- Weekly digests prioritize significance over completeness, so you get what matters without the noise
- Cross-source deduplication means the same decision discussed in chat and email shows up only once
- Works well even with just one connected source
Example Prompts
"Give me a daily digest"
"Weekly digest --since Monday"
"What happened while I was out since last Thursday?"
"Catch me up on everything from the past 48 hours"
"Summarize activity --weekly"