pkking/competitive-battlecard
dotfiles/dot_config/skillshare/skills/competitive-battlecard/SKILL.md
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'
testing
Updated Apr 27, 2026
$ install --global
skillsauthnpx skillsauth add pkking/dotfiles competitive-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 27, 2026, 9:46 AM30.0s2 files scanned
SKILL.md
- name:
- competitive-battlecard
- description:
- Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'
Competitive Battlecard
Create a concise, sales-ready battlecard for use against a specific competitor.
Context
You are creating a competitive battlecard for $ARGUMENTS.
Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.
Instructions
-
Research the competitor (use web search):
- Current product offerings and features
- Pricing tiers and model
- Target market and positioning
- Recent product launches or changes
- Known strengths and weaknesses
- Customer reviews and sentiment (G2, Capterra, Reddit)
-
Create the battlecard with these sections:
Company Overview
- Founded, HQ, funding/revenue (if public)
- Target market and ICP
- Positioning in one sentence
Quick Comparison
| Capability | Us | Them | Winner | |---|---|---|---| | [Feature area 1] | [Our approach] | [Their approach] | [Us/Them/Tie] | | [Feature area 2] | ... | ... | ... | | Pricing | ... | ... | ... | | Support | ... | ... | ... |
Where We Win
- [Advantage 1]: [Proof point or customer quote]
- [Advantage 2]: [Specific capability they lack]
- [Advantage 3]: [Better approach with reasoning]
Where They Win
- [Their strength 1]: [Our counter-positioning]
- [Their strength 2]: [How we mitigate this gap]
Common Objections & Responses
| Prospect Says | Respond With | |---|---| | "Competitor X has [feature]" | "[Our alternative approach and why it's better for them]" | | "They're cheaper" | "[Value framing: total cost of ownership, ROI, hidden costs]" | | "They're more established" | "[Our advantages: speed, innovation, focus, support]" |
Landmines to Plant
Questions to ask the prospect that highlight competitor weaknesses:
- "How important is [area where we excel] to your team?"
- "Have you evaluated [specific capability they lack]?"
Win/Loss Patterns
- We tend to win when: [pattern]
- We tend to lose when: [pattern]
- Key differentiator in competitive deals: [what tips the scale]
-
Keep it scannable: Sales reps need to reference this during calls. Use tables, bold text, and short bullets.
Save as markdown. Format for easy printing or sharing in Notion/Confluence.
Further Reading
- How to Design a Value Proposition Customers Can't Resist?
Related Skills
pkking/grill-me
testing
VerifiedTrustedCommunity
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
SKILL.mdUpdated Jun 5, 2026
pkking/find-skills
data-ai
VerifiedTrustedCommunity
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
SKILL.mdUpdated Jun 4, 2026
pkking/lfg
development
VerifiedTrustedCommunity
Run the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description; do not auto-route casual conversation here.
SKILL.mdUpdated May 9, 2026
pkking/ce-worktree
development
VerifiedTrustedCommunity
Create an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when `ce-work` or `ce-code-review` offers a worktree option.
SKILL.mdUpdated May 9, 2026