Agent skill
competitive-brief
Build a competitive battlecard or brief that a seller can actually use in a live conversation — honest strengths, real weaknesses, trap-setting questions, and landmines.
Filed under Positioning and messaging.
From erickdronski/gtm-skills · 9 skill entries · 0 · pushed 2026-10-06
What it does when it runs
Build a competitive battlecard or brief that a seller can actually use in a live conversation — honest strengths, real weaknesses, trap-setting questions, and landmines. Use this whenever the user asks for a battlecard, competitive analysis, a comparison against a named competitor, how to beat or displace someone, competitive positioning, win-loss themes, or how to respond when a prospect mentions a rival. Also use it when a competitive doc reads like marketing copy and needs to become something a rep can survive a real objection with.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/erickdronski/gtm-skills.git /tmp/gtm-skills git -C /tmp/gtm-skills sparse-checkout set "skills/competitive-brief" mkdir -p ~/.claude/skills/competitive-brief cp -R "/tmp/gtm-skills/skills/competitive-brief/." ~/.claude/skills/competitive-brief/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 9 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add erickdronski/gtm-skills /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from erickdronski/gtm-skills/blob/ef1661418836049c4c5abad0c037f9c7e3fa7c6a/skills/competitive-brief/SKILL.md, which is licensed MIT (repository). 958 words, 12 headings.
Competitive brief
A battlecard has one job: help a seller handle sixty seconds of a live conversation without lying. Most battlecards fail at this because they are written as marketing artifacts — every competitor weak, every one of our features a differentiator — and experienced sellers stop reading them because using them gets them caught.
The reliable test for whether a battlecard is any good: would a rep still trust it after a prospect pushed back on one of its claims? That standard forces honest weaknesses, which is what makes the rest of the card credible.
Sourcing
Rank sources by how much they should move your conclusions:
- Your own win-loss data. What buyers actually said. Nothing else is close.
- Recorded calls where the competitor came up. Real objections, real language.
- The competitor's own materials — docs, pricing, changelog, job postings. Public, verifiable, and quotable back to a prospect.
- Customer reviews. Directionally useful, heavily selection-biased.
- What your team believes. Usually a mix of accurate pattern-matching and eighteen-month-old information presented as current.
Label which tier each claim came from. A battlecard where every claim reads as equally certain is one where the reader cannot tell which parts to lean on.
Date every factual claim about a competitor. Products change. A card asserting a gap that was closed two quarters ago will get a rep publicly corrected by a prospect, which costs more than the card ever earned.
Structure
Write for the sixty-second window. Front-load, keep it scannable, and put detail below the fold.
The one-liner
How to frame this competitor in a single sentence a rep can say out loud. Not "we're better" — the honest frame:
They are a strong fit for teams that want a single vendor for everything and can accept a longer implementation. We win where the team needs to be live in weeks and cares about depth in one area.
That sentence concedes real ground, which is precisely why the next thing the rep says gets believed.
Where we genuinely win
Two or three, each with proof and each specific enough to be checkable. "Faster" is not a claim. "Live in 3 weeks versus their published 8-to-12-week implementation" is.
Where they genuinely win
The section that makes the card trustworthy, and the one most often deleted. Include it. A rep who knows the real gaps can navigate to ground where they are strong; a rep who has been told there are no gaps gets ambushed and improvises badly.
For each, note whether it is on the roadmap and whether the rep may say so.
Trap-setting questions
Questions that surface the competitor's structural weaknesses without naming them. Structural is the operative word — architectural or business-model constraints they cannot quickly fix, not a feature they might ship next month.
"How are you planning to handle it when the volume triples during peak? What does that do to your costs on their pricing model?"
The question is legitimate on its own terms, which is what separates a good trap question from a cheap one. If the prospect's honest answer is "that's fine", the question has cost you nothing.
Landmines they set for us
What the competitor says about you, and the honest response. Reps encounter this constantly and improvise without it.
Format each as: what they say → whether it is true → what to say. The middle column matters. Some of what a competitor says about you is accurate, and a rep who knows which parts can address them directly instead of denying something the prospect can verify.
Pricing posture
How they price, where they discount, what their contract typically looks like. Not a number to quote — postures are durable, prices are not, and a stale price is worse than none.
Handling the competitor in conversation
Three rules that hold across almost every situation:
Never disparage. Trashing a competitor makes the buyer defensive about a decision they may have already partly made, and it makes you look worried. Frame as fit, not as quality.
Do not chase feature parity. "We have that too" concedes the frame that the competitor's feature set is the evaluation criteria. Reframe to the criteria where you are strong: "Yes — the difference is what happens when X."
When you lose on fit, say so. A rep who says "honestly, for what you have described, they may be the better fit" earns a relationship and often a future deal. This is not weakness; it is the highest-leverage credibility move available, and it costs a deal you were going to lose anyway.
Maintenance
A battlecard is a living document with a decay rate:
- Review quarterly, minimum.
- Re-verify every dated claim before each review.
- Add a line every time the competitor appears in a lost deal.
- Delete claims nobody has used. An unused claim is noise crowding out the three that work.
Track which lines reps actually use. The card usually shrinks, and gets better as it does.
Common failures
No honest weaknesses. Covered above, and the single most common defect.
Written for marketing, read by nobody. If it does not fit on one screen, the rep will not open it during a call, which is the only moment it matters.
Stale claims presented as current. Undated assertions about a competitor's gaps age into liabilities.
Comparing against their marketing rather than their product. Their homepage overstates what they do, exactly as yours does. Compare against the docs.
One card for every segment. You may lose to a competitor in enterprise and beat them in mid-market for structural reasons. One card averaging those cases is wrong in both.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- competitive-exec-brief by varunk130 · 7
- competitive-intel-content-brief by thundercatdev · 0
- yt-competitive-analysis by ericosiu · 3,627
- seo-content-brief by OpenClaudia · 714
- meeting-brief-generator by Varnan-Tech · 674
- competitive-analysis by shawnpang · 350
- run-competitive-intel by Othmane-Khadri · 318
- away-brief by sno-ai · 264
Need help setting it up?
This page tells you what competitive-brief does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.