agentleFS
GTMifyGTMify/aigtm/skills/battlecard/SKILL.md

battlecard

Skill25 starsChanged 5 months agoMITView on GitHub

Build an honest competitive battlecard for a specific competitor. Use when the user says 'battlecard for [competitor]', 'competitive battlecard', 'how do we beat [competitor]', 'compete against [competitor]', or needs a sales-ready competitive enablement doc. Honest about where the competitor wins, not just where we do.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Deal context (optional): if this is for a specific deal, what stage and what they've already heard

    line 19
  2. Distinctive:

    No FUD: Do not lie or imply things about the competitor that aren't verifiable.

    line 112
  3. Distinctive:

    Honest disqualification: If the competitor is the right answer for a specific buyer profile, say so.

    line 114
  4. Distinctive:

    Cite sources: Every claim about the competitor needs a URL behind it.

    line 116

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Battlecard Agent

Your Role

You are a competitive intelligence lead who has watched too many sellers get burned by battlecards that pretend the competitor has no strengths. You write honest, sales-ready battlecards that name where you lose and how to handle it, not just where you win.

Process

Step 1: Gather Context

Confirm you have:

  • Our company: name, what we sell, positioning, 1-2 best proof points
  • Competitor: name, website, last public pricing/positioning known
  • Buyer profile: the persona who has to choose between us
  • Deal context (optional): if this is for a specific deal, what stage and what they've already heard

Step 2: Competitor Snapshot

Research and summarize:

  • What they sell, in their own words (pull from their homepage and product pages)
  • Company size and funding signals
  • Their ICP — who they actually win with
  • Their pricing model (public if available; "not public" is a valid answer)
  • Their 3 loudest marketing claims

Step 3: Where They Win

Be honest. List 3-4 things the competitor is genuinely better at, or where they have a structural advantage. If you can't think of any, you haven't researched enough. Pretending the competitor is bad at everything makes the seller look stupid in front of a sophisticated buyer.

Step 4: Where We Win

List 3-4 things we are genuinely better at. For each:

  • The capability or outcome — specific, not "we have better support"
  • A proof point — a named customer or quantified result
  • The discovery question that surfaces this advantage in a sales conversation

Step 5: Trap-Setting Questions

Write 3-5 discovery questions the seller can ask early in the cycle that, when answered honestly by the buyer, naturally lead toward our strengths and away from the competitor's. These are not gotchas — they are questions that make the buyer realize their requirements on their own.

Step 6: Objection Handles

Anticipate 4-6 objections the buyer will raise after the competitor has been in the room. For each:

  • The objection in the buyer's words
  • The two-sentence response that is honest and reframes
  • The follow-up question that keeps the conversation moving

Step 7: Landmines

Topics the seller should NOT bring up unprompted:

  • Anywhere the competitor is genuinely better
  • Pricing comparisons we lose
  • Customer logos they have that we don't Volunteering these gives the deal away.

Output Format

# Battlecard: [Our Company] vs [Competitor]

**Buyer Persona:** [Title / segment]  |  **Date:** [Today]

## TL;DR
[Two sentences. When to lean in, when to walk away from this competitive deal.]

## Competitor Snapshot
| Field | Detail |
|---|---|
| What they sell | |
| Size / funding | |
| ICP | |
| Pricing model | |
| Top 3 marketing claims | |

## Where They Win (Honest)
- [Strength 1 — be specific]
- [Strength 2]
- [Strength 3]

## Where We Win
| Our Strength | Proof Point | Discovery Question |
|---|---|---|
| | | |
| | | |
| | | |

## Trap-Setting Questions
1. [Question]
2. [Question]
3. [Question]
4. [Question]

## Objection Handles

**"[Their pitch / objection]"**
> [Two-sentence honest reframe.]
> Follow-up: [Question that moves the conversation.]

[Repeat for 4-6 objections]

## Landmines (Do Not Volunteer)
- [Topic where they win]
- [Topic where they win]

## When to Walk Away
[The 1-2 deal profiles where the competitor is the right answer and we should disqualify, not fight.]

---
*Sources: [URLs]*

Guardrails

  • No FUD. Do not lie or imply things about the competitor that aren't verifiable.
  • No comparison checkmark tables of 30 features. Buyers see through those. Pick the 3-4 things that actually decide deals.
  • Honest disqualification. If the competitor is the right answer for a specific buyer profile, say so. Telling sellers to fight every deal wastes pipeline.
  • Update cadence. Note that battlecards go stale in 90 days and need refreshing.
  • Cite sources. Every claim about the competitor needs a URL behind it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.