sales/skills/call-summary/SKILL.md
Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary
npx skillsauth add grailautomation/claude-plugins call-summaryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
/sales:call-summary <notes or transcript>
Process these call notes: $ARGUMENTS
If a file is referenced: @$1
┌─────────────────────────────────────────────────────────────────┐
│ 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 │
└─────────────────────────────────────────────────────────────────┘
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."
## 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]
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]
When drafting customer-facing emails:
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
Transcripts connected (e.g. Gong, Fireflies):
CRM connected:
Email connected:
gws gmail for Gmail delivery rather than Gmail MCP, and use --dry-run
or show the exact message before sending.development
Parse and analyze Workato recipe JSON exports. Use when the user asks about a Workato recipe's logic, data flow, field mappings, error handling, or control flow. Also use when the user references a .recipe.json file or asks to debug a Workato integration.
databases
Review implementation plans as a staff software engineer. Use when the user asks for staff engineer feedback, senior engineering review, plan review, architecture review, implementation-plan critique, approval before proceeding, risk review, or feedback on a proposed technical plan.
tools
Use when the user invokes $spec-kit:tasks or /spec-kit:tasks, or asks to generate dependency-ordered tasks from the plan and repo context.
testing
Use when the user invokes $spec-kit:specify or /spec-kit:specify, or asks to create a brownfield-aware feature specification from a natural language description.