---
id: daily-digest
name: "digest"
url: https://skills.yangsir.net/skill/daily-digest
author: anthropics
domain: product
tags: ["content-curation", "news-aggregation", "information-retrieval", "automation"]
install_count: 2700
rating: 4.40 (20 reviews)
github: https://github.com/anthropics/knowledge-work-plugins
---

# digest

> 扫描所有连接信息源的近期活动，智能生成个性化摘要，快速掌握团队动态和重要信息

**Stats**: 2,700 installs · 4.4/5 (20 reviews)

## Before / After 对比

### 信息汇总与摘要

**Before**:

分别打开邮件、Slack、项目管理工具、文档协作平台等多个信息源，手动筛选重要内容，整理成日报或周报，耗时 40 分钟

**After**:

自动从所有连接的信息源收集活动，智能识别重要事项和决策点，生成结构化摘要，5 分钟获得完整信息概览

| Metric | Before | After | Change |
|---|---|---|---|
| 信息整理时间 | 40分钟 | 5分钟 | -88% |

## Readme

# digest

# Digest Command

If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/enterprise-search/skills/digest/../../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 updates
Across [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

Weekly Installs322Repository[anthropics/know…-plugins](https://github.com/anthropics/knowledge-work-plugins)GitHub Stars10.6KFirst SeenMar 13, 2026Security Audits[Gen Agent Trust HubPass](/anthropics/knowledge-work-plugins/digest/security/agent-trust-hub)[SocketPass](/anthropics/knowledge-work-plugins/digest/security/socket)[SnykPass](/anthropics/knowledge-work-plugins/digest/security/snyk)Installed oncodex308gemini-cli306opencode305cursor305kimi-cli304github-copilot304

---
*Source: https://skills.yangsir.net/skill/daily-digest*
*Markdown mirror: https://skills.yangsir.net/api/skill/daily-digest/markdown*