Digest
Generate a daily or weekly digest of mentions, tasks, and doc updates across MCP-connected chat, email, and project tools.
Overview
digest is a journey-wide agent skill that scans MCP-connected work tools and builds a daily or weekly catch-up digest of mentions, tasks, and doc updates.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill digestWhat is this skill?
- Flags: --daily (24h default), --weekly (7d), or --since custom date phrases
- Scans connected MCP sources: chat, email, cloud storage, project tracker, CRM, knowledge base
- Structured digest of mentions, assigned tasks, and recently modified shared docs
- Mirrors search-command connector discovery; guides setup when no sources are connected
- argument-hint documents CLI-style invocations for the digest command
- Six MCP source families listed in SKILL.md: chat, email, cloud storage, project tracker, CRM, knowledge base
Adoption & trust: 1.4k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You return from a break or start Monday with mentions, emails, and tracker noise spread across disconnected tools and no single prioritized summary.
Who is it for?
Solo builders running Claude with knowledge-work MCP connectors who want a repeatable morning or weekly rollup without manual tab hopping.
Skip if: Teams with zero MCP sources connected, or workflows that need deep code review rather than cross-app activity synthesis.
When should I use this skill?
Catching up after time away, starting the day wanting mentions and action items summarized, or reviewing a week’s decisions and document updates grouped by project.
What do I get? / Deliverables
You get a time-bounded digest grouped by project with action items and updates sourced from every connected MCP channel you configured.
- Structured time-windowed digest
- Grouped project highlights
- Action item list from connected sources
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Run --daily before standup to list assigned tracker tasks and doc edits from overnight.
Use --since Monday after PTO to replay channel decisions before shipping a hotfix.
Weekly --weekly pass over CRM and email threads for account activity before renewal outreach.
Scan chat mentions of launch posts and shared analytics docs in one digest.
How it compares
Command-style workflow over raw search—structured digest with time windows, not a generic filesystem grep or single SaaS integration skill.
Common Questions / FAQ
Who is digest for?
Indie builders and operators using Anthropic knowledge-work plugins with at least one MCP connector who need catch-up summaries across chat, mail, and project tools.
When should I use digest?
At Build PM for sprint context; Operate iterate when monitoring cross-team signals; Grow support when reviewing customer threads; any day you want --daily or --weekly rollup after time away.
Is digest safe to install?
It reads data only from connectors you authorize via MCP—review the Security Audits panel on this skill’s detail page and limit connector scopes accordingly.
SKILL.md
READMESKILL.md - Digest
# Digest Command > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../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], [