conversation-digestlisted

Digest any long conversation, chat thread, support ticket, incident log, company announcement, or meeting notes into a structured summary — core problem, timeline, solution/recommendation, and action items, PLUS a personalized "what YOU need to do" section for the current user. Content can be pasted directly OR pulled automatically from a connected source (Slack thread, Notion page, Linear/Jira issue, Google Drive doc) via MCP. When the source is Slack, the skill auto-detects who the current user is from their Slack profile and highlights the items addressed to them. Use when someone needs to quickly understand "what is the actual problem here and what do I need to do" from a wall of text. Output language auto-matches the input (Vietnamese in → Vietnamese out; English in → English out).
Rayloveyou/claude-skills · ★ 0 · AI & Automation · score 67

Install: claude install-skill Rayloveyou/claude-skills

# Conversation Digest Turn a long, messy conversation into a short, decision-ready digest. Works on Slack/chat threads, support tickets, incident/debug logs, email chains, and meeting notes. ## When to use Activate this skill when the user: - Pastes a long thread/conversation/log and asks to "summarize", "tóm tắt", "what's the problem", "vấn đề là gì", "what should we do", or similar. - Points at a source instead of pasting: "digest Slack thread <link>", "tóm tắt ticket LINEAR-123", "summarize this Notion page", "tóm tắt meeting notes trong Drive". - Needs to catch up on a discussion they weren't part of. - Wants the decision, the fix, or the next steps extracted from noise. ## Input sources The content to digest can come from either: 1. **Pasted text** — the user drops the thread/log/notes straight into the prompt. Always works, no setup. 2. **A connected source via MCP** — the user gives a reference and the skill fetches the content itself. Supported when the matching MCP connector is authenticated: - **Slack** — a channel name or thread link → read the thread messages. - **Notion** — a page/database link or title → `notion-fetch` / `notion-search`. - **Linear** — an issue key/link → fetch issue + comments. - **Atlassian/Jira** — an issue key → fetch issue + comments. - **Google Drive** — a doc link/name → `read_file_content`. Discover the tool with ToolSearch (e.g. `select:notion-fetch` or a keyword search like `slack thread`), then call it. If the