Build competitive battle cards with side-by-side feature comparisons, pricing intel, win/loss patterns, objection responses, and sales talk tracks. Use this skill whenever the user mentions battle cards, competitive positioning, "how do we compare to X", competitor analysis for sales, win themes, competitive differentiation, or needs ammunition against a specific competitor. Also trigger when a rep asks "what do I say when a prospect brings up [competitor]".
Generates competitive battle cards with feature comparisons, pricing intel, and objection responses for sales teams.
/plugin marketplace add https://www.claudepluginhub.com/api/plugins/jbalbu01-sales-enablement-2/marketplace.json/plugin install jbalbu01-sales-enablement-2@cpd-jbalbu01-sales-enablement-2This skill inherits all available tools. When active, it can use any tool Claude has access to.
Create actionable competitive battle cards that reps can use in live conversations. Battle cards aren't marketing collateral — they're quick-reference weapons for the field. Every section should answer: "What do I say to the prospect right now?"
┌─────────────────────────────────────────────────────────────────┐
│ BATTLE CARDS │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone via web search + your input) │
│ ✓ Competitor overview and positioning │
│ ✓ Feature-by-feature comparison matrix │
│ ✓ Pricing intelligence (public data + your input) │
│ ✓ Strengths, weaknesses, and landmines │
│ ✓ Talk tracks for common competitive scenarios │
│ ✓ Objection responses specific to competitor │
│ ✓ Customer-facing "Why Us" narratives │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Win/loss data against this competitor │
│ + ~~CRM: Deal patterns — where you win vs lose │
│ + ~~data enrichment (ZoomInfo): Competitor tech stack, headcount │
│ + ~~data enrichment (Clay): Company enrichment, firmographics │
│ + ~~data enrichment (LinkedIn): Competitor org and hiring trends │
│ + ~~chat: Internal competitive intel from team channels │
│ + ~~knowledge base: Existing battle cards and collateral │
└─────────────────────────────────────────────────────────────────┘
Tell me who you're competing against:
I'll research them immediately and combine that with what you tell me about your own product.
The more context you give me, the sharper the battle card. At minimum I need:
Helpful extras:
CRITICAL: Before asking the user for competitive context, check what MCP tools are available and pull data automatically. The best battle cards combine hard data with field observations.
Check if you have access to CRM tools (look for tools containing search_crm_objects, get_crm_objects, or similar).
If CRM tools ARE available:
Pull closed-lost deals against this competitor. Search the deals object type for recently lost deals.
dealstage = "Closed Lost" stages, closedate in the last 180 daysdealname, amount, dealstage, closedate, pipeline, hubspot_owner_id, dealtype, hs_closed_lost_reason, description, notes_last_updatedPull closed-won deals against this competitor. Same search but for "Closed Won" to find where you WIN against them.
Calculate competitive win rate. From the won and lost data:
Map rep names. Use search_owners to translate hubspot_owner_id to actual names for the win story section.
Check if you have access to sales intelligence tools (look for tools prefixed with zoominfo_, clay_, linkedin_).
ZoomInfo (if available):
zoominfo_search_company with the competitor name/domain.
zoominfo_get_tech_stack with competitor domain.
zoominfo_search_contact to find their sales team size, engineering headcount, leadership changes.
Clay (if available):
clay_enrich_company with competitor domain.
LinkedIn (if available):
linkedin_search_companies with competitor name.
linkedin_search_leads with company_name + senior titles.
Check if you have access to Gong tools (look for tools prefixed with gong_).
If Gong tools ARE available:
gong_search_calls to find recent calls where this competitor was discussed.gong_get_call_details on relevant calls to find:
Check if you have access to chat tools (slack_search_public, slack_search_public_and_private, chat_message_search).
If chat tools ARE available:
After pulling data, present a summary:
"I found [N] competitive deals in your CRM against [Competitor] — [X] wins and [Y] losses for a [Z]% win rate. Per ZoomInfo, they have [N] employees and $[X] in revenue. I also found [N] call recordings where [Competitor] was discussed and [N] Slack messages with competitive intel. Building the battle card now..."
Supplement the tool-sourced data with public web research:
Run web searches:
1. "[Competitor] product features" → Core capabilities
2. "[Competitor] pricing plans" → Public pricing
3. "[Competitor] vs [alternatives]" → Market positioning
4. "[Competitor] reviews G2 Capterra" → Customer sentiment
5. "[Competitor] news 2025 2026" → Recent launches, funding, changes
6. "[Competitor] limitations complaints" → Known weaknesses
After the auto-pull, ask ONLY for information you couldn't find in tools. If you pulled CRM data, you already know win/loss patterns. If you got ZoomInfo data, you already have company details. Focus questions on:
Using ALL evidence — CRM win/loss data, ZoomInfo intel, Gong call insights, Slack intel, web research, and user input:
After generating the battle card:
memory/competitors.md with new intel gathered during researchmemory/content-registry.md with today's date and dependenciesmemory/deal-patterns.md with competitive win/loss patterns from CRM dataBuild the card using the template below, keeping everything concise and action-oriented. Every section should be scannable in under 30 seconds — reps use these mid-conversation.
# Battle Card: [Your Product] vs [Competitor]
**Last Updated:** [Date]
**Confidence Level:** [High/Medium/Low — based on data quality]
---
## At a Glance
| | [Your Product] | [Competitor] |
|---|---|---|
| **Best For** | [Ideal use case] | [Their ideal use case] |
| **Pricing** | [Range/model] | [Range/model] |
| **Key Strength** | [Your #1 differentiator] | [Their #1 strength] |
| **Key Weakness** | [Your gap — be honest] | [Their biggest vulnerability] |
---
## Quick Win Themes
When you're competing against [Competitor], lead with these 3 themes:
1. **[Theme 1]** — [One sentence on why this matters to the prospect]
2. **[Theme 2]** — [One sentence]
3. **[Theme 3]** — [One sentence]
---
## Feature Comparison
| Capability | [Your Product] | [Competitor] | Verdict |
|------------|---------------|--------------|---------|
| [Feature 1] | [Your capability] | [Their capability] | [Who wins and why] |
| [Feature 2] | ... | ... | ... |
| [Feature 3] | ... | ... | ... |
| [Feature 4] | ... | ... | ... |
| [Feature 5] | ... | ... | ... |
---
## Pricing Intelligence
**Their Model:** [How they price — per seat, usage, tier]
**Your Model:** [How you price]
**Where We Win on Price:** [Scenarios where you're cheaper/better value]
**Where They Win on Price:** [Be honest — and how to handle it]
**Talk Track:**
> "[Scripted response when prospect says 'they're cheaper']"
---
## Landmine Questions
Questions to ask prospects that expose [Competitor]'s weaknesses:
1. "Have you looked into how [Competitor] handles [weakness area]?"
2. "What's your plan for [use case they can't support]?"
3. "How important is [capability they lack] for your team?"
These questions plant doubt without directly attacking the competitor.
---
## Objection Responses
### "We're already using [Competitor]"
> [Talk track — acknowledge, differentiate, propose evaluation]
### "[Competitor] is cheaper"
> [Talk track — reframe value, TCO argument, hidden costs]
### "[Competitor] has [feature we lack]"
> [Talk track — honest response, alternative approach, roadmap if relevant]
### "Our team already knows [Competitor]"
> [Talk track — switching costs vs. long-term value]
---
## Their Weaknesses (With Evidence)
- **[Weakness 1]:** [Evidence from reviews, customer feedback, or research]
- **[Weakness 2]:** [Evidence]
- **[Weakness 3]:** [Evidence]
---
## Our Vulnerabilities (Be Honest)
- **[Gap 1]:** [How to handle when it comes up]
- **[Gap 2]:** [Mitigation strategy]
Honesty here protects reps from being blindsided. It's better to have a prepared response than to be caught off guard.
---
## Recent Intel
- [Date]: [Recent news, product launch, pricing change, leadership change]
- [Date]: [Any relevant update]
---
## Win Story
**Customer:** [Name if shareable]
**Situation:** [They were evaluating us and [Competitor]]
**Why They Chose Us:** [The deciding factor]
**Quote:** "[Customer quote if available]"
---
## Sources
- [Source 1](URL)
- [Source 2](URL)
After generating the battle card, I'll ask how you want it:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.