digest

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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.

若遇到不熟悉的占位符或需查看已连接工具，请参考 CONNECTORS.md。

扫描所有关联数据源的近期活动，生成突出关键信息的结构化摘要。

Instructions

操作说明

1. Parse Flags

1. 解析参数

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

根据用户输入确定时间范围：

```
--daily
```
— 过去24小时（未指定参数时默认使用）
```
--weekly
```
— 过去7天

用户也可指定自定义范围：

```
--since yesterday
```
```
--since Monday
```
```
--since 2025-01-20
```

2. Check Available Sources

2. 检查可用数据源

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.

确认已连接的MCP数据源（与搜索命令采用相同逻辑）：

~~chat — 频道、私信、提及内容
~~email — 收件箱、已发送、线程对话
~~cloud storage — 近期修改且与用户共享的文档
~~project tracker — 已分配、已完成、有评论的任务
~~CRM — 商机更新、客户账户活动
~~knowledge base — 近期更新的维基页面

若未连接任何数据源，引导用户：

要生成摘要，您至少需要连接一个数据源。
请前往MCP设置添加~~chat、~~email、~~cloud storage或其他工具。

3. Gather Activity from Each Source

3. 从各数据源收集活动信息

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

~~chat：

搜索提及用户的消息（
```
to:me
```
）
检查用户所在频道的近期活动
查找用户参与过的线程对话
识别关键频道中的新消息

~~email：

搜索近期收件箱消息
识别有新回复的线程对话
标记包含待办事项或向用户提出问题的邮件

~~cloud storage：

查找近期修改或共享给用户的文档
记录用户拥有或协作的文档的新评论

~~project tracker：

分配给用户的任务（新增或更新）
用户关注的、由他人完成的任务
用户参与的任务的评论

~~CRM：

商机阶段变更
用户负责的客户账户上记录的新活动
更新的联系人或客户账户

~~knowledge base：

相关集合中近期更新的文档
关注区域内新增的文档

4. Identify Key Items

4. 识别关键内容

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

从收集到的所有活动中，提取并分类：

待办事项（Action Items）：

直接向用户提出的请求（“你能否...”, “请...”, “@用户”）
已分配或即将到期的任务
等待用户回复的问题
评审请求

决策（Decisions）：

线程对话或邮件中达成的结论
批准或拒绝决定
政策或方向变更

提及内容（Mentions）：

用户被提及或引用的场景
关于用户负责项目或领域的讨论

更新内容（Updates）：

用户关注的项目状态变更
用户负责领域内的文档更新
用户等待的已完成事项

5. Group by Topic

5. 按主题分组

Organize the digest by topic, project, or theme rather than by source. Merge related activity across sources:

undefined

按主题、项目或主题而非数据源组织摘要，合并跨数据源的相关活动：

undefined

Project Aurora

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

~~chat: 设计评审线程已结束 — 团队选择了方案B（#design，周二）
~~email: Sarah发送了整合反馈后的更新版规格文档（周三）
~~cloud storage: Sarah更新了《Aurora API 规格v3》（周三）
~~project tracker: 3项任务移至进行中，2项已完成

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)

undefined

~~email: 财务团队要求周五前提交Q2预测数据
~~chat: Todd在#finance频道分享了模板（周一）
~~cloud storage: 《Q2预算模板》已共享给您（周一）

undefined

6. Format the Digest

6. 格式化摘要

Structure the output clearly:

undefined

清晰结构化输出内容：

undefined

[Daily/Weekly] Digest — [Date or Date Range]

[每日/每周] 摘要 — [日期或日期范围]

Sources scanned: ~~chat, ~~email, ~~cloud storage, [others]

已扫描数据源：~~chat, ~~email, ~~cloud storage, [其他]

Action Items (X items)

待办事项（共X项）

[Action item 1] — from [person], [source] ([date])
[Action item 2] — from [person], [source] ([date])

[待办事项1] — 来自[联系人]，[数据源]（[日期]）
[待办事项2] — 来自[联系人]，[数据源]（[日期]）

Decisions Made

已做出的决策

[Decision 1] — [context] ([source], [date])
[Decision 2] — [context] ([source], [date])

[决策1] — [背景说明]（[数据源]，[日期]）
[决策2] — [背景说明]（[数据源]，[日期]）

[Topic/Project Group 1]

[主题/项目组1]

[Activity summary with source attribution]

[带数据源标注的活动摘要]

[Topic/Project Group 2]

[主题/项目组2]

[Activity summary with source attribution]

[带数据源标注的活动摘要]

Mentions

提及内容

[Mention context] — [source] ([date])

[提及场景] — [数据源]（[日期]）

Documents Updated

已更新文档

[Doc name] — [who modified, what changed] ([date])

undefined

[文档名称] — [修改人，修改内容]（[日期]）

undefined

7. Handle Unavailable Sources

7. 处理不可用的数据源

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

8. 汇总统计

End with a quick summary:

---
[X] action items · [Y] decisions · [Z] mentions · [W] doc updates
Across [N] sources · Covering [time range]

在末尾添加快速汇总：

---
[X]项待办事项 · [Y]项决策 · [Z]次提及 · [W]份文档更新
覆盖[N]个数据源 · 时间范围：[具体范围]

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

若未指定参数，默认使用
```
--daily
```
模式
按主题/项目分组，而非按数据源 — 用户关心的是发生了什么，而非在哪里发生
待办事项应始终排在首位 — 这是摘要中最具行动价值的部分
去重跨数据源的重复活动（同一决策同时出现在~~chat和email中 = 仅保留一条记录）
对于每周摘要，优先突出重要内容而非追求完整性 — 聚焦关键信息，过滤无效内容
若用户有记忆系统（CLAUDE.md），使用它解析人名和项目引用
每个条目需包含足够上下文，让用户无需点击跳转即可判断是否需要深入查看