메뉴
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".
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".
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>?".
Send follow-up emails on threads that haven't replied — 3, 7, 14 day cadence with fresh angles. Reads sent folder, identifies no-reply threads, drafts context-aware follow-ups. Trigger on "send follow-ups", "bump my cold emails", or "who hasn't replied?".
| name | battlecard-creator |
| description | 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". |
| allowed-tools | ["Read","Write","WebSearch","AskUserQuestion"] |
A battlecard is a rep's survival kit in a competitive deal, not a marketing brochure.
./battlecards/<competitor>.md.# vs. <Competitor> (last updated <date>)
## One-line positioning
We win when <specific scenario>. They win when <specific scenario>.
## Fight or flight (lead with this)
**Fight** when the prospect has: <3 qualifiers that favor us>.
**Flight** when: <2-3 deal-killer conditions> — redirect to partner / walk.
## Our wedge (3 max — not 10)
1. <Wedge>: <evidence/metric> · Prospect question to surface: "<q>"
2. …
3. …
## Their strengths (name them honestly)
- <Strength> — why this matters to <persona>
- <Strength>
## Landmines to set (questions a prospect should ask them)
1. "Can you show me <specific capability> without custom code?"
2. "What does <edge-case workflow> look like in your product?"
3. "Can I see a customer at my scale in production?"
## Objection handling
- **"<Competitor> has <feature> and you don't"**
Acknowledge → reframe to what matters → evidence. Verbatim example.
- **"<Competitor> is cheaper"**
…
- **"We're already evaluating them"**
…
## Trap the reference
If they're going to <competitor>'s reference call, tell the champion to ask:
- "<specific uncomfortable question>"
- "<another>"
## Proof we win
- <Customer X> switched from <competitor> — outcome: <metric>
- <Customer Y> evaluated both — quote: "<verbatim>"