battle-card-builder
Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.
npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Battle Card Builder ## Purpose Build a field-action competitive battle card from public evidence: **use or gather evidence → search plan (if gathering) → draft card with per-claim labels → appendix → next-step options.** A battle card is the artifact a rep opens mid-deal, not a research report — it must fit thirty seconds, every claim must survive being said out loud to a hostile audience, and every claim therefore carries a source URL, a date, and a Fact/Inference/Assumption label. Most battle cards in the wild are unlabeled inference; this skill exists because of what it costs a rep when one of those turns out wrong. ## Input **Works best with:** your product and its primary differentiation, and **the one competitor** this card targets. **Also useful:** the deal context (segment, buyer, common objections or the loss reason that triggered this card), and any [`competitive-research-snapshot`](../competitive-research-snapshot/SKILL.md) or [`competitive-intel-watch`](../competitive-intel-watch/SKILL.md) output in session — the skill uses existing evidence and searches only for gaps and anything older than one quarter. Input supplied inline with the invocation — text after the skill
- Purpose
- Input
- Key Concepts
- Application
- Card schema (do not reorder)
- Final Step (offer exactly 4 options)
- Examples
- Common Pitfalls
- References
What does the battle-card-builder skill do?
Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.
How do I install it?
Run `npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From deanpeters/Product-Manager-Skills, a repository with 6,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.