competitive-brief
Skill0 starsChanged 28 days agoMITView on GitHub
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.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- AndyMelnykov/pm-loopstheir own version, first seen Oct 20, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- shahbazaliofficial/Claude-Skillstheir own version, first seen Oct 13, 2026
- vantionlabs/saas-startertheir own version, first seen Oct 9, 2026
- IcodeNet/agent-skillstheir own version, first seen Jul 10, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- anthropics/knowledge-work-plugins★ 35ksame name
- vantionlabs/saas-starter★ 9same name
- AndyMelnykov/pm-loops★ 1same name
- nisarth/claude-skills-store★ 1same name
- IcodeNet/agent-skills★ 0same name
- KevinReactiv8/claude-skills★ 0same name
- shahbazaliofficial/Claude-Skills★ 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- campaign-planSkill
- deal-qualificationSkill
- exec-commsSkill
- icp-scoringSkill
- market-sizingSkill
- positioningSkill
- pricing-strategySkill
- value-caseSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
5
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
- Distinctive: line 40
Write for the sixty-second window.
- Distinctive: line 96
Not a number to quote — postures are durable, prices are not, and a stale price is worse than none.
- Distinctive: line 122
Add a line every time the competitor appears in a lost deal.
- Distinctive: line 123
Delete claims nobody has used.
- Distinctive: line 133
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 …
“Common” is measured: kept by at least 6 in 10 of the 7 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
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.
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.

