agentleFS
Sign inStart free
yuusakuriyuusakuri/agent-skills/skills/competitive-battlecard/SKILL.md

competitive-battlecard

Skill2 starsChanged 10 days agoMITView on GitHub

Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    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:

    Create a concise, sales-ready battlecard for use against a specific competitor.

    line 8
  2. Distinctive:

    Use web search to research the competitor's current product, pricing, positioning, and recent changes.

    line 14

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

Competitive Battlecard

Create a concise, sales-ready battlecard for use against a specific competitor.

Context

You are creating a competitive battlecard for $ARGUMENTS.

Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.

Instructions

  1. Research the competitor (use web search):
    • Current product offerings and features
    • Pricing tiers and model
    • Target market and positioning
    • Recent product launches or changes
    • Known strengths and weaknesses
    • Customer reviews and sentiment (G2, Capterra, Reddit)

  2. Create the battlecard with these sections:

    Company Overview

    • Founded, HQ, funding/revenue (if public)
    • Target market and ICP
    • Positioning in one sentence

    Quick Comparison

    CapabilityUsThemWinner
    [Feature area 1][Our approach][Their approach][Us/Them/Tie]
    [Feature area 2].........
    Pricing.........
    Support.........

    Where We Win

    • [Advantage 1]: [Proof point or customer quote]
    • [Advantage 2]: [Specific capability they lack]
    • [Advantage 3]: [Better approach with reasoning]

    Where They Win

    • [Their strength 1]: [Our counter-positioning]
    • [Their strength 2]: [How we mitigate this gap]

    Common Objections & Responses

    Prospect SaysRespond With
    "Competitor X has [feature]""[Our alternative approach and why it's better for them]"
    "They're cheaper""[Value framing: total cost of ownership, ROI, hidden costs]"
    "They're more established""[Our advantages: speed, innovation, focus, support]"

    Landmines to Plant

    Questions to ask the prospect that highlight competitor weaknesses:

    • "How important is [area where we excel] to your team?"
    • "Have you evaluated [specific capability they lack]?"

    Win/Loss Patterns

    • We tend to win when: [pattern]
    • We tend to lose when: [pattern]
    • Key differentiator in competitive deals: [what tips the scale]
  3. Keep it scannable: Sales reps need to reference this during calls. Use tables, bold text, and short bullets.

Save as markdown. Format for easy printing or sharing in Notion/Confluence.

Further Reading

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