Skip to content
Back to skills

Post Call Debrief

ASecurity

Use when you've just finished a sales call and want to extract what happened fast. Runs a quick brain-dump-to-debrief in 5 minutes, delivered in chat.

  • 2 stars
  • 0 votes
  • 0 copies
  • 6 views
  • Added September 12, 2026
businessgo

Security analysis

A100/100

Scanned September 12, 2026

npx -y skills add Peter-Swain-Inc/psi-skills --skill post-call-debrief --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Post Call Debrief?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Post Call Debrief
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/peter-swain-inc-post-call-debrief/badge)](https://www.skillsdirectory.com/skills/peter-swain-inc-post-call-debrief)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: post-call-debrief
description: Use when you've just finished a sales call and want to extract what happened fast. Runs a quick brain-dump-to-debrief in 5 minutes, delivered in chat.
version: 1.0.0
author: Pete Swain / Hermes Agent
output_mode: chat
destination: direct chat response
---

## Overview

The 10 minutes immediately after a sales call are the most valuable learning window you have — and most people squander them by jumping straight to the next task. This skill turns a rough post-call brain dump into a structured, actionable debrief in under 5 minutes. It extracts the decision, the key signals, what resonated, what didn't, next steps, and one thing to do differently next time. Fast, direct, conversational — not a report.

## When to Use

- You say "debrief this call"
- You say "post-call"
- You say "just finished a sales call"
- You want to capture the details while they're fresh before they fade
- You're on a coaching or sales development programme and tracking your calls
- You had a call that went unexpectedly and want to process what happened

## How It Works

1. **Ask for the brain dump.** Say: *"Tell me what happened on the call — rough is fine. I'll ask follow-up questions to fill in any gaps."* Accept a stream-of-consciousness dump, bullet points, or a structured summary — whatever the user gives.

2. **Extract the core information.** From the brain dump, identify or ask about:

   **Decision status:**
   - What's the outcome? (Yes/moving forward, No/hard pass, Pending/needs to think, Needs more info, Referred to decision-maker)
   - If pending: what do they need, by when, and what's the agreed next step?

   **Objections raised:**
   - What did they push back on?
   - Were there concerns they voiced or ones you sensed but weren't spoken?
   - Were any objections resolved during the call, or are they still live?

   **What resonated:**
   - What made them lean in?
   - Which part of your offer, story, or framing got the most engagement?
   - Was there a moment you felt the energy shift positively?

   **What didn't land:**
   - Where did you lose energy or momentum?
   - Was there a section that felt flat or met with silence?
   - Did you say anything you'd take back?

   **Next steps committed to:**
   - What did you commit to? (Send a proposal, send a resource, book a follow-up call)
   - What did they commit to? (Review it by X, speak to Y, reply by Z)
   - What's the exact follow-up and timeline?

   **One thing to do differently:**
   - If you ran this call again tomorrow, what would you change?
   - What's the skill, framing, or habit to work on?

3. **Deliver the debrief.** Format clearly with 5 short sections — not paragraphs:
   - **Decision:** [one line]
   - **Objections:** [bullet list]
   - **What resonated:** [bullet list]
   - **What didn't land:** [bullet list]
   - **Next steps:** [numbered, with dates/owners]
   - **Do differently next time:** [one line]

4. **Add one forward action.** Based on the debrief, name the single most important thing to do in the next 24 hours to maximise the outcome of this call. Be specific: not "follow up" but "Send the proposal by 5pm today with a subject line referencing [specific pain point they mentioned]."

5. **Keep it conversational.** Ask one follow-up question at a time if details are missing. Don't interrogate — this is a thinking partner helping someone process a call, not a CRM form.

## What the Agent Needs From You

- **A brain dump** — whatever you remember, in whatever order it comes out
- The agent will ask targeted follow-up questions if anything critical is missing

## Output

Delivered in chat:
- 5-section debrief card: Decision, Objections, What Resonated, What Didn't, Next Steps
- One improvement observation (do differently next time)
- One forward action for the next 24 hours

No document needed. This is a fast, in-the-moment processing tool. If you want to save it, copy and paste into your CRM or notes app.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.