К основному содержанию
скилл CX Codex

battle-card-builder · travisjneuman — скилл для Claude Code

Скилл battle-card-builder генерирует батл-карты и сценарии отработки возражений для отдела продаж по чёткой восьмичастной структуре.

MIT 137 установок ★ 114 обновлён 2026-10-25

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add travisjneuman/.claude --skill battle-card-builder -a claude-code
Открыть на GitHub

Что делает battle-card-builder

Скилл задаёт шаблоны конкурентного анализа: от карточки соперника с оценкой угрозы до таблицы сравнения функций, тарифов и целевой аудитории. Он раскладывает аргументы на сильные стороны обеих сторон, формирует темы для победы в сделках и контрольные вопросы, выявляющие слабые места конкурента.

Внутри описан четырёхшаговый алгоритм ответов на возражения (Acknowledge, Bridge, Respond, Evidence), матрица позиционирования по осям охвата и возможностей, а также график сбора данных. Без собственных вводных данных о продукте и тарифах конкурента скилл выдаст лишь общую канву.

Какие задачи решает

  • составить структурированную батл-карту по конкретному конкуренту
  • подготовить аргументы для отработки возражений по цене и функционалу
  • сформулировать наводящие вопросы для выявления слабых мест соперника
  • разметить матрицу позиционирования продукта на рынке

Примеры запросов агенту

  • Собери батл-карту против нашего главного конкурента на рынке CRM
  • Распиши ответы на возражения клиентов по схеме Acknowledge-Bridge-Respond-Evidence
  • Подготовь список вопросов для демо, которые подсвечивают наши преимущества перед соперником

Как установить battle-card-builder

1Через Skills CLI (Vercel)

npx skills add travisjneuman/.claude --skill battle-card-builder -a claude-code

2Вручную: положить файлы

~/.claude/skills/battle-card-builder/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/battle-card-builder/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о battle-card-builder

Как установить battle-card-builder в Claude Code?

Запустите команду npx skills add travisjneuman/.claude --skill battle-card-builder -a claude-code. Также можно вручную поместить файл по пути ~/.claude/skills/battle-card-builder/SKILL.md.

Что делает battle-card-builder?

Скилл даёт агенту инструкции по созданию конкурентных документов: карточек соперников, таблиц сравнения цен и возможностей, формулировок для парирования возражений и вопросов для квалификации лидов.

Какие разделы входят в стандартную батл-карту скилла?

Шаблон включает 8 блоков: профиль соперника, таблицу сравнения, наши преимущества, сильные стороны соперника, отработку возражений, ключевые темы победы, проверочные вопросы и свежие новости.

Исходный текст

SKILL.md · MIT
---
name: battle-card-builder
description: Competitive battle card creation for sales teams combining competitive intelligence, sales enablement, and document formatting. Use when building battle cards, competitive analysis decks, or win/loss analysis materials.
---

# Battle Card Builder

Structured frameworks for creating competitive battle cards that help sales teams win against specific competitors.

## Battle Card Structure

### Standard Battle Card Sections

```
BATTLE CARD LAYOUT:

1. COMPETITOR SNAPSHOT (top of page)
   - Company name, logo, tagline
   - Founded, HQ, headcount, funding/revenue
   - Target market and primary use case
   - Threat level: HIGH / MEDIUM / LOW

2. QUICK COMPARISON TABLE
   - Feature-by-feature comparison
   - Pricing comparison
   - Target customer comparison

3. OUR STRENGTHS (vs. this competitor)
   - 3-5 key advantages with proof points
   - Customer quotes that validate each strength

4. THEIR STRENGTHS (honest assessment)
   - 2-3 areas where competitor excels
   - How to acknowledge without conceding

5. OBJECTION HANDLING
   - Top 5-7 objections prospects raise
   - Recommended responses for each

6. WIN THEMES
   - 3-4 messaging themes that resonate
   - Discovery questions to surface our advantages

7. LANDMINES
   - Questions to plant that expose competitor weaknesses
   - Features to demo that highlight differentiation

8. RECENT INTEL
   - Latest product releases or changes
   - Pricing changes
   - Key wins/losses
   - Last updated date
```

## Competitive Intelligence Gathering

### Intelligence Sources

| Source | Data Type | Refresh Frequency | Reliability |
| --- | --- | --- | --- |
| **Competitor website** | Pricing, features, messaging | Monthly | High |
| **G2/Capterra reviews** | User sentiment, complaints | Monthly | Medium-High |
| **Job postings** | Strategic direction, tech stack | Quarterly | Medium |
| **SEC filings / investor decks** | Revenue, strategy, risks | Quarterly | High |
| **Patent filings** | Future product direction | Quarterly | Medium |
| **Win/loss interviews** | Real buyer reasoning | Ongoing | High |
| **Sales call recordings** | Objections, competitor mentions | Ongoing | High |
| **Industry analyst reports** | Market positioning | Annually | High |
| **Social media / forums** | Product issues, sentiment | Weekly | Low-Medium |
| **Conference presentations** | Roadmap, vision | As available | Medium |

### Intelligence Collection Framework

```
COLLECTION CADENCE:

WEEKLY:
- Social listening for competitor mentions
- Review new G2/Capterra reviews
- Check competitor blog/news for announcements

MONTHLY:
- Full website and pricing page review
- Feature comparison audit
- Gong/Chorus analysis of competitor mentions in calls
- Win/loss interview synthesis

QUARTERLY:
- Deep competitive analysis refresh
- Battle card full update
- Sales team feedback collection
- Market positioning reassessment

ANNUALLY:
- Comprehensive competitive landscape review
- Strategic differentiation audit
- Battle card rebuild from scratch
```

## Positioning Frameworks

### Competitive Positioning Matrix

```
POSITIONING MAP:

                    HIGH CAPABILITY
                         |
                         |
     NICHE LEADER        |        MARKET LEADER
     (deep in segment)   |        (broad + deep)
                         |
   ─────────────────────+──────────────────────
     LOW REACH           |        HIGH REACH
                         |
     EMERGING PLAYER     |        BROAD PLAYER
     (limited scope)     |        (wide but shallow)
                         |
                    LOW CAPABILITY

POSITION US: [where we sit]
POSITION COMPETITOR: [where they sit]
NARRATIVE: "While [Competitor] covers more ground, we go deeper
            in [our segment] where it matters most for [buyer]."
```

### Differentiation Categories

| Category | Our Position | Competitor Position | Talking Point |
| --- | --- | --- | --- |
| **Product** | [specific feature/capability] | [their approach] | [why ours matters] |
| **Technology** | [architecture/approach] | [their architecture] | [technical advantage] |
| **Service** | [support model] | [their support model] | [customer impact] |
| **Price** | [pricing model] | [their pricing model] | [value story] |
| **Market Focus** | [our ICP] | [their ICP] | [specialization benefit] |
| **Integration** | [ecosystem fit] | [their ecosystem] | [workflow advantage] |
| **Security** | [certifications/approach] | [their posture] | [trust factor] |

## Objection Handling Templates

### Objection Response Framework

```
STRUCTURE FOR EVERY OBJECTION:

ACKNOWLEDGE: Validate the concern without agreeing
BRIDGE:      Transition to your perspective
RESPOND:     Address with evidence and specifics
EVIDENCE:    Proof point (customer, data, demo)

EXAMPLE:

OBJECTION: "[Competitor] has more integrations than you."

ACKNOWLEDGE: "Integration breadth is important — I understand
              why that's a factor in your evaluation."

BRIDGE: "What we've found with customers in your space is that
         it's less about the total number and more about depth
         of the integrations you actually use."

RESPOND: "We have 40+ integrations focused on [their stack],
          with bi-directional sync and real-time data flow.
          [Competitor]'s integrations are often one-directional
          or require manual configuration."

EVIDENCE: "[Customer X] evaluated both and chose us specifically
           because our [specific integration] saved their team
           12 hours per week vs. the manual workaround with
           [Competitor]'s connector."
```

### Common Objection Categories

```
PRICING OBJECTIONS:
- "They're cheaper"
- "We can't justify the premium"
- "Their free tier is sufficient"

FEATURE OBJECTIONS:
- "They have [feature] that you don't"
- "Their product does more"
- "We need [specific capability]"

MARKET OBJECTIONS:
- "They're the market leader"
- "Everyone in our industry uses them"
- "They have more customers like us"

RISK OBJECTIONS:
- "They're a bigger, safer company"
- "What if you get acquired?"
- "We're already using them and switching is risky"

RELATIONSHIP OBJECTIONS:
- "We already have a contract with them"
- "Our team is trained on their platform"
- "Our exec has a personal relationship there"
```

## Win Theme Templates

### Discovery Questions That Favor Us

```
QUESTION DESIGN PRINCIPLE:
Ask questions whose honest answers reveal competitor weaknesses
without mentioning the competitor by name.

FORMAT:
Question → Expected Answer → Bridge to Our Strength

EXAMPLES:

Q: "How important is [our strength area] to your workflow?"
A: [Prospect describes importance]
B: "That's exactly where we've invested most deeply..."

Q: "What's your experience been with [pain our product solves]?"
A: [Prospect describes pain]
B: "We hear that a lot from teams who've used [category]. Here's
    how we approach it differently..."

Q: "When you evaluated solutions before, what fell short?"
A: [Prospect describes gaps]
B: "Those are the exact gaps we were built to fill..."
```

### Landmine Questions

```
LANDMINE STRATEGY:
Plant questions the prospect will ask the competitor that
expose their weaknesses.

TEMPLATE:
"When you're evaluating [Competitor], you might want to ask
them about [specific weakness area]. Specifically:

1. [Question about their known limitation]
2. [Question about their pricing gotcha]
3. [Question about their support gap]

These are areas where we've seen prospects get surprised during
implementation, and it's worth clarifying upfront."

RULES:
- Never lie or exaggerate competitor weaknesses
- Base landmines on documented, verified issues
- Keep it professional — attack the product, not the people
- Be prepared for the competitor to do the same to you
```

## Pricing Comparison Framework

### Pricing Analysis Template

```
PRICING COMPARISON:

                    US              COMPETITOR
──────────────────────────────────────────────────
Model:              [per seat]      [per usage]
Entry Price:        $___/mo         $___/mo
Mid-Market:         $___/mo         $___/mo
Enterprise:         $___/mo         $___/mo

HIDDEN COSTS:
- Implementation:   [included]      [$X extra]
- Support:          [included]      [paid tier]
- Integrations:     [included]      [add-on]
- Storage/Usage:    [included]      [overage fees]

TRUE TCO (3-year, 100 users):
Us:         $______
Competitor: $______
Savings:    $______ (__%)

WIN NARRATIVE:
"While their list price appears [lower/similar], when you factor
in [hidden cost 1] and [hidden cost 2], the total cost of
ownership over 3 years is actually [X%] higher."
```

## Battle Card Maintenance

### Update Cadence

| Component | Update Frequency | Owner |
| --- | --- | --- |
| Competitor snapshot | Quarterly | Competitive Intel |
| Feature comparison | Monthly | Product Marketing |
| Pricing comparison | Quarterly (or on change) | Pricing Team |
| Objection handling | Monthly (from win/loss) | Sales Enablement |
| Win themes | Quarterly | Product Marketing |
| Customer proof points | Monthly | Customer Marketing |
| Recent intel | Weekly | Competitive Intel |

### Staleness Indicators

```
BATTLE CARD IS STALE WHEN:

RED FLAGS:
- Last updated > 90 days ago
- Competitor released major product update since last refresh
- Win rate against competitor dropped > 5% QoQ
- Sales reps report card is "not useful"
- Pricing information is outdated

HEALTH CHECK QUESTIONS:
- When was this last updated? [date]
- Has competitor launched anything since? [Y/N]
- Have we validated with recent win/loss data? [Y/N]
- Do sales reps actively use this card? [Y/N]
- Is our proof point data current? [Y/N]
```

### Win/Loss Integration

```
WIN/LOSS DATA COLLECTION:

AFTER EVERY COMPETITIVE DEAL:
1. Record outcome (win/loss)
2. Document primary reasons (top 3)
3. Note competitor strengths that resonated
4. Note our strengths that resonated
5. Capture any new objections heard
6. Flag any pricing intelligence

QUARTERLY ANALYSIS:
- Win rate by competitor (trending)
- Top reasons for wins (reinforce in card)
- Top reasons for losses (address in card)
- New objections to add
- Proof points to update
```

## Battle Card Quality Checklist

| Check | Status |
| --- | --- |
| Competitor info verified within last 30 days | [ ] |
| Pricing data confirmed (not assumed) | [ ] |
| At least 3 customer proof points per strength | [ ] |
| Objection responses tested with top reps | [ ] |
| Win themes validated by recent win/loss data | [ ] |
| Honest about competitor strengths (credibility) | [ ] |
| No unverified claims or speculation | [ ] |
| Formatting is scannable (not wall of text) | [ ] |
| Card fits on 2 pages (front and back) | [ ] |
| Last updated date is visible | [ ] |

## See Also

- [Sales](../sales/SKILL.md)
- [Marketing](../marketing/SKILL.md)
- `anthropic-skills:docx` (Anthropic document skill)
- [Product Management](../product-management/SKILL.md)

© travisjneuman · MIT · travisjneuman/.claude

Похожие скиллы

Все скиллы по теме «Маркетинг и контент» →

Сначала — battle-card-builder от других авторов.

battle-card-builder deanpeters Скилл battle-card-builder собирает карту конкурентной борьбы из публичных данных: цены, отзывы, релизы. Каждое утверждение получает метку и ссылку на источник. CX Codex +1 1 300установок competitive-strategist ncklrs Скилл competitive-strategist помогает исследовать конкурентов, разбирать причины побед и проигрышей, создавать battlecards и формулировать позиционирование для B2B/SaaS. CX Codex +1 163установок competitor-analysis manojbajaj95 Скилл competitor-analysis для конкурентного анализа и создания сравнительных страниц. Собирает данные по конкурентам, формирует SWOT, матрицы функций, карточки для отдела продаж. CX Codex +1 284установок build-battlecard-suite gtmagents Команда build-battlecard-suite генерирует баттлкарты, разборы возражений и скрипты разговоров по конкурентам под разные отделы и форматы. Структурирует конкурентную разведку. CX Codex +1 ★ 450звёзд репо sales-enablement coreyhaines31 Скилл sales-enablement для Claude Code помогает готовить материалы для B2B-продаж. Создаёт презентации, памятки, сценарии демо и ответы на возражения. CX Codex +1 130 800установок competitive-analysis OrchestKit Скилл competitive-analysis формирует анализ рынка по пяти силам Портера, SWOT-матрицы, профили конкурентов и карты позиционирования. Включается при оценке ниши или подготовке сейлз-батлкард. CX Codex +1 125установок case-studies gtmagents Скилл case-studies для Claude Code, который собирает клиентские истории по фреймворку CHIC: Challenge → Hypothesis → Implementation → Change. CX Codex +1 ★ 450звёзд репо

Из того же набора117

Весь набор →
payment-integration Скилл payment-integration помогает подключать Stripe и RevenueCat, строить подписки и обрабатывать вебхуки. Нужен при интеграции платежей и проверке PCI-границ. CX Codex +1 139установок generic-static-feature-developer Скилл generic-static-feature-developer помогает добавлять функции в статические сайты на чистом HTML, CSS и JS: паттерны, автодеплой и проверки перед коммитом. CX Codex +1 139установок customer-success Скилл customer-success помогает проектировать базы знаний, настраивать интеграции с тикет-системами и собирать метрики клиентской поддержки вроде CSAT и NPS. CX Codex +1 138установок test-specialist Скилл test-specialist для Claude Code задаёт шаблоны модульных, интеграционных и сквозных тестов на JS/TS, Python, Go и Rust. Агент подключает правила только по прямому запросу на написание тестов или замер покрытия. CX Codex +1 138установок serverless-development Скилл serverless-development для Claude Code разбирает бессерверные функции AWS Lambda, Vercel Edge и Cloudflare Workers. API и вебхуки масштабируются сами. CX Codex +1 133установок growth-engineering Скилл growth-engineering для Claude Code содержит шаблоны A/B-тестирования, фича-флагов, воронок активации и виральных циклов. CX Codex +1 133установок email-systems Скилл email-systems для Claude Code и Codex помогает настроить отправку транзакционных писем, вёрстку шаблонов и DNS-записи. Включается при создании почтовой инфраструктуры или отладке спам-фильтров. CX Codex +1 132установок graphql-expert Скилл graphql-expert для Claude Code помогает проектировать схемы GraphQL, писать резолверы и оптимизировать запросы. Включается при создании API или настройке DataLoader. CX Codex +1 132установок

Спонсоры проекта

Компании, которые помогают держать аналитику открытой