digest
starsforks
How to install digest?
anthropics/knowledge-work-plugins/digest
$npx -y skills add anthropics/knowledge-work-plugins --skill digestGenerate 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.
SKILL.md
| 1 | # Digest Command |
| 2 | |
| 3 | > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). |
| 4 | |
| 5 | Scan recent activity across all connected sources and generate a structured digest highlighting what matters. |
| 6 | |
| 7 | ## Instructions |
| 8 | |
| 9 | ### 1. Parse Flags |
| 10 | |
| 11 | Determine the time window from the user's input: |
| 12 | |
| 13 | - `--daily` — Last 24 hours (default if no flag specified) |
| 14 | - `--weekly` — Last 7 days |
| 15 | |
| 16 | The user may also specify a custom range: |
| 17 | - `--since yesterday` |
| 18 | - `--since Monday` |
| 19 | - `--since 2025-01-20` |
| 20 | |
| 21 | ### 2. Check Available Sources |
| 22 | |
| 23 | Identify which MCP sources are connected (same approach as the search command): |
| 24 | |
| 25 | - **~~chat** — channels, DMs, mentions |
| 26 | - **~~email** — inbox, sent, threads |
| 27 | - **~~cloud storage** — recently modified docs shared with user |
| 28 | - **~~project tracker** — tasks assigned, completed, commented on |
| 29 | - **~~CRM** — opportunity updates, account activity |
| 30 | - **~~knowledge base** — recently updated wiki pages |
| 31 | |
| 32 | If no sources are connected, guide the user: |
| 33 | ``` |
| 34 | To generate a digest, you'll need at least one source connected. |
| 35 | Check your MCP settings to add ~~chat, ~~email, ~~cloud storage, or other tools. |
| 36 | ``` |
| 37 | |
| 38 | ### 3. Gather Activity from Each Source |
| 39 | |
| 40 | **~~chat:** |
| 41 | - Search for messages mentioning the user (`to:me`) |
| 42 | - Check channels the user is in for recent activity |
| 43 | - Look for threads the user participated in |
| 44 | - Identify new messages in key channels |
| 45 | |
| 46 | **~~email:** |
| 47 | - Search recent inbox messages |
| 48 | - Identify threads with new replies |
| 49 | - Flag emails with action items or questions directed at the user |
| 50 | |
| 51 | **~~cloud storage:** |
| 52 | - Find documents recently modified or shared with the user |
| 53 | - Note new comments on docs the user owns or collaborates on |
| 54 | |
| 55 | **~~project tracker:** |
| 56 | - Tasks assigned to the user (new or updated) |
| 57 | - Tasks completed by others that the user follows |
| 58 | - Comments on tasks the user is involved with |
| 59 | |
| 60 | **~~CRM:** |
| 61 | - Opportunity stage changes |
| 62 | - New activities logged on accounts the user owns |
| 63 | - Updated contacts or accounts |
| 64 | |
| 65 | **~~knowledge base:** |
| 66 | - Recently updated documents in relevant collections |
| 67 | - New documents created in watched areas |
| 68 | |
| 69 | ### 4. Identify Key Items |
| 70 | |
| 71 | From all gathered activity, extract and categorize: |
| 72 | |
| 73 | **Action Items:** |
| 74 | - Direct requests made to the user ("Can you...", "Please...", "@user") |
| 75 | - Tasks assigned or due soon |
| 76 | - Questions awaiting the user's response |
| 77 | - Review requests |
| 78 | |
| 79 | **Decisions:** |
| 80 | - Conclusions reached in threads or emails |
| 81 | - Approvals or rejections |
| 82 | - Policy or direction changes |
| 83 | |
| 84 | **Mentions:** |
| 85 | - Times the user was mentioned or referenced |
| 86 | - Discussions about the user's projects or areas |
| 87 | |
| 88 | **Updates:** |
| 89 | - Status changes on projects the user follows |
| 90 | - Document updates in the user's domain |
| 91 | - Completed items the user was waiting on |
| 92 | |
| 93 | ### 5. Group by Topic |
| 94 | |
| 95 | Organize the digest by topic, project, or theme rather than by source. Merge related activity across sources: |
| 96 | |
| 97 | ``` |
| 98 | ## Project Aurora |
| 99 | - ~~chat: Design review thread concluded — team chose Option B (#design, Tuesday) |
| 100 | - ~~email: Sarah sent updated spec incorporating feedback (Wednesday) |
| 101 | - ~~cloud storage: "Aurora API Spec v3" updated by Sarah (Wednesday) |
| 102 | - ~~project tracker: 3 tasks moved to In Progress, 2 completed |
| 103 | |
| 104 | ## Budget Planning |
| 105 | - ~~email: Finance team requesting Q2 projections by Friday |
| 106 | - ~~chat: Todd shared template in #finance (Monday) |
| 107 | - ~~cloud storage: "Q2 Budget Template" shared with you (Monday) |
| 108 | ``` |
| 109 | |
| 110 | ### 6. Format the Digest |
| 111 | |
| 112 | Structure the output clearly: |
| 113 | |
| 114 | ``` |
| 115 | # [Daily/Weekly] Digest — [Date or Date Range] |
| 116 | |
| 117 | Sources scanned: ~~chat, ~~email, ~~cloud storage, [others] |
| 118 | |
| 119 | ## Action Items (X items) |
| 120 | - [ ] [Action item 1] — from [person], [source] ([date]) |
| 121 | - [ ] [Action item 2] — from [person], [source] ([date]) |
| 122 | |
| 123 | ## Decisions Made |
| 124 | - [Decision 1] — [context] ([source], [date]) |
| 125 | - [Decision 2] — [context] ([source], [date]) |
| 126 | |
| 127 | ## [Topic/Project Group 1] |
| 128 | [Activity summary with source attribution] |
| 129 | |
| 130 | ## [Topic/Project Group 2] |
| 131 | [Activity summary with source attribution] |
| 132 | |
| 133 | ## Mentions |
| 134 | - [Mention context] — [source] ([date]) |
| 135 | |
| 136 | ## Documents Updated |
| 137 | - [Doc name] — [who modified, what changed] ([date]) |
| 138 | ``` |
| 139 | |
| 140 | ### 7. Handle Unavailable Sources |
| 141 | |
| 142 | If any source fails or is unreachable: |
| 143 | ``` |
| 144 | Note: Could not reach [source name] for this digest. |
| 145 | The following sources were included: [list of successful sources]. |
| 146 | ``` |
| 147 | |
| 148 | Do not let one failed source prevent the digest from being generated. Produce the best digest possible from available sources. |
| 149 | |
| 150 | ### 8. Summary Stats |
| 151 | |
| 152 | End with a quick summary: |
| 153 | ``` |
| 154 | --- |
| 155 | [X] action items · [Y] decisions · [Z] mentions · [W] doc updates |
| 156 | Across [N] sources · Covering [time range] |
| 157 | ``` |
| 158 | |
| 159 | ## Notes |
| 160 | |
| 161 | - Default to `--daily` if no flag is specified |
| 162 | - Group by topic/project, not by source |
People who liked this also viewed
6 picksType
- azure-resource-lookupList, find, and show Azure resources across subscriptions or resource groups. Handles prompts like \"list the websites in my subscription\", \"list my web apps\", \"show my app services\", \"list virtSkillsJul 2026
- azure-messagingTroubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. SkillsJul 2026
- lark-doc飞书云文档（Docx / Wiki 文档）：读取和编辑飞书文档内容。当用户给出文档 URL 或 token，或需要查看、创建、编辑文档、插入或下载文档图片附件时使用。文档中嵌入的电子表格、多维表格、画板，先用本 skill 提取 token 再切到对应 skill。当用户给出 doubao.com 的 /docx/ 或 /wiki/ URL/token 时，也应直接使用本 skill；路由依据是 SkillsJul 2026
- lark-im飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件（支持大文件分片下载）、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 FeedSkillsJul 2026
- lark-wiki飞书知识库：管理知识空间、空间成员和文档节点。创建和查询知识空间、查看和管理空间成员、管理节点层级结构、在知识库中组织文档和快捷方式。当用户需要在知识库中查找或创建文档、浏览知识空间结构、查看或管理空间成员、移动或复制节点时使用。当用户给出 doubao.com 的 /wiki/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URLSkillsJul 2026
- lark-mail飞书邮箱：Use when user mentions 起草邮件、写邮件、草稿、发送/回复/转发邮件、查阅邮件、看邮件、搜索邮件、邮件文件夹、邮件标签、邮件联系人、监听新邮件、邮件收信规则等；use for mail/email intent only. Do not use for docs/sheets/calendar/auth setup/pure contact lookup/IM chSkillsJul 2026
