Digest

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

FeaturedInstructions onlyProductivity & Workflow
AI-generated overview

Generates a daily or weekly digest of activity across connected sources, grouped by topic with action items first.

What it does
Scans recent activity across connected sources such as chat, email, cloud storage, project trackers, CRM and knowledge bases for a chosen time window. Extracts and categorizes action items, decisions, mentions and updates, then groups them by topic or project rather than by source. Produces a structured digest with source attribution, dates and closing summary statistics, and notes any sources it could not reach.
When to use it
Use it 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. It supports daily, weekly or custom date-range windows.
Requirements
Requires at least one connected MCP source (chat, email, cloud storage, project tracker, CRM or knowledge base) and access to those services. Instructions only; no scripts are shipped.

Digest Command

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 --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
  • 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

Source and attribution

Source:anthropics/knowledge-work-pluginsinenterprise-search/skills/digestat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today