← ClaudeAtlas

call-preplisted

Prepares a customer call around the one thing it has to produce, rather than around what you plan to say. Trigger whenever the user says "call prep", "prep me for", "I have a call with", "meeting in an hour", "what should I ask", "what do I need to know before", "help me prepare for this call", "agenda for", "talking points for", or names a customer and an upcoming meeting in the same breath. Also trigger when they are walking into an account they have just inherited, or a call they are dreading. It names the outcome, works out who is really in the room, surfaces what changed on the customer's side, finds the landmine, writes the questions including the one they are avoiding, and sets the ask and the fallback ask. Use business-review when the meeting is a QBR or EBR, exec-conversation when the senior person is the point of the meeting, and hard-conversation when the job is delivering bad news. Runs on what the user knows and names what it could not check.
CSPulse/customer-success-skills · ★ 1 · Code & Development · score 67
Install: claude install-skill CSPulse/customer-success-skills
# Call Prep Most call prep is reading. You open the account, scan the notes, feel prepared, and walk into a meeting with no outcome attached to it. Preparation is not the same as reassurance. This skill produces the four things that change how a call goes: the outcome, the room, the questions, and the ask. The failure this exists to prevent: **the call that goes fine, generates a recap, and moves nothing.** Everyone leaves satisfied, the account is exactly where it was, and the next call has the same agenda. --- ## What this needs **Shared context.** If an `account-context` document exists, read it first. It carries the product, the segments, the contract shapes and what healthy looks like in this business, which is what stops the questions coming out generic. Where it is absent, carry on and name the assumption. **Minimum: who you are meeting and why.** Even a single line gets you an outcome, a set of questions and an ask. Everything unverified is marked unverified. **Better with** the last call's notes or recap, recent email history, and the invite with its attendee list. Those three convert most of the guesses into facts. **Best with** a stakeholder map and the account plan, because then the prep knows who is missing from the room rather than only who is in it. Nothing here is required. If the call is in ten minutes, skip to **The ten-minute version** at the bottom. --- ## When this runs Any customer call that is not a set piece: a check-in, a first meeting on