call-summary
anthropics/knowledge-work-plugins
Extract action items, draft follow-ups, and summarize calls from notes or transcripts in seconds.
What is call-summary?
Process call notes or transcripts to automatically extract key discussion points, action items, objections, and competitive intel. Use after discovery, demo, or negotiation calls to generate internal summaries and customer follow-up emails without manual transcription work.
- Extract key discussion points and decisions from unstructured notes or transcripts
- Identify action items with owners and due dates
- Surface objections, concerns, and open questions
- Draft professional customer-facing follow-up emails
- Generate internal summaries for team logging and CRM
- Pull transcripts automatically when connected to Gong, Fireflies, or similar tools
How to install call-summary
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill call-summaryHow to use call-summary
- 1.Paste your call notes, transcript, or brief description of what happened
- 2.The skill will extract key discussion points, attendees, and decisions
- 3.Review the generated internal summary for accuracy
- 4.Customize the draft follow-up email as needed
- 5.If connectors are configured, optionally update your CRM, create tasks, or send the email directly
Use cases
- After a discovery call, quickly extract action items and send a follow-up email to the prospect
- Log a demo call activity in your CRM with structured summary and next steps
- Capture objections and competitive mentions from a negotiation call for your sales team
- Create tasks from a call without manually typing them out
- Generate a recap email when you only have rough notes or a voice memo transcript
- Sales professionals and account executives
- Business development managers
- Customer success and support teams
- Anyone conducting discovery, demo, or negotiation calls
call-summary FAQ
Any format works. You can paste bullet points, a full transcript from Zoom/Teams, rough notes, or even describe the call in your own words. More detail produces better output.
Yes, if you connect conversation intelligence tools like Gong or Fireflies. Otherwise, paste the transcript or notes manually.
When a CRM connector is configured, the skill can update opportunity stages, log activities, create tasks, and update next steps fields automatically.
If email is connected, you can approve and send the draft directly. Otherwise, copy the generated email and send it manually.
The skill works with any level of detail. Even incomplete notes help structure the summary and identify action items.
Full instructions (SKILL.md)
Source of truth, from anthropics/knowledge-work-plugins.
name: call-summary description: Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team. argument-hint: "<call notes or transcript>"
/call-summary
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Process call notes or a transcript to extract action items, draft follow-up communications, and update records.
Usage
/call-summary <notes or transcript>
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.
Related skills
More from anthropics/knowledge-work-plugins and the wider catalog.

campaign-plan
Generate structured marketing campaign briefs with objectives, audience, messaging, channels, content calendars, and success metrics.

canva-creator
>

capacity-plan
Analyze team capacity and forecast resource allocation for quarterly planning and hiring decisions.

cash-flow-snapshot
>

change-request
Create structured change requests with impact analysis, risk assessment, and rollback plans for system or process changes.

choose-zoom-approach
Choose the right Zoom architecture for a use case. Use when deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Zoom MCP, Phone, Contact Center, or a hybrid approach.