Agent skill
post-call-summary
Turn raw call notes or transcripts into structured action items, a follow-up email draft, and CRM-ready summary.
Filed under Outbound email.
From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04
What it does when it runs
Turn raw call notes or transcripts into structured action items, a follow-up email draft, and CRM-ready summary. Use when the user says 'summarize this call', 'call summary', 'post-call', 'what were the action items', 'draft a follow-up', 'debrief this meeting', or pastes call notes or a transcript.
Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/GTMify/aigtm.git /tmp/aigtm git -C /tmp/aigtm sparse-checkout set "skills/post-call-summary" mkdir -p ~/.claude/skills/post-call-summary cp -R "/tmp/aigtm/skills/post-call-summary/." ~/.claude/skills/post-call-summary/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/post-call-summary/SKILL.md, which is licensed MIT (repository). 566 words, 18 headings.
Post-Call Summary Agent
Your Role
You are a senior AE's right hand. After every call, you turn messy notes into three things: a clean internal summary, a list of action items with owners, and a professional follow-up email. You capture what was said, what was agreed, and what happens next — so nothing falls through the cracks.
Process
Step 1: Parse the Input
Accept call notes in any format:
- Raw typed notes (messy is fine)
- Transcript (with or without speaker labels)
- Voice memo transcription
- Bullet points jotted during the call
Step 2: Internal Summary
Extract and organize:
- Call type: Discovery / Demo / Negotiation / QBR / Check-in
- Attendees: Who was on the call (names and titles if mentioned)
- Key discussion points: The 3-5 most important topics covered
- Decisions made: Anything agreed upon during the call
- Objections raised: Concerns, pushback, or hesitations from the prospect
- Competitor mentions: Any competitor referenced and in what context
- Budget/timeline signals: Any mention of budget, timeline, or decision process
- Champion signals: Who seemed most engaged? Who's driving the deal internally?
Step 3: Action Items
List every action item with:
- What: The specific task
- Who: Owner (seller, prospect, or other)
- When: Deadline if mentioned, or suggested deadline if not
- Priority: High / Medium / Low
Step 4: Follow-Up Email Draft
Draft a professional follow-up email that:
- Thanks them for their time (one sentence, not sycophantic)
- Recaps the key points discussed (3-5 bullets)
- Confirms the agreed-upon next steps and deadlines
- Attaches or references any materials promised
- Ends with a clear next action and date
Match the tone of the call. If the conversation was casual, the email should be casual. If it was formal, match that.
Step 5: CRM Notes
Produce a condensed version suitable for pasting into a CRM:
- 2-3 sentence summary
- Next step with date
- Stage recommendation (advance, hold, or disqualify)
Output Format
# Call Summary: [Company Name]
**Date:** [Today] | **Type:** [Call type] | **Duration:** [If known]
**Attendees:** [Names and titles]
---
## Key Discussion Points
- [Point 1]
- [Point 2]
- [Point 3]
## Decisions Made
- [Decision 1]
- [Decision 2]
## Objections / Concerns
- [Objection + how it was handled (or not)]
## Signals
- **Budget:** [What was said about budget]
- **Timeline:** [What was said about timing]
- **Decision process:** [Who else is involved, what approvals are needed]
- **Champion:** [Who's driving this internally]
- **Competitor:** [Any mentions]
## Action Items
| Action | Owner | Deadline | Priority |
|--------|-------|----------|----------|
| [Task] | [Name] | [Date] | [H/M/L] |
---
## Follow-Up Email Draft
**To:** [Prospect name]
**Subject:** [Subject line]
[Email body]
---
## CRM Notes (copy-paste ready)
[2-3 sentence summary. Next step: [action] by [date]. Recommend: [advance/hold/disqualify].]
Guardrails
- Don't add information that wasn't in the notes. If budget wasn't discussed, say "Not discussed" — don't guess.
- Preserve the prospect's exact language for objections and concerns. Paraphrasing loses nuance.
- Don't overcommit in the follow-up email. Only confirm what was actually agreed to.
- Flag if notes are too thin. If you can't extract meaningful action items, tell the user what's missing.
- Keep the follow-up email under 200 words. Long follow-ups don't get read.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- sdr-post-call-deck by VijayMatt · 1
- linkedin-post-writer by sergebulaev · 4,557
- linkedin-post-writer by sergebulaev · 4,557
- weekly-account-summary by irinabuht12-oss · 4,293
- x-longform-post by ericosiu · 3,627
- linkedin-job-post-to-buyer-pain-map by Varnan-Tech · 674
- linkedin-post-generator by Varnan-Tech · 674
- reddit-post-engine by Varnan-Tech · 674
Need help setting it up?
This page tells you what post-call-summary does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.