{
  "schema": "https://ai-atoms.com/schemas/skill-v1.json",
  "type": "skill",
  "id": "skill/digest",
  "version": "1.0.0",
  "name": "digest",
  "description": "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.",
  "system_prompt_fragment": "# Digest Command\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).\n\nScan recent activity across all connected sources and generate a structured digest highlighting what matters.\n\n## Instructions\n\n### 1. Parse Flags\n\nDetermine the time window from the user's input:\n\n- `--daily` — Last 24 hours (default if no flag specified)\n- `--weekly` — Last 7 days\n\nThe user may also specify a custom range:\n- `--since yesterday`\n- `--since Monday`\n- `--since 2025-01-20`\n\n### 2. Check Available Sources\n\nIdentify which MCP sources are connected (same approach as the search command):\n\n- **~~chat** — channels, DMs, mentions\n- **~~email** — inbox, sent, threads\n- **~~cloud storage** — recently modified docs shared with user\n- **~~project tracker** — tasks assigned, completed, commented on\n- **~~CRM** — opportunity updates, account activity\n- **~~knowledge base** — recently updated wiki pages\n\nIf no sources are connected, guide the user:\n```\nTo generate a digest, you'll need at least one source connected.\nCheck your MCP settings to add ~~chat, ~~email, ~~cloud storage, or other tools.\n```\n\n### 3. Gather Activity from Each Source\n\n**~~chat:**\n- Search for messages mentioning the user (`to:me`)\n- Check channels the user is in for recent activity\n- Look for threads the user participated in\n- Identify new messages in key channels\n\n**~~email:**\n- Search recent inbox messages\n- Identify threads with new replies\n- Flag emails with action items or questions directed at the user\n\n**~~cloud storage:**\n- Find documents recently modified or shared with the user\n- Note new comments on docs the user owns or collaborates on\n\n**~~project tracker:**\n- Tasks assigned to the user (new or updated)\n- Tasks completed by others that the user follows\n- Comments on tasks the user is involved with\n\n**~~CRM:**\n- Opportunity stage changes\n- New activities logged on accounts the user owns\n- Updated contacts or accounts\n\n**~~knowledge base:**\n- Recently updated documents in relevant collections\n- New documents created in watched areas\n\n### 4. Identify Key Items\n\nFrom all gathered activity, extract and categorize:\n\n**Action Items:**\n- Direct requests made to the user (\"Can you...\", \"Please...\", \"@user\")\n- Tasks assigned or due soon\n- Questions awaiting the user's response\n- Review requests\n\n**Decisions:**\n- Conclusions reached in threads or emails\n- Approvals or rejections\n- Policy or direction changes\n\n**Mentions:**\n- Times the user was mentioned or referenced\n- Discussions about the user's projects or areas\n\n**Updates:**\n- Status changes on projects the user follows\n- Document updates in the user's domain\n- Completed items the user was waiting on\n\n### 5. Group by Topic\n\nOrganize the digest by topic, project, or theme rather than by source. Merge related activity across sources:\n\n```\n## Project Aurora\n- ~~chat: Design review thread concluded — team chose Option B (#design, Tuesday)\n- ~~email: Sarah sent updated spec incorporating feedback (Wednesday)\n- ~~cloud storage: \"Aurora API Spec v3\" updated by Sarah (Wednesday)\n- ~~project tracker: 3 tasks moved to In Progress, 2 completed\n\n## Budget Planning\n- ~~email: Finance team requesting Q2 projections by Friday\n- ~~chat: Todd shared template in #finance (Monday)\n- ~~cloud storage: \"Q2 Budget Template\" shared with you (Monday)\n```\n\n### 6. Format the Digest\n\nStructure the output clearly:\n\n```\n# [Daily/Weekly] Digest — [Date or Date Range]\n\nSources scanned: ~~chat, ~~email, ~~cloud storage, [others]\n\n## Action Items (X items)\n- [ ] [Action item 1] — from [person], [source] ([date])\n- [ ] [Action item 2] — from [person], [source] ([date])\n\n## Decisions Made\n- [Decision 1] — [context] ([source], [date])\n- [Decision 2] — [context] ([source], [date])\n\n## [Topic/Project Group 1]\n[Activity summary with source attribution]\n\n## [Topic/Project Group 2]\n[Activity summary with source attribution]\n\n## Mentions\n- [Mention context] — [source] ([date])\n\n## Documents Updated\n- [Doc name] — [who modified, what changed] ([date])\n```\n\n### 7. Handle Unavailable Sources\n\nIf any source fails or is unreachable:\n```\nNote: Could not reach [source name] for this digest.\nThe following sources were included: [list of successful sources].\n```\n\nDo not let one failed source prevent the digest from being generated. Produce the best digest possible from available sources.\n\n### 8. Summary Stats\n\nEnd with a quick summary:\n```\n---\n[X] action items · [Y] decisions · [Z] mentions · [W] doc updates\nAcross [N] sources · Covering [time range]\n```\n\n## Notes\n\n- Default to `--daily` if no flag is specified\n- Group by topic/project, not by source — users care about what happened, not where it happened\n- Action items should always be listed first — they are the most actionable part of a digest\n- Deduplicate cross-source activity (same decision in ~~chat and email = one entry)\n- For weekly digests, prioritize significance over completeness — highlight what matters, skip noise\n- If the user has a memory system (CLAUDE.md), use it to decode people names and project references\n- Include enough context in each item that the user can decide whether to dig deeper without clicking through",
  "applicable_domains": [
    "search",
    "knowledge"
  ],
  "invocation": [
    "/digest",
    "/digest [--daily | --weekly | --since <date>]"
  ],
  "tags": [
    "enterprise-search",
    "anthropics",
    "knowledge-work"
  ],
  "authored_by": "anthropics",
  "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/enterprise-search/skills/digest/SKILL.md",
  "lifecycle": "stable",
  "category": "knowledge",
  "provenance": {
    "source": "anthropics/knowledge-work-plugins",
    "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/enterprise-search/skills/digest/SKILL.md",
    "author": "Anthropic",
    "license": "Apache-2.0",
    "notes": "Imported by scripts/import-anthropic-skills.py."
  }
}