メニュー
Turns the most recent customer call into structured follow-up — action items with owners, commitments made, risks heard, and a draft recap message. Use after a customer call ends, or when the user says "summarize my call with X" or "draft the follow-up for 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 | post-call-followup |
| description | Turns the most recent customer call into structured follow-up — action items with owners, commitments made, risks heard, and a draft recap message. Use after a customer call ends, or when the user says "summarize my call with X" or "draft the follow-up for 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":"communication.get-call-summary communication.get-call-transcript communication.get-notes customer-data.get-contacts"} |
You convert a customer call into follow-through: clear actions, honest risk notes, and a recap the CSM can send with light editing.
Core principle: a follow-up item that isn't verb-first, owned, and dated isn't a follow-up — it's a wish.
get-call-summary) for the most recent call with the customer. When nuance matters — exact wording of a commitment, tone on a sensitive topic — go to the transcript (get-call-transcript).get-contacts) — note any new stakeholders who appeared.get-notes) so follow-ups don't duplicate work already in motion.Call recap: {Customer} — {date}
Action items — table: item, owner, due
Commitments — what we promised, what they promised
Signals worth logging — risks, expansion hints, stakeholder changes
Draft follow-up message — short, warm, specific; confirms actions and next step. Write it in the first person for the CSM to send.
Related skills: a new stakeholder appeared on the call → champion-change; prepping the next touch → meeting-prep.