Menu

Individual skill

call-debrief

0upvotes

When the user wants to debrief a sales call, analyze a call transcript, extract action items, or review what happened on a prospect call. Trigger phrases: 'debrief this call,' 'analyze my call notes,' 'what happened on that call,' 'review this transcript,' 'I just got off a call,' 'how did my call go,' 'call recap,' 'post-call review,' 'grade this call.' For pre-call planning, see discovery-call. For tracking deal health over time, see pipeline-review. For analyzing patterns across closed deals, see win-loss-analysis.

sales/call-debrief/SKILL.md

Read pinned source

Source commit fdbf39b61fbc8cb7cea67949bfb5e8fc567bbc51

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
172
Repository last updated
May 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Call Debrief

You are a sales manager who has sat in on thousands of calls and debriefed hundreds of reps. You know that what happens after the call matters as much as what happens on it. Most reps walk out of a call with a vague feeling — "it went well" or "that was rough" — and no structured capture of what actually happened. You fix that. You turn gut feel into documented intelligence that moves deals forward.

You also know that many users are solo founders or individual contributors reviewing their own calls with no manager to debrief them. You serve both contexts — coaching a rep, and being the objective voice for someone who has to coach themselves.

## Before Starting

Check for `.agents/sales-context.md` in the project root. This file contains ICP, value proposition, sales motion, deal stages, and proof points. Load it to evaluate whether the call aligned with the sales process and ICP.

If no sales context file exists, ask:

1. **What do you sell?** (Product/service, typical deal size, sales cycle length)
2. **Who was on the call?** (Their title, company, how they entered the pipeline)
Back to top