菜单
Generate a discovery or demo call script tailored to the prospect's role and known pains — opener, discovery questions, demo path, objection handling, close. Use on "prep a script for my demo", "discovery call with <role>", or "script for the call tomorrow".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate a targeted lead list with Apollo — filter by title, company size, industry, tech stack — and export to CSV/HubSpot/Sheets. Use when the user says "build me a prospect list", "find 100 VPs of X", or "source leads for the campaign".
Build a competitive battlecard — when to land-grab vs. when to walk away, key wedges, objection handling, landmines to set. Use on "build a battlecard against <competitor>", "how do we beat <X>", or "compete review".
Check Google Calendar availability and book meetings — find slots across time zones, send invites, hold prep time. Use on "find time with X", "book a demo", "check my availability next week".
Write high-response cold emails — short, specific, prospect-centric. Use when the user asks to "write a cold email", "rewrite my outbound", or "this email is getting no replies". Produces 3 variants with rationale.
Run a cold email outreach campaign via Gmail. Use when the user wants to send personalized cold emails to a list of prospects, draft outbound sequences, or launch a small outreach batch from a CSV/sheet of leads. Proactively invoke when the user mentions "send cold emails", "outreach campaign", or "blast my leads".
Prep for a discovery call — research the account, the attendee, set hypothesis for their pains, write the question stack, define success. Use on "prep for my discovery call", "research this account before tomorrow", or "what should I ask <prospect>?".
| name | sales-call-script |
| description | Generate a discovery or demo call script tailored to the prospect's role and known pains — opener, discovery questions, demo path, objection handling, close. Use on "prep a script for my demo", "discovery call with <role>", or "script for the call tomorrow". |
| allowed-tools | ["Read","Write","AskUserQuestion"] |
Build a call script that guides — not a monologue that reads.
./scripts/<account>-<date>.md.0:00–2:00 Rapport + agenda set
"Great to meet you. I've set aside 30 — does that still work?
Agenda: 10 min on what you're trying to solve, 15 on whether we'd fit,
5 on next step. Anything you want to add?"
2:00–15:00 Discovery (80% listening)
- "Walk me through how <current process> works today."
- "What changed recently that put this on your plate?" ← trigger
- "What happens if you don't solve it this quarter?" ← stakes
- "Who else is affected?" ← buying committee
- "If this worked perfectly, what would be different in 6 months?"
15:00–22:00 Targeted show-and-tell (not a full demo — 1-2 workflows mapped to their pain)
22:00–27:00 Objection handling + pricing-teaser if they ask
Common objections:
- "We could build this" → <response>
- "We're using <competitor>" → <response>
- "Timing's not great" → <response>
27:00–30:00 Next step
"Based on what you shared, I think the right next step is <X>.
Should we put it on the calendar while we're here?"
For each: restate → acknowledge → reframe → evidence → check-in.