Back to Skills

call-summary

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.

22,281stars2,609forksUpdated 7/2/2026

Security Assessment

Safe(100/100)
Security Score100/100

About call-summary

A slash command that turns raw call notes or a full transcript into structured, ready-to-use outputs for sales and customer-facing teams. It fits the moment right after a discovery, demo, negotiation, or check-in call, when you have messy notes or a transcript and need an internal summary, a customer follow-up, and a clean list of action items and next steps. It works standalone with nothing more than pasted text, and can accept bullet points, stream-of-consciousness notes, a verbatim transcript, or even a short description of what happened.

From that input it extracts key discussion points and decisions, identifies action items with owners and due dates, surfaces objections, concerns, and open questions, and captures any competitive intelligence. Two artifacts are produced: an internal summary structured with attendees, call type, customer priorities, objections, an action-item table, next steps, and deal impact; and a customer-facing follow-up email. The email follows explicit style guidelines that favor concise plain text over markdown, short scannable paragraphs, and simple dashes instead of bold formatting, so the draft reads naturally in any email client.

When connectors are available the workflow is extended rather than replaced. Connected conversation-intelligence tools such as Gong or Fireflies let it locate and pull the transcript automatically and lift platform-flagged key moments; a connected CRM enables updating the opportunity stage, logging the call as an activity, and creating tasks from action items; a connected email tool can draft or send the follow-up; and a calendar connection supplies attendee context. Practical tips note that more detail yields better output, naming attendees improves structure and action-item assignment, and stating the deal stage tailors the follow-up tone.

FAQ

Do I need any tools connected to use it?

No. It always works standalone from pasted notes, a transcript, or a short description; connectors for transcripts, CRM, email, and calendar only supercharge it.

What does it produce?

An internal summary covering attendees, discussion points, customer priorities, objections, an action-item table, next steps, and deal impact, plus a customer-facing follow-up email.

Why is the follow-up email in plain text?

The style guidelines call for concise plain text with no markdown, short scannable paragraphs, and simple dashes, so it renders naturally in any email client.

What can it pull from connected tools?

It can auto-locate and pull transcripts from tools like Gong or Fireflies, update the CRM opportunity and create tasks, draft or send the email, and pull attendee context from the calendar.

How can I get the best summary?

Provide as much detail as you can, name the attendees, flag what mattered most, and tell it the deal stage so it can tailor the follow-up tone and next steps.

Install call-summary

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill