--- id: daily-call-summary name: "call-summary" url: https://skills.yangsir.net/skill/daily-call-summary author: anthropics domain: sales tags: ["sales-enablement", "crm", "lead-qualification", "b2b-sales"] install_count: 1200 rating: 4.30 (20 reviews) github: https://github.com/anthropics/knowledge-work-plugins --- # call-summary > 自动分析销售通话记录或转录文本，提取关键行动项、客户痛点和跟进任务，生成结构化的会议摘要 **Stats**: 1,200 installs · 4.3/5 (20 reviews) ## Before / After 对比 ### 通话记录处理 **Before**: 销售代表需要反复收听录音或阅读冗长的转录文本，手动标记客户需求、承诺事项和下一步行动，容易遗漏关键信息，一份 30 分钟通话的整理需要 20 分钟 **After**: 上传通话录音或转录文本，自动识别客户意图、决策因素和异议点，提取所有承诺和行动项，按优先级排序并生成 CRM 可直接导入的摘要，2 分钟完成完整分析 | Metric | Before | After | Change | |---|---|---|---| | 通话处理时间 | 20分钟 | 2分钟 | -90% | ## Readme # call-summary # /call-summary If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/sales/skills/call-summary/../../CONNECTORS.md). Process call notes or a transcript to extract action items, draft follow-up communications, and update records. ## Usage ``` /call-summary ``` Process these call notes: $ARGUMENTS If a file is referenced: @$1 ## How It Works ``` ┌─────────────────────────────────────────────────────────────────┐ │ CALL SUMMARY │ ├─────────────────────────────────────────────────────────────────┤ │ STANDALONE (always works) │ │ ✓ Paste call notes or transcript │ │ ✓ Extract key discussion points and decisions │ │ ✓ Identify action items with owners and due dates │ │ ✓ Surface objections, concerns, and open questions │ │ ✓ Draft customer-facing follow-up email │ │ ✓ Generate internal summary for your team │ ├─────────────────────────────────────────────────────────────────┤ │ SUPERCHARGED (when you connect your tools) │ │ + Transcripts: Pull recording automatically (e.g. Gong, Fireflies) │ │ + CRM: Update opportunity, log activity, create tasks │ │ + Email: Send follow-up directly from draft │ │ + Calendar: Link to meeting, pull attendee context │ └─────────────────────────────────────────────────────────────────┘ ``` ## What I Need From You **Option 1: Paste your notes** Just paste whatever you have — bullet points, rough notes, stream of consciousness. I'll structure it. **Option 2: Paste a transcript** If you have a full transcript from your video conferencing tool (e.g. Zoom, Teams) or conversation intelligence tool (e.g. Gong, Fireflies), paste it. I'll extract the key moments. **Option 3: Describe the call** Tell me what happened: "Had a discovery call with Acme Corp. Met with their VP Eng and CTO. They're evaluating us vs Competitor X. Main concern is integration timeline." ## Output ### Internal Summary ``` ## Call Summary: [Company] — [Date] **Attendees:** [Names and titles] **Call Type:** [Discovery / Demo / Negotiation / Check-in] **Duration:** [If known] ### Key Discussion Points 1. [Topic] — [What was discussed, decisions made] 2. [Topic] — [Summary] ### Customer Priorities - [Priority 1 they expressed] - [Priority 2] ### Objections / Concerns Raised - [Concern] — [How you addressed it / status] ### Competitive Intel - [Any competitor mentions, what was said] ### Action Items | Owner | Action | Due | |-------|--------|-----| | [You] | [Task] | [Date] | | [Customer] | [Task] | [Date] | ### Next Steps - [Agreed next step with timeline] ### Deal Impact - [How this call affects the opportunity — stage change, risk, acceleration] ``` ### Customer Follow-Up Email ``` Subject: [Meeting recap + next steps] Hi [Name], Thank you for taking the time to meet today... [Key points discussed] [Commitments you made] [Clear next step with timeline] Best, [You] ``` ## Email Style Guidelines When drafting customer-facing emails: - **Be concise but informative** — Get to the point quickly. Customers are busy. - **No markdown formatting** — Don't use asterisks, bold, or other markdown syntax. Write in plain text that looks natural in any email client. - **Use simple structure** — Short paragraphs, line breaks between sections. No headers or bullet formatting unless the customer's email client will render it. - **Keep it scannable** — If listing items, use plain dashes or numbers, not fancy formatting. **Good:** ``` Here's what we discussed: - Quote for 20 seats at $480/seat/year - W9 and supplier onboarding docs - Point of contact for the contract ``` **Bad:** ``` **What You Need from Us:** - Quote for 20 seats at $480/seat/year ``` ## If Connectors Available **Transcripts connected (e.g. Gong, Fireflies):** - I'll search for the call automatically - Pull the full transcript - Extract key moments flagged by the platform **CRM connected:** - I'll offer to update the opportunity stage - Log the call as an activity - Create tasks for action items - Update next steps field **Email connected:** - I'll offer to create a draft in ~~email - Or send directly if you approve ## Tips - **More detail = better output** — Even rough notes help. "They seemed concerned about X" is useful context. - **Name the attendees** — Helps me structure the summary and assign action items. - **Flag what matters** — If something was important, tell me: "The big thing was..." - **Tell me the deal stage** — Helps me tailor the follow-up tone and next steps. Weekly Installs285Repository[anthropics/know…-plugins](https://github.com/anthropics/knowledge-work-plugins)GitHub Stars10.5KFirst Seen14 days agoSecurity Audits[Gen Agent Trust HubPass](/anthropics/knowledge-work-plugins/call-summary/security/agent-trust-hub)[SocketPass](/anthropics/knowledge-work-plugins/call-summary/security/socket)[SnykWarn](/anthropics/knowledge-work-plugins/call-summary/security/snyk)Installed oncodex274gemini-cli272opencode271cursor271github-copilot270amp270 --- *Source: https://skills.yangsir.net/skill/daily-call-summary* *Markdown mirror: https://skills.yangsir.net/api/skill/daily-call-summary/markdown*