agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/competitive-battlecard/SKILL.md

competitive-battlecard

Skill13 starsChanged 23 days agoMITView on GitHub

Use this skill when reps need a one-page battlecard to win against a specific competitor: \"make a battlecard for X\", \"how do we beat X\", \"competitive talk track\", \"what to say when they mention X\". Produces a rep-ready card with when you win and lose, quick positioning, the top differentiators with proof, landmine questions, objection responses, pricing notes and traps to avoid, written to be used live on a call.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-experiments-existing, prioritize-assumptions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skytiger6724Skill

    brainstorm-experiments-existing

    Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

    Also in 7 projects that use this

  • skytiger6724Skill

    prioritize-assumptions

    Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.

    Also in 7 projects that use this

  • About-IntelligenceSkill

    positioning-ideas

    Brainstorm product positioning ideas differentiated from competitors.

    Also in 8 projects that use this

  • About-IntelligenceSkill

    product-name

    Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.

    Also in 8 projects that use this

  • 45ckSkill

    pestle-analysis

    Also in 7 projects that use this

  • launchapp-devSkill

    interview-script

    Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.

    Also in 9 projects that use this

  • +4 more from skytiger6724
  • +2 more from About-Intelligence

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 7

    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:

    Use this when a competitor comes up often on calls.

    line 16
  2. Distinctive:

    Only differences that matter to buyers and that you can prove.

    line 33
  3. Distinctive:

    Read references/battlecard-template.md for the full one-page template and a filled example.

    line 44
  4. Distinctive:

    MUST keep claims about the competitor factual, current and sourced.

    line 55
  5. Distinctive:

    MUST include when to walk away.

    line 56
  6. Distinctive:

    NEVER disparage the competitor or its people.

    line 57
  7. Distinctive:

    NEVER use confidential competitor information.

    line 58

“Common” is measured: kept by at least 6 in 10 of the 14 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

Use this when a competitor comes up often on calls. A battlecard is the on-call version of a teardown: short enough to read in 30 seconds with the buyer still talking.

Inputs

  • Competitor research (or run a teardown first).
  • Win-loss notes against this competitor.
  • Your differentiators and approved proof.

The play

1. Lead with when you win and lose

The most useful line on the card. Reps need to know whether to fight or qualify out.

2. Write the quick positioning

Two sentences a rep can say when the buyer mentions the competitor, acknowledging their strength and stating your difference fairly.

3. Three differentiators with proof

Only differences that matter to buyers and that you can prove. Each: what, why it matters to the buyer, proof.

4. Landmine questions

Questions the rep asks that lead the buyer to discover the competitor's weakness on their own. Fair, neutral, answerable.

5. Objection responses

"They're cheaper", "They have feature X", "We already use them for Y". One or two lines each.

6. Traps

What the competitor says about you and how to answer it; what not to do (trash talk, matching their discount without a trade).

Read references/battlecard-template.md for the full one-page template and a filled example.

What good looks like

  • Fits on one screen; a rep can find an answer mid-call.
  • Fair about the competitor's strengths; buyers trust reps who are.
  • Updated each quarter with fresh win-loss notes and pricing.
  • The common mistake is a ten-page feature comparison that reps never open on a call.

Rules

  • MUST keep claims about the competitor factual, current and sourced.
  • MUST include when to walk away.
  • NEVER disparage the competitor or its people.
  • NEVER use confidential competitor information.

Example prompts

  • "Make a battlecard against Acme for our mid-market reps."
  • "Turn this teardown into a one-page battlecard."
  • "What should I say when a prospect says 'Acme is half the price'?"

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.

Check your setup, free