battle-card-builder · deanpeters — Claude Code skill for evidence-backed competitive battle cards
battle-card-builder builds a sales battle card from public evidence: pricing pages, reviews, release notes. Every claim gets a source URL, date, and a Fact/Inference/Assumption label.
CC-BY-SA-4.0 1,300 installs ★ 8,115 updated 2026-10-16
npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -a claude-codeWhat battle-card-builder does
This skill assembles a field-action card for deals where one competitor keeps showing up. The agent digs through pricing pages, reviews, release notes and customer stories, then drafts a card a rep can open mid-conversation. The card is sized for a thirty-second read; depth lands in the appendix.
Every claim carries a source URL, a date, and a Fact, Inference or Assumption label. That is the point: most battle cards are unlabeled inference, and a rep pays for that when a claim collapses in front of a hostile audience. The skill forbids inventing features, pricing, market share, customer wins, roadmap items and quotes.
The card schema is fixed: a thirty-second summary, a "Say This" section capped at four sourced talking points, trap questions with documented answers, "Watch Out For", a pricing snapshot, a "Do Not Say" list, and an evidence table in the appendix. After the draft the agent offers exactly four next steps: pressure-test the card, build one for a second competitor, set up a watch skill to keep it current, or compress it for mobile.
If a competitive snapshot or watch report already sits in the session, the skill uses it as the evidence base and searches only for gaps and material older than one quarter. Starting empty, it asks at most three questions: product and competitor, segment and buyer, triggering objection. Unanswered questions become labeled assumptions.
A run takes 20–35 minutes, so budget for that before you kick it off mid-deal.
What it helps with
- assemble a competitor card from public sources
- label every claim with a URL, date and evidence type
- separate facts from inferences and assumptions
- write trap questions with documented answers
- refresh a stale card in 20–35 minutes
Example prompts for the agent
- Use the competitive-research-snapshot in this session and draft a battle card for an enterprise deal
- Rebuild the card for Competitor B: re-check anything older than one quarter, reuse the rest from the report
How to install battle-card-builder
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -a claude-code2Manually: put the files in place
~/.claude/skills/battle-card-builder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/battle-card-builder/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -a codex2Manually: put the files in place
.agents/skills/battle-card-builder/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -a cursor2Manually: put the files in place
.cursor/skills/battle-card-builder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills skills/battle-card-builder2Manually: put the files in place
.github/skills/battle-card-builder/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/battle-card-builderManually: put the files in place
.devin/skills/battle-card-builder/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about battle-card-builder
How do I install battle-card-builder in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -a claude-code. The skill file lands at ~/.claude/skills/battle-card-builder/SKILL.md.
What does battle-card-builder do?
It researches a competitor from public sources and drafts a sales battle card: talking points, trap questions, pricing, risks. Every claim gets a source URL, date, and a Fact/Inference/Assumption label.
How is this different from a normal battle card?
Typical cards are full of unlabeled inference. This skill requires a source and a label on every claim, and it explicitly bans inventing features, prices and quotes. A rep can defend every line before saying it out loud.
Similar skills
All skills for Agent setup: memory, context, orchestration →battle-card-builder by other authors comes first.