{"skill":{"slug":"cm-conversation-summarizer","displayName":"Conversation Summarizer","summary":"Summarize long conversations, chat histories, and discussion threads into structured summaries with key decisions, action items, and topics — optimized for m...","description":"---\nname: conversation-summarizer\ndescription: Summarize long conversations, chat histories, and discussion threads into structured summaries with key decisions, action items, and topics — optimized for meeting notes, Slack threads, and support tickets.\nmetadata:\n  tags: [\"summarization\", \"conversation\", \"meeting-notes\", \"productivity\", \"ai\"]\n---\n\n# Conversation Summarizer\n\nSummarize long conversations, chat histories, meeting transcripts, and discussion threads into structured, actionable summaries. Extracts key decisions, action items, topics discussed, and open questions. Optimized for meeting notes, Slack/Discord threads, email chains, and support tickets.\n\n## Usage\n\n```\n\"Summarize this meeting transcript\"\n\"Extract action items from this Slack thread\"\n\"Create meeting notes from this conversation\"\n\"Summarize the last 50 messages in this channel\"\n\"Turn this email chain into a decision log\"\n```\n\n## How It Works\n\n### 1. Input Processing\n\nAccept conversations from various sources:\n\n- Meeting transcripts (Zoom, Google Meet, Teams recordings)\n- Chat logs (Slack, Discord, Telegram, Teams messages)\n- Email threads (forwarded or parsed)\n- Support ticket conversations\n- Forum/discussion threads\n- Raw text conversations\n\n### 2. Conversation Analysis\n\nParse and analyze the conversation structure:\n\n**Participant mapping:**\n- Identify unique speakers/authors\n- Track who said what\n- Note speaker changes and patterns\n\n**Topic segmentation:**\n- Identify distinct topics discussed\n- Track topic transitions\n- Note topic duration/depth\n\n**Sentiment tracking:**\n- Agreement vs disagreement moments\n- Emotional shifts\n- Consensus building\n\n**Decision identification:**\n- Explicit decisions: \"We've decided to...\"\n- Implicit agreements: \"Sounds good, let's go with that\"\n- Deferred decisions: \"Let's revisit this next week\"\n- Vetoes: \"No, we can't do that because...\"\n\n### 3. Summary Generation\n\nProduce structured summaries at different detail levels:\n\n**Executive summary (1-3 sentences):**\n- What was discussed, what was decided, what's next\n\n**Standard summary:**\n- Topics covered with key points\n- Decisions made with rationale\n- Action items with owners and deadlines\n- Open questions and unresolved issues\n\n**Detailed summary:**\n- Full topic breakdown with context\n- Supporting arguments for decisions\n- Minority opinions and concerns raised\n- Reference to specific statements\n\n### 4. Action Item Extraction\n\nExtract and structure action items:\n\n```\n## Action Items\n\n- [ ] @sarah: Update the API docs with new endpoints (by Friday)\n- [ ] @mike: Set up staging environment for load testing (by EOD)\n- [ ] @team: Review the RFC draft and add comments (by next Monday)\n- [ ] @alex: Schedule follow-up meeting with vendor (this week)\n```\n\nRules for extraction:\n- Must have a clear owner (person or team)\n- Must have a specific deliverable\n- Extract deadlines when mentioned\n- Flag items without clear deadlines\n- Distinguish between commitments and suggestions\n\n### 5. Decision Log\n\nDocument decisions for organizational memory:\n\n```\n## Decisions\n\n1. **Migrate from PostgreSQL to CockroachDB** (approved)\n   - Rationale: Need multi-region, active-active replication\n   - Proposed by: @sarah\n   - Concerns: @mike raised migration complexity\n   - Timeline: Q3 2026\n\n2. **Keep current pricing tier structure** (decided)\n   - Rationale: Churn data doesn't support adding a new tier\n   - Alternative rejected: Enterprise tier with custom pricing\n   - Review date: After Q3 metrics review\n```\n\n### 6. Key Quotes\n\nPreserve important verbatim quotes:\n\n```\n## Notable Quotes\n\n> \"We're optimizing for developer experience over raw performance here\"\n> — @sarah, on the framework decision\n\n> \"If we don't fix the onboarding flow this quarter, we'll lose another 15% in trial conversion\"\n> — @mike, escalating the onboarding project priority\n```\n\n### 7. Output Formats\n\nGenerate summaries in different formats:\n\n- **Markdown**: For docs, wikis, Notion\n- **Slack message**: For thread summaries with mentions\n- **Email**: For sending to absent participants\n- **JIRA/Linear**: For creating follow-up tickets\n- **Calendar**: For scheduling follow-up meetings\n\n## Output\n\n```\n## Meeting Summary: API Redesign Discussion\n**Date:** 2026-04-30 | **Duration:** 47 min | **Participants:** 5\n\n### TL;DR\nTeam agreed to adopt REST with OpenAPI 3.1 for the public API (dropping GraphQL consideration). Migration starts Q3 with a 6-month deprecation window for v1 endpoints. Sarah owns the RFC.\n\n### Topics Discussed\n\n**1. API Architecture (25 min)**\n- Compared REST vs GraphQL for the public API\n- GraphQL rejected due to: client complexity, caching difficulties, security surface area\n- REST with OpenAPI 3.1 chosen for: tooling ecosystem, easier rate limiting, client library generation\n- Will use JSON:API spec for consistent response format\n\n**2. Migration Plan (15 min)**\n- v1 endpoints get 6-month deprecation window\n- v2 will be versioned via URL path (/v2/...)\n- SDKs will be auto-generated from OpenAPI spec\n- Breaking changes require RFC approval\n\n**3. Timeline (7 min)**\n- RFC due: May 15\n- Design review: May 22\n- Implementation start: June 1\n- Beta: August 1\n- GA: September 15\n\n### Decisions\n1. ✅ Use REST + OpenAPI 3.1 (not GraphQL)\n2. ✅ 6-month deprecation window for v1\n3. ⏳ SDK language priority — decide after RFC review\n\n### Action Items\n- [ ] @sarah: Write API v2 RFC (by May 15)\n- [ ] @mike: Inventory all v1 endpoints and usage stats (by May 10)\n- [ ] @alex: Evaluate OpenAPI generators for Python/JS/Go (by May 12)\n- [ ] @sarah: Schedule design review meeting (May 22)\n\n### Open Questions\n- Should we offer a self-hosted API option?\n- How to handle webhook backward compatibility?\n- Need legal review on API terms of service changes\n\n### Parking Lot\n- Rate limiting strategy (separate discussion needed)\n- API key management overhaul (Q4 candidate)\n```\n","tags":{"latest":"1.0.0"},"stats":{"comments":0,"downloads":358,"installsAllTime":0,"installsCurrent":0,"stars":0,"versions":1},"createdAt":1777944014011,"updatedAt":1778492846193},"latestVersion":{"version":"1.0.0","createdAt":1777944014011,"changelog":"Initial release of Conversation Summarizer.\n\n- Summarizes long conversations, chat logs, and transcripts into structured summaries.\n- Extracts topics, key decisions, action items (with owners and deadlines), and open questions.\n- Captures notable quotes, tracks sentiment and consensus, and segments discussion topics.\n- Optimized output formats for meeting notes, Slack/Discord threads, support tickets, and emails.\n- Supports multiple summary detail levels (executive, standard, detailed).\n- Outputs in Markdown, Slack message, email, JIRA/Linear ticket, and calendar formats.","license":"MIT-0"},"metadata":null,"owner":{"handle":"charlie-morrison","userId":"s17cttbdxry5kkyafjw983mq8s83p4y3","displayName":"charlie-morrison","image":"https://avatars.githubusercontent.com/u/271589886?v=4"},"moderation":null}