prep-call

name	prep-call
description	Build a one-page cheatsheet for the next call with a client from what the client folder already holds. Who they are, where things stand, the open threads, two to four goals for the call, the questions to ask, what to say when they push on price, timing or scope, and the one next step to propose, in the client's language and register (Hebrew by default). Use right before a scheduled call, once clients/NAME/ exists, whether it is the first call or the fifth. NOT for drafting the recap and scope after a call (post-call), for a status board when no call is ahead (client-context), or for writing an outcome into the state log (sync-call-state). Reads local files, an optional CRM export and Wispr Flow meeting titles; writes one new file and never overwrites. Model-invocable, so fire it yourself when the goal matches; do not fire it speculatively or as a checkpoint.
tags	["client","prep-call","cheatsheet","register","wispr-flow","hebrew"]
version	1.2.1
author	yonyon-ai
user-invocable	true
complexity	low
argument-hint	<client-name> [--for YYYY-MM-DD] [--lang he|en]
disable-model-invocation	false
allowed-tools	Read, Write, Glob, Grep, AskUserQuestion
license	MIT
compatibility	Full file workflow on coding agents with a working directory: Claude Code (verified), Cursor, GitHub Copilot, Windsurf, OpenCode, Codex, Gemini CLI, Antigravity, OpenClaw, Grok Build. Chat mode (Step 0) on hosts without file access: Claude.ai, Claude Desktop, ChatGPT, Grok, Manus, Gemini Spark; paste the inputs, read the outputs, save them yourself, nothing is written. Wispr Flow MCP optional.
supported_agents	["claude-code","cursor","github-copilot","windsurf","opencode","codex","gemini-cli","antigravity","openclaw","grok-build","claude-desktop","claude-ai","chatgpt","manus","gemini-spark","grok"]
metadata	{"display_name":{"he":"הכנה לשיחה","en":"Pre-call cheatsheet"},"display_description":{"he":"דף הכנה של עמוד אחד לשיחה הבאה עם לקוח: מי, איפה עומדים, מה פתוח, מה לשאול ומה להציע. כל שורה מצביעה על המקור שלה.","en":"A one-page cheatsheet for the next client call: who, where things stand, what is open, what to ask and what to offer. Every line points at its source."},"tags":{"he":["לקוחות","הכנה לשיחה","צ'יטשיט","מכירות","עברית"],"en":["clients","prep-call","cheatsheet","sales","hebrew"]},"supported_agents":["claude-code","cursor","github-copilot","windsurf","opencode","codex","gemini-cli","antigravity","openclaw","grok-build","claude-desktop","claude-ai","chatgpt","manus","gemini-spark","grok"]}

prep-call

The last thing you read before you dial. One client folder in, one cheatsheet out: seven short sections that say who you are talking to, where things stand, what is still open, what this call must achieve, what to ask, what to say under pressure, and the single next step to propose. Every goal and every question points at the file it came from; when the folder holds no history, the sheet says which sections are defaults.

Sibling split: post-call runs after the call, client-context shows the board when no call is ahead, sync-call-state writes the outcome into state.md after you approve it. This skill only reads the folder and writes clients/<client-name>/cheatsheet-<date>-<HHMM>.md.

When to use

• A call with a known client is minutes or hours away and you want the plan on one page.
• You want the open threads from the last call turned into goals and questions, not a summary of what already happened.
• It is a first call and you want the defaults spelled out instead of an empty page.

When NOT to use

• After the call, to draft the recap and the scope: post-call.
• To see the stage, the open threads and the last contact with no call ahead: client-context.
• To change the stage line or append to state.md: sync-call-state.
• For a client with no folder yet: create the folder first (Step 1 prints the command).

Workflow

Step 0: chat mode (hosts without file access)

On a host that cannot read or write files (Claude.ai, ChatGPT, Grok, Manus, Gemini Spark, or Claude Desktop without a filesystem MCP), run in chat mode: ask the user to paste whatever they have (profile, the latest state entry, the last post-call CallFacts, recent outreach) plus the client's name and language. Run Step 2 on the pasted material, list the sources that were absent, and print the cheatsheet in chat instead of writing it (Step 3 write is skipped). Nothing is written.

Step 1: gather the sources

Read, in this order, skipping what is absent: clients/<client-name>/profile.md (a missing folder is an error: print cp -r fixtures/clients/_template clients/<client-name> and stop); the newest entry in state.md; the CallFacts block of the newest post-call-*.md; the newest outreach-*.md; the newest call-*.txt for address forms only, never for facts; the client's row in or when the file exists (read-only). When, and only when, the MCP server is connected, call with one term at a time (contact first name, then company), never or , and keep only the title and date of the newest match; never call , never cache. Output: the list of sources found, each with its path or , and the list of sources absent.