All skills
deanpeters avatar

/battle-card-builder

@eb7a51e

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.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/battle-card-builder

This session only. Nothing lands on disk.

examplessample-industrial.md

≈1.7k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Battle Card Builder — Worked Example (Industrial)

All companies, products, URLs, and figures are fictional. Industrial sibling of sample.md, completing the industrial chain: Northfield Automation arms its integrator-channel sellers against Helix Motion Systems in retrofit-monitoring deals, rebuilding from the November watch report's update flags. Note two industrial differences: the "buyer" the card serves includes the systems integrator (the channel is in the room), and pricing evidence is list-price-less — the Pricing & Packaging section works with what's public and labels the rest.

Invocation: Build a battle card: Northfield retrofit monitoring vs Helix Foresight, mid-size mixed-vendor plants, integrator-led deals — triggered by the watch report flagging the Thirty-Second Read as stale. Snapshot and watch report in session.


Battle Card: Northfield Retrofit Monitoring vs Helix Foresight

As-of date: 2026-11-10 Deal context: mixed-vendor plants, 100-500 employees; integrator-led deals; plant manager + corporate engineering in the room

1. Thirty-Second Read

  • They win when: the plant is predominantly Helix equipment — Foresight on their own components is credible and channel-backed — Fact (compatibility docs, Nov 2026)
  • We win when: the floor is mixed-vendor — Foresight's own docs scope it to Helix equipment, and their CFO scoped the program to their installed base — Fact (docs; Q3 transcript)
  • The one thing to say: "Walk the floor and count the nameplates — we monitor all of them; ask what Foresight covers."

2. Say This

  • "Foresight is scoped to Helix equipment — their own compatibility list says so" — Fact (docs, Nov 2026)
  • "Their CFO told investors Foresight expands 'from our installed base rather than chase greenfield' — mixed floors are not their plan" — Fact, exact quote (Q3 transcript, Oct 2026)
  • "Our retrofit ships with the machinery-safety documentation pack — your compliance file builds itself during commissioning" — Fact (our product docs); no competitor lists an equivalent — Fact (feature absence, all three checked Nov 2026)
  • (For the integrator:) "White-label the dashboards; the plant sees your brand" — Fact (partner program page)

3. Ask This (trap questions)

  • "Ask what happens to Foresight coverage on your non-Helix lines" — documented answer: not on the compatibility list — Fact (docs)
  • "Ask whether Foresight monitoring requires a Helix service contract" — documented answer: bundled with aftermarket agreements per the program page — Fact (Foresight page, Nov 2026)

4. Watch Out For

  • Their distributor and service network is real and beloved — do not attack Helix component quality or their channel; the integrator in the room probably resells them — Fact (channel structure; deal-loss debriefs)
  • Likely counter: "Northfield is a software company; who services the sensors at 2 a.m.?" — Inference (their services-depth positioning). Response: the integrator services it — that's the model, and it's why the integrator is in the room.

5. Pricing & Packaging Snapshot

  • Helix publishes no Foresight list pricing; program page ties it to aftermarket service agreements — Fact (page, as of Nov 10, 2026); deal anecdotes suggest per-asset subscription framing — Inference (two win/loss debriefs; small sample, labeled)
  • Ours: published per-line pricing with integrator margin schedule — Fact (pricing)
  • Where "contact sales" hides the number: their multi-plant corporate agreements — unknowable from outside; do not guess in the room — Assumption territory, flagged

6. Do Not Say

  • Don't say "Helix is abandoning digital" — they re-scoped it, they didn't kill it; overclaiming invites a correction from any buyer who reads transcripts — (basis: watch report, Nov 2026)
  • Don't quote a Foresight price — none is published; a guessed number detonates if the Helix rep is in the follow-up meeting — (do-not-invent list)
  • Don't promise coverage of every legacy protocol — our own compatibility matrix has gaps; hand the integrator the matrix instead — Fact (our docs)

Appendix: Evidence Table

Claim Label Source Date
Foresight scoped to Helix equipment Fact example.com/helix/foresight-docs 2026-11
"From our installed base rather than chase greenfield" Fact (exact quote) example.com/helix/q3-transcript 2026-10
Foresight bundled with aftermarket agreements Fact example.com/helix/foresight 2026-11
No competitor ships safety-documentation automation Fact (absence) all three vendors' docs 2026-11
Per-asset subscription framing in Helix deals Inference 2 win/loss debriefs 2026-10

Assumptions to Validate

  • Foresight's Helix-only scope survives their next planning cycle (reversal tripwire lives in the quarterly watch)
  • The 2 a.m. servicing objection actually costs us deals (instrument win/loss)
  • Integrator margin schedule is competitive with their Helix resale economics

Why this example works

  • The channel is a card audience, not just a deal factor. One talking point and the entire servicing counter exist for the integrator — in an integrator-led market, a card that only arms your own rep misses the person who actually closes.
  • Opaque pricing handled honestly. No list price exists, so the card gives the rep the documented framing, labels the per-asset read as a two-debrief Inference, and explicitly forbids guessing — the industrial version of the do-not-invent discipline.
  • The strongest ammunition is the competitor's own words — a compatibility list and an exact CFO quote. Nothing in Say This requires the buyer to trust Northfield's opinion of Helix.
  • "Do Not Say" prunes the overclaim ("abandoning digital") that the watch report's nuance would otherwise decay into by the third sales retelling — cards protect reps from their own team's simplifications.

Source: SKILL.md on GitHub

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The 'battle-card-builder' skill is a workflow designed to research and draft competitive battle cards using public information. It instructs the agent to gather evidence from sources like pricing pages and reviews, then format the findings into a structured report with source citations and factual labels. No security risks or malicious patterns were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

Signed by skilld at eb7a51e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 3 months ago
argument-hint
[your product vs which competitor, and the deal context]
type
workflow
theme
market-intelligence
Other metadata
intent
Autonomous battle card construction: given your product and one competitor, the AI does the fieldwork — pricing pages, reviews, release notes, customer stories — and produces a field-action card with a source URL and Fact/Inference/Assumption label on every claim, sized to a rep's thirty seconds.
best_for
[
  "Arming sales against one competitor with claims they can actually defend",
  "Turning a competitive snapshot or watch report into a field-action artifact",
  "Building trap questions whose documented answers favor you"
]
scenarios
[
  "We keep hitting the same rival in enterprise deals — build the battle card from public evidence",
  "Our battle card is six months old and sales stopped trusting it; rebuild it with sources"
]
estimated_time
20-35 min per run

README badge

README badge for deanpeters/product-manager-skills/battle-card-builder