Create a competitive sales battlecard for any competitor
Sales Battlecard Skill
Create a competitive sales battlecard for any competitor. Use when asked to build a battlecard, competitive comparison, sales cheat sheet, or objection handling guide for a specific competitor.
--- name: sales-battlecard description: "Create a competitive sales battlecard for any competitor. Use when asked to build a battlecard, competitive comparison, sales cheat sheet, or objection handling guide for a specific competitor. Produces a one-page battlecard with positioning, differentiators, objection responses, and landmines." --- # Sales Battlecard Skill Produces a practical one-page competitive battlecard that sales reps can use in calls — not a theoretical analysis. ## Required Inputs - **Your product/company** - **Competitor name** - **Your target customer** (ICP) - **Your top 3 differentiators** vs this competitor - **Common objections** when competing against them - **Known competitor weaknesses** ## Output Structure
Overview
Produces a practical one-page competitive battlecard that sales reps can use in calls — not a theoretical analysis.
Manual install (npx, ZIP)
Claude Code
npx skills add mohitagw15856/pm-claude-skills --skill sales-battlecard -g -a claude-codeClaude Code (manual)
mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \
| tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/sales-battlecardWindows (PowerShell)
New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/df956a669a8b095c673c/sales-battlecard.zip" -OutFile "$env:TEMP\sales-battlecard.zip"; Expand-Archive "$env:TEMP\sales-battlecard.zip" -DestinationPath "$HOME\.claude\skills" -ForceClaude.ai / desktop
Codex, Cursor, other agents
Connects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md3.4 KB
Read the files here
mohitagw15856/
SKILL.md
Show the full text97 lines
Sales Battlecard Skill
Produces a practical one-page competitive battlecard that sales reps can use in calls — not a theoretical analysis.
Required Inputs
- Your product/company
- Competitor name
- Your target customer (ICP)
- Your top 3 differentiators vs this competitor
- Common objections when competing against them
- Known competitor weaknesses
Output Structure
Battlecard: [Your Product] vs [Competitor]
Updated: [Date] — Review quarterly
In One Sentence
When a prospect mentions [Competitor], say: "[Your positioning in one sentence]"
Why Customers Choose [Competitor]
(Be honest about their genuine strengths)
- [Strength 1]
- [Strength 2]
Why Customers Choose Us
(Specific differentiators with proof points)
- [Differentiator 1]: [Proof point — customer outcome or capability]
- [Differentiator 2]: [Proof point]
Objection Responses
"[Competitor] is cheaper" "You are right their list price is lower. What our customers find is [specific TCO difference]. [Customer] saw [result]. Should we explore total cost of ownership?"
"We already use [Competitor]" "That is helpful. What is working well? [Listen] And what is one thing you wish was better?"
"[Competitor] has [feature] you do not" "You are right. What problem are you solving with that feature? [Listen] Here is how our customers solve that..."
Landmines to Plant
- "How do you currently handle [area where competitor is weak]?"
- "What happens when you need to [scenario competitor struggles with]?"
Traps to Avoid
- Never badmouth [Competitor] directly
- Do not lead with features — lead with the prospect problem
- Do not claim you do everything better — be specific about where you win
When We Win / When We Lose
We win when: [Scenario — e.g. customer prioritises outcome over price] We lose when: [Honest scenario — e.g. primary driver is lowest upfront cost]
Quality Checks
- Competitor strengths are listed honestly (not minimised)
- Differentiators have proof points (not just claims)
- Objection responses are conversational (not scripted-sounding)
- Landmine questions are natural and non-confrontational
- "When we lose" is included and honest
- Battlecard has a review date
Example Trigger Phrases
- "Build a battlecard against [competitor]"
- "Create a competitive cheat sheet for [competitor]"
- "Write objection handling for [competitor] comparisons"
Anti-Patterns
- Do not minimise or ignore genuine competitor strengths — sales reps who encounter them unprepared lose credibility
- Do not write differentiators without proof points — a claim without evidence is marketing, not a battlecard
- Do not make the battlecard exhaustive — it is a one-page cheat sheet, not a full competitive analysis
- Do not include a "When we lose" section that is dishonestly optimistic — honest loss scenarios build rep trust
- Do not skip the review date — an outdated battlecard with wrong information is worse than no battlecard
| 1 | |
| 2 | name sales-battlecard |
| 3 | description "Create a competitive sales battlecard for any competitor. Use when asked to build a battlecard, competitive comparison, sales cheat sheet, or objection handling guide for a specific competitor. Produces a one-page battlecard with positioning, differentiators, objection responses, and landmines." |
| 4 | |
| 5 | |
| 6 | # Sales Battlecard Skill |
| 7 | |
| 8 | Produces a practical one-page competitive battlecard that sales reps can use in calls — not a theoretical analysis. |
| 9 | |
| 10 | ## Required Inputs |
| 11 | **Your product/company** |
| 12 | **Competitor name** |
| 13 | **Your target customer** (ICP) |
| 14 | **Your top 3 differentiators** vs this competitor |
| 15 | **Common objections** when competing against them |
| 16 | **Known competitor weaknesses** |
| 17 | |
| 18 | ## Output Structure |
| 19 | |
| 20 | |
| 21 | |
| 22 | # Battlecard: [Your Product] vs [Competitor] |
| 23 | Updated: [Date] — Review quarterly |
| 24 | |
| 25 | |
| 26 | |
| 27 | ### In One Sentence |
| 28 | When a prospect mentions [Competitor], say: "[Your positioning in one sentence]" |
| 29 | |
| 30 | |
| 31 | |
| 32 | ### Why Customers Choose [Competitor] |
| 33 | (Be honest about their genuine strengths) |
| 34 | [Strength 1] |
| 35 | [Strength 2] |
| 36 | |
| 37 | |
| 38 | |
| 39 | ### Why Customers Choose Us |
| 40 | (Specific differentiators with proof points) |
| 41 | **[Differentiator 1]:** [Proof point — customer outcome or capability] |
| 42 | **[Differentiator 2]:** [Proof point] |
| 43 | |
| 44 | |
| 45 | |
| 46 | ### Objection Responses |
| 47 | |
| 48 | **"[Competitor] is cheaper"** |
| 49 | "You are right their list price is lower. What our customers find is [specific TCO difference]. [Customer] saw [result]. Should we explore total cost of ownership?" |
| 50 | |
| 51 | **"We already use [Competitor]"** |
| 52 | "That is helpful. What is working well? [Listen] And what is one thing you wish was better?" |
| 53 | |
| 54 | **"[Competitor] has [feature] you do not"** |
| 55 | "You are right. What problem are you solving with that feature? [Listen] Here is how our customers solve that..." |
| 56 | |
| 57 | |
| 58 | |
| 59 | ### Landmines to Plant |
| 60 | "How do you currently handle [area where competitor is weak]?" |
| 61 | "What happens when you need to [scenario competitor struggles with]?" |
| 62 | |
| 63 | |
| 64 | |
| 65 | ### Traps to Avoid |
| 66 | Never badmouth [Competitor] directly |
| 67 | Do not lead with features — lead with the prospect problem |
| 68 | Do not claim you do everything better — be specific about where you win |
| 69 | |
| 70 | |
| 71 | |
| 72 | ### When We Win / When We Lose |
| 73 | We win when: [Scenario — e.g. customer prioritises outcome over price] |
| 74 | We lose when: [Honest scenario — e.g. primary driver is lowest upfront cost] |
| 75 | |
| 76 | ## Quality Checks |
| 77 | |
| 78 | [ ] Competitor strengths are listed honestly (not minimised) |
| 79 | [ ] Differentiators have proof points (not just claims) |
| 80 | [ ] Objection responses are conversational (not scripted-sounding) |
| 81 | [ ] Landmine questions are natural and non-confrontational |
| 82 | [ ] "When we lose" is included and honest |
| 83 | [ ] Battlecard has a review date |
| 84 | |
| 85 | ## Example Trigger Phrases |
| 86 | "Build a battlecard against [competitor]" |
| 87 | "Create a competitive cheat sheet for [competitor]" |
| 88 | "Write objection handling for [competitor] comparisons" |
| 89 | |
| 90 | ## Anti-Patterns |
| 91 | |
| 92 | [ ] Do not minimise or ignore genuine competitor strengths — sales reps who encounter them unprepared lose credibility |
| 93 | [ ] Do not write differentiators without proof points — a claim without evidence is marketing, not a battlecard |
| 94 | [ ] Do not make the battlecard exhaustive — it is a one-page cheat sheet, not a full competitive analysis |
| 95 | [ ] Do not include a "When we lose" section that is dishonestly optimistic — honest loss scenarios build rep trust |
| 96 | [ ] Do not skip the review date — an outdated battlecard with wrong information is worse than no battlecard |
| 97 |
Details
- Updated
- Sep 23, 2026
- License
- MIT
- Stars on the repo
- ★ 1,395
- Checked
- Source
- mohitagw15856/pm-claude-skills ↗
- Creator
- mohitagw15856 · 193 listings
Made with sales-battlecard
Sales Battlecard Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Sales Battlecard Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Similar skills
See all →
SkillEstimate the intrinsic value of a public company using DCFCompany valuation
himself65/finance-skills · by himself65Estimate the intrinsic value of a public company using DCF, relative (peer multiple) and sum-of-parts (SOTP) methods, then triangulate to an implied share price with upside/downside versus the current market price. Use this skill whenever the user asks: what is AAPL worth", "valuation of NVDA", "fair value of TSLA", "intrinsic value", DCF for MSFT", "build a DCF", "discounted cash flow", "WACC", "terminal value", implied share price", "upside to fair value", "is X overvalued/undervalued", relative valuation", "peer comparison valuation", "EV/EBITDA target", "SOTP", sum of the parts", "how much is [company] worth", "price target from fundamentals", value this company", or any ticker in the context of computing intrinsic or relative valuation. Default to running ALL three methods (DCF + relative + SOTP-if-applicable) and presenting a blended implied price with a sensitivity table. Do not answer valuation questions from memory — always run the workflow.★ 3.3k GitHub stars
SkillFind keywords a competitor ranks for that the user's siteCompetitor gap
Ryze-AI-Adgent/open-seo-mcp-skills · by Ryze-AI-AdgentFind keywords a competitor ranks for that the user's site doesn't — the content gap, prioritized by volume and winnability. Use when asked "what does competitor.com rank for", "keyword gap vs X", "steal competitor keywords", or "why do they outrank us".★ 3.1k GitHub stars
SkillMine the highest-converting ad angles from customer reviewsAd angle miner
gooseworks-ai/goose-skills · by gooseworks-aiMine the highest-converting ad angles from customer reviews, Reddit complaints, support tickets, and competitor ads. Extracts actual pain language, competitor weaknesses, and outcome phrases that real buyers use. Outputs a ranked angle bank with proof quotes and recommended ad formats per angle.★ 1.2k GitHub stars
SkillAnalyze competitor content coverageCompetitor content intelligence
sandbaseai/sandbase-skills · by sandbaseaiAnalyze competitor content coverage and uncover differentiated content opportunities using web search, page extraction, and DataForSEO content analysis. Use when asked for competitor content research, editorial gap analysis, content brief inputs, or topic whitespace.★ 203 GitHub stars
SkillCreates competitive battlecards for sales deal conversations
growthack88/growth-marketing-os · by growthack88Creates competitive battlecards for sales deal conversations. Produces win themes, landmines to plant, objection handlers, and competitive positioning per competitor. Outputs a structured markdown battlecard with quick-reference sections for live sales calls. Depends on competitor-research for competitive intelligence and consumes product-messaging, win-loss-analysis, and positioning for framing. Feeds into sales-deck, outreach-emails, and demo-script. Triggered by "battlecard", "competitive intel", "win against [competitor]", or "how do we beat [competitor]".★ 117 GitHub stars
SkillRead your X audience and niche from real dataX audience insights
sergebulaev/x-skills · by sergebulaevRead your X (Twitter) audience and niche from real data. Pull a handle's recent tweets (yours or a competitor's) with likes, replies, and views, see which formats and hooks are working, read the repliers on a tweet (X gates likers, so repliers are the signal), and scan a niche query for top tweets. Powered by Apify, no login. Triggers on "analyze my tweets", "what is working on X", "read the replies", "competitor tweets", "who is engaging". Not for writing a tweet (use x-post-writer).★ 95 GitHub starsMore from mohitagw15856
SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skill
mohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub stars
SkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub stars
SkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub stars
SkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub stars
SkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub stars
SkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars