{"id":71995,"plugin_id":"plugin_asdk_app_6ae1fbfde930819188d2ae80dcfc0bce","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-30T00:06:34.467Z","digest":"cfe5fcaba23f5bf133cf83c252ea66f054dbcb46ef22724470bd19e8352aaa0b","against":null,"payload":{"description":"Builds the Sales to CS handover doc for one deal or account. Covers stakeholders, why we won, open objections, commitments, and call history. Gives you the handover as markdown, ready to paste into a doc.","included_files":[{"relative_path":"references/handover-template.md","size_in_bytes":5538}],"name":"create-sales-to-cs-handover","skill_md_contents":"---\nname: create-sales-to-cs-handover\ndescription: \"Builds the Sales to CS handover doc for one deal or account. Covers stakeholders, why we won, open objections, commitments, and call history. Gives you the handover as markdown, ready to paste into a doc.\"\nlicense: MIT\nmetadata:\n  zime:skill-id: 0e82dc75-cffd-449c-b45f-ba8b00f94ea1\n  zime:tag: workflow\n  zime:roles: ae,cs\n  zime:visibility: global\n  zime:skill-version: \"1\"\n  zime:marketplace-version: 0.1.20\n---\n\n# Sales → CS Handover\n\nBefore anything else, call the Zime connector tool `skill_used` with skill_id `0e82dc75-cffd-449c-b45f-ba8b00f94ea1`, skill_version `1` and skill_slug `create-sales-to-cs-handover`. It records which skill ran for Zime usage analytics. If the Zime connector is not available, skip this step and continue.\n\nFills the handover document CS uses to accept an account. Two kinds of field\nlive in it, and the difference is the whole skill:\n\n1. **Fields Zime data can fill** — stakeholders, why we won, objections,\n   commitments, call history, current state.\n2. **Fields only the rep knows** — NDA links, drive folders, demo slots,\n   client sensitivities, what not to say.\n\nCategory 2 is left as an explicit `[SALES TO FILL]` prompt. Never guessed.\n\n## Why guessing is worse than blank here\n\nCS accepts or rejects a handover based on this document. An invented client\nsensitivity (\"don't mention pricing\") gets treated as real and changes how CS\ntalks to the customer. A blank field gets chased and filled. The template's own\nrule is that CS pushes the start date rather than accepting an incomplete\nhandover — so a plausible-looking fabrication defeats the control the document\nexists to provide.\n\n## How It Works\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                   SALES → CS HANDOVER                            │\n├─────────────────────────────────────────────────────────────────┤\n│  STEP 1 — RESOLVE                                                │\n│  ✓ list_deals (deal handover) or list_accounts (account)         │\n├─────────────────────────────────────────────────────────────────┤\n│  STEP 2 — GATHER                                                 │\n│  + ask_zime — why we won, objections, commitments          │\n│  + list_meetings — call history, cadence, last engagement        │\n├─────────────────────────────────────────────────────────────────┤\n│  STEP 3 — FILL, DON'T GUESS                                      │\n│  ✓ Zime-backed fields filled with evidence + dates               │\n│  ! Rep-only fields left as [SALES TO FILL]                       │\n│  ✓ Open gaps listed at the top so CS sees them first             │\n├─────────────────────────────────────────────────────────────────┤\n│  STEP 4 — DELIVER                                                │\n│  ✓ Hand back the filled handover as markdown, ready to paste     │\n├─────────────────────────────────────────────────────────────────┤\n│  LOCAL FALLBACK (no zime-mcp)                                    │\n│  ~ Narrower draft from provided transcripts or CRM export        │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n## Usage\n\n```\n@create-sales-to-cs-handover <deal or account name>\n```\n\nIn the ChatGPT desktop app you can also type `/create-sales-to-cs-handover`.\n\nBuild the handover for the deal or account the user named.\n\n## Routing\n\n- Deal strategy while still selling, or the account's CRM record alone →\n  `review-account`.\n- Just the open commitments → `actions-commitments`.\n- An account review deck for a QBR → `create-sales-asset`.\n\n## What I Need From You\n\nThe deal or account name. Also useful, and otherwise left blank:\n\n- Who's handing over, and to whom\n- Anything sensitive CS must not say or do\n- Links (drive folder, NDA, charter) if you have them\n\nAnything not supplied comes back as a `[SALES TO FILL]` prompt — that's the\ndesign, not a shortfall.\n\n## MCP mode (required when zime-mcp is connected)\n\n**Required tools:** `list_deals` / `list_accounts` (resolve), `ask_zime`\n(evidence), `list_meetings` (call history).\n\n### Step 1 — resolve\n\n```json\n{ \"query\": \"Acme\" }\n```\n\n`multiple_matches` → show candidates, ask, pin. A handover written about the\nwrong account is worse than none.\n\n### Step 2 — gather, asking for dates and names\n\nName the deal or account in the question itself, since `ask_zime` has no\nseparate deal/account scoping argument:\n\n```json\n{ \"question\": \"For the Acme deal: who are the stakeholders and what does each one care about, why did we win, what objections or blockers are still live, and what did we commit to delivering? Give the evidence, the speaker, and the date for each.\" }\n```\n\nCall history:\n\n```json\n{ \"query\": \"Acme\", \"start_date\": \"2026-02-01\", \"end_date\": \"2026-08-13\" }\n```\n\nAsk for speaker and date explicitly — a stakeholder motivation with no source\ncan't be validated by CS.\n\n### Outcomes\n\nUsual shapes — `resolved` / `multiple_matches` / `no_match`, or\n`{\"error\": \"<CODE>\", \"message\": \"<sentence>\"}` (show the user the message;\n`INTERNAL_ERROR` retry once; `TIMEOUT` narrow and retry; `CREDIT_LIMIT` stop\nand relay the message; `UNAUTHORIZED` / `FORBIDDEN` means reconnect or lack\nof access). A failed or empty evidence call means that section becomes a\n`[SALES TO FILL]` prompt — it does not become a guess.\n\n## Output\n\nFollow [references/handover-template.md](references/handover-template.md) for\nthe full field list. Structure:\n\n```markdown\n# Sales → CS Handover: [Account]\n_Drafted from Zime call and CRM data on [date]. Sections marked\n[SALES TO FILL] need the rep before CS can accept._\n\n## Open gaps — blocking acceptance\n- [ ] [field] — [SALES TO FILL]\n\n## 1. Deal and commercial status\n| Field | Value | Source |\n|---|---|---|\n| Deal | [name] · [stage] · [amount] | CRM |\n| Close date | [date] | CRM |\n| NDA / charter links | [SALES TO FILL] | — |\n\n## 2. Client context\n[what they do, team shape, tooling — evidence + date, or SALES TO FILL]\n\n## 3. Stakeholders\n| Name | Title | Role | What they care about | Source |\n|---|---|---|---|---|\n| [name] | [title] | [champion / DM / economic buyer] | [motivation] | [call, date] |\n\n## 4. Why we won\n- **[hook]** — [evidence] — [speaker, date]\n\n## 5. Objections and blockers still live\n| Objection | Raised by | Date | Status |\n|---|---|---|---|\n\n## 6. Commitments made\n| Commitment | Owner | Due | Source |\n|---|---|---|---|\n\n## 7. Call history\n| Date | Meeting | Type | Attendees |\n|---|---|---|---|\n\n**Last engagement:** [date] · **Cadence:** [observed pattern]\n\n## 8. Marching orders for CS\n[first actions, from what the calls indicate]\n\n## 9. What NOT to do — client sensitivities\n[SALES TO FILL] — not inferable from call data\n\n## 10. Open questions for CS to chase\n- [unresolved item] — [source]\n```\n\nPresent the finished handover as plain markdown: short sections with labelled\nlines, status written as words (at risk, needs attention, on track), any\ncommentary in the chat around it, and gaps kept visible as \"not stated\" or\n`[SALES TO FILL]`.\n\n## Deliver\n\nHand back the filled-in markdown above as the finished handover, ready for\nthe user to paste into Docs or another editor and share with CS. Say plainly\nthat the paste is a manual step, so the user knows it's needed.\n\n### Rules\n\n- **`[SALES TO FILL]` is mandatory** for: NDA and charter links, drive folder,\n  demo/kickoff slots, client sensitivities, what-not-to-say, post-POC\n  commercial terms. Never infer these — none are reliably in call data.\n- **Every Zime-filled row carries a source** (call + date). CS validates the\n  handover; unsourced claims can't be validated.\n- **Lead with Open gaps.** CS reads that first and knows immediately whether\n  this handover is acceptable.\n- **A stakeholder needs a real source.** No inferring a champion from who\n  talked most.\n- **Never invent an owner or a due date** on a commitment. \"not stated\" is\n  correct.\n- If the account has almost no call history, say so plainly at the top — a\n  thin handover honestly labelled is useful; a padded one is not.\n\n## Tips\n\n1. **Supply the links up front** — they're the most common blockers to\n   acceptance.\n2. **Sensitivities are yours to write** — the calls rarely contain them and\n   guessing them is the most dangerous fabrication in this document.\n3. **Widen the call-history window** — handovers want the whole relationship,\n   not the last 90 days.\n4. **Chase the gaps with `actions-commitments`** before handing over.\n\n## Local mode (only when no zime-mcp server is connected)\n\nIf the user provides transcripts or a CRM export, draft from those files only.\nOpen with one line saying the draft covers only the provided files, so\nstakeholder motivations and objections from other calls are missing by\nconstruction. Expand `[SALES TO FILL]` to cover everything the files don't\ncarry.\n\n## What this sends where\n\nMCP mode sends query words (to `list_deals`/`list_accounts`), the evidence\nquestion naming the deal or account (to `ask_zime`), and query words\nplus dates (to `list_meetings`). Local mode reads only the provided files.\nAt the start, the skill calls the Zime connector tool `skill_used`, which\nrecords the skill's id, version and name with your user and session in\nZime's usage log.\n\n## Related Skills\n\n- **actions-commitments** — close the gaps before handing over\n- **review-account** — the pre-handover view of the same deal\n- **create-sales-asset** — the account review deck CS will run later\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}