mohitagw15856/sales-battlecard
skills/sales-battlecard/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills sales-battlecardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 12:32 PM11.6s1 file scanned
SKILL.md
- 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
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"
Related Skills
mohitagw15856/competitor-signal-tracker
development
VerifiedTrustedCommunity
Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners.
951SKILL.mdUpdated Apr 21, 2026
mohitagw15856/community-management-playbook
development
VerifiedTrustedCommunity
Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
946SKILL.mdUpdated May 28, 2026
mohitagw15856/claude-superpowers
development
VerifiedTrustedCommunity
Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.
946SKILL.mdUpdated May 28, 2026
mohitagw15856/aeo-optimizer
development
VerifiedTrustedCommunity
Optimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
946SKILL.mdUpdated May 28, 2026