skills/pre-call-prep/SKILL.md
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.
npx skillsauth add stephenrogan/csm-skills pre-call-prepInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Provide whatever you know:
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]
| Element | Content | |---------|---------| | Objective | Maintain the relationship. Surface any changes. Offer value | | Lead with | Something specific to their account (usage observation, upcoming event, open item status) | | Ask about | Their priorities this quarter, any changes, any concerns | | Avoid | Running through a generic checklist. If you have nothing specific, reconsider whether this call should happen |
| Element | Content | |---------|---------| | Objective | Demonstrate value. Align on direction. Identify expansion or risk | | Lead with | Value evidence (the headline number they should take away) | | Prepare | Deck or data (from qbr-content-assembler), discussion questions, strategic recommendation | | Avoid | Data dump without narrative. QBR is a conversation, not a presentation |
| Element | Content | |---------|---------| | Objective | Show accountability. Provide an update. Confirm resolution path | | Lead with | The update -- what has been done since the last conversation. Do not make them ask | | Prepare | Timeline, resolution status, next steps, any asks of the customer | | Avoid | Defensive language. Do not explain why the issue is hard. Explain what is being done |
| Element | Content | |---------|---------| | Objective | Confirm value. Initiate the commercial conversation. Understand their position | | Lead with | Value delivered (use the value-narrative-builder output) | | Prepare | Renewal pricing, objection responses (from pricing-conversation-framework), competitive readiness | | Avoid | Jumping to the commercial discussion before establishing value. Value first, then pricing |
| Element | Content | |---------|---------| | Objective | Build the relationship. Understand their priorities. Establish credibility | | Lead with | A brief introduction and a genuine question about their priorities | | Prepare | Research on their role and likely concerns (from stakeholder-research-prep) | | Avoid | Presenting. First meetings should be 70% listening, 30% responding |
Before every call, write one sentence: "This call is successful if [specific outcome]."
| Good Objectives | Bad 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.
The skill produces:
development
Structures the CSM's week based on their portfolio status, upcoming events, overdue items, and strategic priorities. Produces a time-blocked plan that balances reactive demands with proactive account management. Use when asked to plan a week, structure daily priorities, build a weekly schedule, allocate time across accounts, manage a busy week, or when a CSM feels overwhelmed and needs to determine where to focus. Also triggers for questions about time management, weekly planning, account prioritisation for the week, daily priority setting, or how to balance competing demands across a portfolio.
development
Constructs a compelling value narrative for a customer account by connecting product usage to business outcomes in the customer's language. Produces different versions for different audiences -- the champion, the CFO, the board. Use when asked to build a value story, articulate ROI, create a business case for the customer, prepare value evidence for a renewal or QBR, or when a CSM needs to translate usage metrics into business impact the customer will recognise. Also triggers for questions about value articulation, ROI storytelling, customer business case, value evidence, or how to prove the product is worth the investment.
data-ai
Takes raw usage data -- even a spreadsheet export or pasted metrics -- and identifies patterns, risks, and opportunities. Translates product analytics into account intelligence a CSM can act on. Use when asked to interpret usage data, analyse product metrics, make sense of a usage report, identify trends in customer behaviour, flag usage-based risks, or when a CSM has data but does not know what it means for the account. Also triggers for questions about usage analysis, product analytics interpretation, behavioural pattern detection, usage-based risk identification, or turning raw metrics into actionable insight.
development
Builds a structured 30-60-90 day plan for a CSM taking over a new book of accounts or joining a new team. Prioritises accounts by risk and value, identifies immediate relationship actions, and structures the ramp to full productivity. Use when asked to plan a book transition, create a new CSM onboarding plan, structure a territory takeover, build a 30-60-90 plan for a new role, or when a CSM is inheriting accounts and needs a systematic approach to getting up to speed. Also triggers for questions about account transitions, new book ramp-up, CSM onboarding to a portfolio, territory planning, or how to take over accounts from another CSM.