battlecard
Skill1 starsChanged 4 months agoMITView on GitHub
On-demand competitive card when a specific competitor comes up — approved talk track, the trap question to ask, what NOT to claim, and where the landmines are. Use when the rep says "they use [competitor]", "battlecard for...", "how do we beat [competitor]", or "they're evaluating [tool]".
6 other projects use a version of this.
Adopted by
Most recently taken up by
- calven-ai/calven-mcptheir own version, first seen Nov 1, 2026
- Hyde-and-Larkin/product-marketing-toolkittheir own version, first seen Nov 1, 2026
- calven-ai/marketing-as-codetheir own version, first seen Oct 7, 2026
- tga-cheetung/competitive-intel-enginetheir own version, first seen Jul 23, 2026
- styfinity/claude-marketing-departmenttheir own version, first seen Jul 8, 2026
- GTMify/aigtmtheir own version, first seen May 25, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- GTMify/aigtm★ 25same name
- calven-ai/marketing-as-code★ 10same name
- styfinity/claude-marketing-department★ 6same name
- calven-ai/calven-mcp★ 3same name
- Hyde-and-Larkin/product-marketing-toolkit★ 2same name
- tga-cheetung/competitive-intel-engine★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- account-briefSkill
- build-listSkill
- dojoSkill
- draft-sequenceSkill
- handle-replySkill
- meeting-prepSkill
- post-callSkill
- reactivateSkill
- setupSkill
- signal-watchSkill
- voice-interviewSkill
- what-worksSkill
- work-inboundSkill
- write-emailSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read ${CLAUDE_PLUGIN_ROOT}/references/messaging.md if not already in context — the approved competitive claims live there and they are the …
- Distinctive: line 66
If the same competitor keeps appearing (3+ times in a stretch), flag it for the what-works weekly and for your marketing lead — a pattern …
“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.
Files
Battlecard
Input: the competitor and the situation (mid-call, drafting a reply, prepping a meeting). Output: a card you can act on in the next five minutes. The prime directive: approved claims and fresh intel are different substances — the first goes in emails, the second stays on calls with a hedge ("last I looked...").
Before you build the card
Read ${CLAUDE_PLUGIN_ROOT}/references/messaging.md if not already in context — the approved competitive claims live there and they are the ceiling. This skill never invents a claim; it packages approved ones and adds current context. Never invent a competitor name.
Step 1 — Approved foundation (from messaging.md)
The organizing frame: [your organizing competitive frame from messaging.md] — use exactly the framing approved there, never a version you improvise.
Map each competitor to its category, then pull only the approved angle for that category:
- The legacy incumbent (often acquired) → roadmap subject to a parent's strategy; slow post-acquisition velocity; built for an earlier era. Lean on your product-velocity / independence angle, per messaging.md.
- The native / status-quo tool → built for a narrower, earlier use case; doesn't cover what the modern problem requires. Lean on your breadth angle, per messaging.md.
- A point solution that owns one narrow slice → NEVER claim you beat them at their specialty. Position your coverage of that slice as "included," and win on the whole-platform contrast.
- A single-capability point solution → don't claim deeper depth in their one area; your claim is that capability as part of the whole platform.
- Modern point solutions → narrower coverage and shallower depth than a full platform. Still no disparaging tone — these are credible products and Tier 1 buyers know it; win on the contrast, not contempt.
- A DIY / in-house build → eng-time cost; the build decays. Lean on the "stop maintaining this yourself" angle, per messaging.md.
The banned-claims list (applies against everyone): there are claims you must not make. They live in messaging.md's "Do NOT claim" section — do not claim to be best-at anything a point solution specializes in, and do not use any superlative messaging.md hasn't cleared. Also banned: every item on messaging.md's "Never mention" list (unreleased features). If the winning move requires one of these claims, the honest card says "this one's a knife fight — bring your admin or an AE in."
Step 2 — Fresh intel (Exa, 2-3 searches)
Current-quarter context only: pricing/packaging changes, acquisition or leadership news, G2/Reddit sentiment shifts, renewal-relevant events. Tag every fresh item [unverified — say it hedged, don't write it]. Recent complaints from real users (community forums, G2) are the most useful find — they tell you which pain to ask about.
Step 3 — The card
# Battlecard: [Competitor] · [date] · situation: [call/email/meeting]
## Say this (approved, 2 sentences)
[the talk track — differentiator framed for the persona at hand]
## Ask this (the trap question)
[ONE question whose honest answer exposes the gap — e.g. legacy incumbent:
"when's the renewal, and has the roadmap changed since the acquisition?" ·
point solution: "[the trap question that exposes the point solution's coverage
gap — see messaging.md]" · DIY: "how many eng-hours a month keep the dashboard
alive?"]
## Don't claim
[banned claims relevant here + anything messaging.md is silent on]
## Landmines (where they're genuinely strong)
[concede-and-reframe lines: "if [strength] is the whole requirement, they're a
fine choice — the question is [reframe to our ground]." Never argue a true point.]
## Fresh intel [unverified — calls only, hedged]
[current items + sources]
## One-liner for email
[a single approved sentence safe to put in writing]Step 4 — Offer the next move
Mid-call situation → offer to drill it: "want to run this in the dojo — I'll play the [Competitor] fan?" Drafting situation → hand off to write-email/handle-reply with the card in context. Meeting tomorrow → fold the card into meeting-prep.
If the same competitor keeps appearing (3+ times in a stretch), flag it for the what-works weekly and for your marketing lead — a pattern in competitive mentions is market intel, not just a sales obstacle (guardrail #7 escalation applies to anything that smells like a positioning question).
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
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.

