agentleFS
stephenroganstephenrogan/csm-skills/skills/pre-call-prep/SKILL.md

pre-call-prep

Skill0 starsChanged 8 months agoMITView on GitHub

Builds a structured pre-call brief from manually provided account context. Produces talking points, questions to ask, risks to address, and a clear call objective. Use when asked to prepare for a customer call, build talking points, create a pre-meeting brief, structure a call agenda, or when a CSM has a call in 30 minutes and needs to walk in prepared. Also triggers for questions about call preparation, meeting readiness, talking point development, or structuring a productive customer conversation.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Call type (check-in, QBR, escalation, renewal, first meeting, ad hoc)

    line 19
  2. Distinctive:

    Before every call, write one sentence: "This call is successful if [specific outcome]."

    line 107
  3. Distinctive:

    If you cannot write a specific objective, either (a) you need more preparation or (b) the call does not need to happen.

    line 116

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Pre-Call Prep

Builds a structured brief for any customer call. The 10 minutes you spend preparing determine whether the call advances the relationship or wastes everyone's time.

How to Use

Provide whatever you know:

  • Account name, ARR, health status
  • Call type (check-in, QBR, escalation, renewal, first meeting, ad hoc)
  • Who is attending (customer contacts and internal team)
  • Last touchpoint (what was discussed, any open items)
  • Current account situation (health, usage, engagement, open issues)
  • What you want to accomplish (the objective of this specific call)
  • Anything you are worried about (risk signals, difficult topics, relationship concerns)

The 5-Minute Brief

For routine calls, the skill produces a 5-minute brief:

## Pre-Call Brief: [Account Name]
**Date:** [date] | **Type:** [type] | **Duration:** [expected]

### Call Objective
[One sentence: what does success look like when this call ends?]

### Context (30-Second Refresh)
[Account name] | EUR [ARR] | [Health] | [Renewal: date]
Last touch: [date, what happened]
Open items: [any commitments pending from either side]

### Talking Points (In Priority Order)
1. [Most important topic -- the one you must cover even if the call runs short]
2. [Second priority]
3. [Third priority -- cover if time allows]

### Questions to Ask
- [Question 1 -- genuine information-gathering, not leading]
- [Question 2]

### Watch For
- [Signal to listen for -- competitive mention, sentiment shift, new information]

### Do Not Forget
- [Open item to close, commitment to confirm, or follow-up to mention]

Prep by Call Type

Check-In Call

ElementContent
ObjectiveMaintain the relationship. Surface any changes. Offer value
Lead withSomething specific to their account (usage observation, upcoming event, open item status)
Ask aboutTheir priorities this quarter, any changes, any concerns
AvoidRunning through a generic checklist. If you have nothing specific, reconsider whether this call should happen

QBR / Business Review

ElementContent
ObjectiveDemonstrate value. Align on direction. Identify expansion or risk
Lead withValue evidence (the headline number they should take away)
PrepareDeck or data (from qbr-content-assembler), discussion questions, strategic recommendation
AvoidData dump without narrative. QBR is a conversation, not a presentation

Escalation / Issue Review

ElementContent
ObjectiveShow accountability. Provide an update. Confirm resolution path
Lead withThe update -- what has been done since the last conversation. Do not make them ask
PrepareTimeline, resolution status, next steps, any asks of the customer
AvoidDefensive language. Do not explain why the issue is hard. Explain what is being done

Renewal Conversation

ElementContent
ObjectiveConfirm value. Initiate the commercial conversation. Understand their position
Lead withValue delivered (use the value-narrative-builder output)
PrepareRenewal pricing, objection responses (from pricing-conversation-framework), competitive readiness
AvoidJumping to the commercial discussion before establishing value. Value first, then pricing

First Meeting with New Contact

ElementContent
ObjectiveBuild the relationship. Understand their priorities. Establish credibility
Lead withA brief introduction and a genuine question about their priorities
PrepareResearch on their role and likely concerns (from stakeholder-research-prep)
AvoidPresenting. First meetings should be 70% listening, 30% responding

The Call Objective Test

Before every call, write one sentence: "This call is successful if [specific outcome]."

Good ObjectivesBad Objectives
"Confirm Tom supports the renewal and identify any blockers""Discuss the renewal"
"Understand Lisa's priorities for Q2 and identify one way our product supports them""Check in with Lisa"
"Get agreement to schedule a QBR for April""Talk about doing a QBR"
"Confirm the escalation is resolved from the customer's perspective""Follow up on the issue"

If you cannot write a specific objective, either (a) you need more preparation or (b) the call does not need to happen.

Output

The skill produces:

  • The structured brief (5-minute or full depending on call complexity)
  • The call objective (one sentence)
  • Talking points in priority order (most important first)
  • Questions to ask (genuine, not leading)
  • Signals to watch for (competitive, sentiment, political)
  • Post-call actions to plan (follow-up email, CRM update, internal debrief if warranted)

Quality Gates

  • Does the brief have a clear objective? Not a topic -- an objective with a definition of success
  • Are the talking points prioritised? If the call runs short, will you have covered the most important item?
  • Is there at least one genuine question? A call where you only talk and never ask is a presentation, not a conversation
  • Are open items from the last touchpoint addressed? Walking into a call without knowing what was promised last time is a credibility failure
  • Can you complete this prep in under 10 minutes? If the prep is longer than the call, the tool is not working

Principles

  • Preparation is respect for the customer's time. Walking into a call unprepared wastes 30 minutes of their day. 10 minutes of preparation creates 30 minutes of value
  • The objective is the anchor. If the conversation drifts, the objective brings it back. If the customer takes the conversation in a new direction, the objective helps you assess whether that direction is more valuable than what you planned
  • Priority order saves bad calls. If the internet drops at minute 15, you have covered the most important topic. If the customer takes the call in a different direction, you covered the critical item before the drift
  • The best calls feel like a conversation, not a checklist. The prep provides structure. Your skill as a CSM provides the responsiveness, empathy, and judgment that make the conversation valuable

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.