Skip to main content

post-call-summary

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.

소스 정보

저장소
GTMify/aigtm
최근 소스 활동
2026년 3월 20일 05:24
감지된 SKILL.md 언어
영어
스타
25
포크
12

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
3 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
post-call-summary
description
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.
# 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.
GitHub에서 보기