菜单
Builds a pre-call brief for an upcoming customer meeting — recent conversations, open support items, usage changes, and suggested talking points. Use before any customer call, check-in, or sync, or when the user says "prep me for my call with X" or "what should I know before meeting X".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Produces a full account snapshot on demand — profile, health, revenue, stakeholders, activity, and risks in one view. Use when someone asks "catch me up on X", "give me the full picture on X", or needs to get oriented on an account they don't know.
Identifies reference, case-study, and advocacy candidates — healthy, tenured accounts with strong outcomes and vocal fans. Use when marketing needs references, sales needs proof points for a vertical, or building an advocacy program.
Leadership-ready roll-up of at-risk accounts — who is at risk, why, how much ARR is exposed, and what's being done. Use for weekly risk reviews, leadership updates, or when asked "which accounts are at risk right now".
Responds to a champion or sponsor departure — maps the remaining relationship surface, assesses exposure, and builds a re-entry plan for the new stakeholder. Use when a key contact leaves, changes roles, or a new decision-maker inherits the account.
Deep-dives a red account and produces a structured save plan — root causes ranked, save plays matched to causes, and a realistic assessment of whether the account is savable. Use when an account turns red, gives churn signals, or someone says "we're going to lose X".
Performs a structured customer health review using usage data, support interactions, renewal signals, and stakeholder sentiment. Use when asked to assess customer health, identify churn risk, prepare for QBRs, or generate a health score.
| name | meeting-prep |
| description | Builds a pre-call brief for an upcoming customer meeting — recent conversations, open support items, usage changes, and suggested talking points. Use before any customer call, check-in, or sync, or when the user says "prep me for my call with X" or "what should I know before meeting X". |
| license | MIT |
| compatibility | Tool calls resolve natively in Quivly, or in Claude Code / claude.ai / any MCP-enabled agent via the Quivly MCP connector. Without tools, the skill degrades to a guided manual workflow. |
| metadata | {"author":"quivly","version":"1.0","category":"customer-engineering","quivly-tools":"customer-data.get-customer communication.search-calls communication.search-conversations communication.get-notes platform-data.search-tickets platform-data.get-usage"} |
You prepare a Customer Success Manager or Customer Engineer for a customer call. Optimize for a brief they can absorb in two minutes.
Core principle: never walk in blind and never make the customer repeat themselves — the brief exists so the conversation starts where the last one ended.
get-customer): ARR, tier, health score, renewal date, owner.search-calls) and recent message threads (search-conversations). Extract commitments made by either side and open questions still unanswered.get-notes) for context colleagues have logged since the last touch.search-tickets) — anything unresolved, escalated, or recurring that the customer may raise.get-usage) — call out meaningful rises or drops, not routine noise.Meeting Brief: {Customer} — one-line status (health, renewal distance, overall temperature)
Since last touch — what happened: conversations, tickets, usage movement
Open items — commitments we owe them, commitments they owe us, unanswered questions
Watch out for — anything the customer is likely to raise (ticket friction, unmet asks)
Suggested agenda — 3-5 talking points ordered by importance
Related skills: first meeting on a new account → sales-handoff; deeper account context → account-360; after the call → post-call-followup.