The Call Prep Skill — a Working Reference Implementation
The previous sheet said a confidence-labeled prep routine was "worth building yourself." This is that routine, built, not just recommended.
Mod 08+ makes the case for starting with the admin layer and for labeling every researched fact by confidence before it goes anywhere near a customer. presales-call-prep is a small Claude Code skill that does exactly that, for the two moments in a deal where prep work is most repetitive: the ten minutes before a call, and the ten minutes after one.
What it does
| Mode | Input | Output |
|---|---|---|
prep | Whatever you already know — a company/URL, deal stage, attendees, prior notes | A short brief: labeled Verified/Inferred/Not‑found facts, 6–8 questions pulled from Template 1's question bank and tailored to the deal stage, and a list of what's still missing |
capture | A pasted call transcript or your own notes | A discovery grid in the exact problem → impact → outcome → owner shape the live tool below already uses, each row tagged Stated/Inferred/Unclear, plus a list of which of the six discovery categories got zero coverage on the call |
Why this, and not more
It is deliberately paste-based — no CRM connection, no calendar, no Microsoft Graph integration. That is a scope decision, not a limitation nobody noticed: it means the skill works for anyone who installs it, regardless of what tenant, license, or admin access they have, and it means nothing here can push data anywhere on its own. Auto-pulling a Teams transcript or a calendar invite is listed in the file itself as a roadmap item, not claimed as already working.
Guardrails, carried over from the rest of this manual
- Never fabricate a fact, name, or number — "not found" or "unclear" is a correct answer, not a failure
- Every researched claim is labeled by confidence, the label is never dropped partway through a sentence
- Nothing it produces goes to a CRM or a customer unread — it drafts, a person reviews, exactly like Module 12's rule for AI‑drafted RFP answers
- It doesn't write to the browser tool's storage directly — that's a genuine security boundary (a page can't be written to from outside itself), so
capturemode outputs a copy‑paste‑ready JSON block instead of pretending to sync
Try it now — nothing to install
The skill above needs Claude Code installed to get the AI-assisted research and drafting. These two don't — they run right here in the page, do the same job for the two moments above without calling any AI, and save to this browser only, same as every other tool in this manual.
.claude/skills/ directory (project-level or global) to use it.