sales-call-debrief
Skill1 starsChanged 17 days agoMITView on GitHub
Use this skill in the ten minutes after a first call or pitch, while it is still fresh and before the next one starts. Produces the record update, the follow-up written in their words, and an honest read on whether this is real. Also use for "debrief that call", "write the follow-up", "update the deal", "was that a good call".
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- client-win-backSkill
- late-payment-chaseSkill
- network-path-mappingSkill
- rate-increase-planSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- ceo-exec-assistantSkill
- og-image-from-templateSkill
- weekly-site-and-ad-reportSkill
- icp-reviewSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- kondo-owed-reply-sweepSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- riverside-short-social-scheduleSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- linkedin-shoutout-postSkill
- plain-language-copy-checkSkill
- revenue-goal-funnel-mathSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Write the follow-up in their language, not the firm's.
- Distinctive: line 29
Update the record with the verbatim lines, the category and the dated next step.
- Distinctive: line 42
MUST debrief within ten minutes of the call ending.
- Distinctive: line 43
MUST capture verbatim phrasing before writing any assessment.
- Distinctive: line 44
MUST qualify against the same criteria every time.
- Distinctive: line 45
MUST categorise honestly, including "not", and act on it.
- Distinctive: line 46
MUST write the follow-up in their words, with a dated next step.
- Distinctive: line 47
MUST record a next step with a date, or no stage change.
- Distinctive: line 48
NEVER treat interest with no named problem as qualified.
- Distinctive: line 49
NEVER let a call with no decision-maker produce a proposal as its next step.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Applies immediately after a first call with a prospect. Produces three things in ten minutes: the record, the follow-up, and a qualification call that is honest rather than hopeful.
The play
- Do it within ten minutes, before the next call. The specific phrasing a prospect used is gone within the hour, and the phrasing is the most valuable thing the call produced. A debrief written at the end of the day is a summary of a summary.
- Capture their words first, before any assessment. Three to five verbatim lines: how they described the problem, the number they volunteered, what they have already tried, what they said about timing. What to capture and why verbatim matters is in references/capture-first.md.
- Then qualify, against the same criteria every time. Fit, problem, authority, timing, and whether there is a real next step with a date. The bar for each, and the rule for what counts as a real next step, are in references/qualification.md. Qualify after capturing, never during, because judging while listening is how a call gets heard as better than it was.
- Decide the honest category: real, maybe, or not. Most firms have no "not" category, which is why their pipeline is three times its actual size. The categories and what each one means for next steps are in references/qualification.md.
- Branch by what the call produced:
- Clear problem, clear owner, a date: write the follow-up and the proposal path.
- Clear problem, no authority in the room: the next step is access, not a proposal. Write the follow-up to the person who was there, asking who else needs to be in it.
- Interest with no problem named: not qualified, whatever the enthusiasm. Interest is not a buying signal and is the single most common reason a pipeline is full of nothing.
- Problem named, no timing, no trigger: real but not now. Record the trigger that would change that, and set a date to check.
- They talked about price unprompted and early: usually a budget they already have, sometimes a brush-off. The follow-up should ask what it needs to fit inside.
- Write the follow-up in their language, not the firm's. Quote their phrasing back, name the next step and its date, and keep it short. The structure is in references/the-follow-up.md.
- Update the record with the verbatim lines, the category and the dated next step. A record with a stage and no next step is a record that will be guessed at in three weeks.
- Send the follow-up the same day. Next-day follow-ups land into a different context and read as routine.
What good looks like
- First thing I check that most people skip: whether they named a problem or just expressed interest. Enthusiasm on a call is pleasant and predicts nothing; a specific problem with a cost attached predicts almost everything.
- The mediocre version: a one-line note saying "good call, following up", a stage bumped on optimism, and a follow-up email that restates what the firm does. Three weeks later nobody can remember what the prospect actually wanted.
- I know the debrief is right when the follow-up contains a sentence the prospect would recognise as their own.
- Second test: the category is honest. A debrief where every call comes out as "real" is not a qualification process.
- Red flag: the record has a stage change and no next step with a date. The stage moved because the call felt good.
Rules
- MUST debrief within ten minutes of the call ending.
- MUST capture verbatim phrasing before writing any assessment.
- MUST qualify against the same criteria every time.
- MUST categorise honestly, including "not", and act on it.
- MUST write the follow-up in their words, with a dated next step.
- MUST record a next step with a date, or no stage change.
- NEVER treat interest with no named problem as qualified.
- NEVER let a call with no decision-maker produce a proposal as its next step.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

