heyparsadev/claude-venture-plugin / venture/skills/competitors
competitors
VerifiedThis skill should be used when the user asks for competitor analysis, competitive landscape, battlecards, positioning maps, or "who else does this" — e.g. "analyze my competitors", "competitive analysis for X", "build a battlecard", "who are the alternatives", "تحلیل رقبا", "رقیبهای این محصول کیان", "رقبا رو بررسی کن", "بتلکارت بساز", "مقایسه با رقبا". Produces competitor profiles, a comparison matrix, positioning map, and battlecards in the venture workspace.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.2 KB |
| references/battlecard-template.md | markdown | 1.4 KB |
| references/profile-template.md | markdown | 1.9 KB |
references/battlecard-template.md
View on GitHub# Battlecard Template
One page per key competitor. Audience: whoever sells/pitches against them (founder, sales, or the consulting client). Keep it brutally practical — this gets read 30 seconds before a call.
```markdown
# Battlecard: us vs <Competitor>
<date> · threat: <high/med/low>
## Them in one line
<what they are and who they're best for — honest, no strawman>
## Quick compare
| | Us | Them |
|---|---|---|
| Best for | | |
| Pricing | | |
| Key strength | | |
| Key weakness | | |
| Deal-breaker gap | | |
## When we win
<2–3 scenarios/customer profiles where we're genuinely the better choice — and the proof points to use>
## When we lose (be honest)
<scenarios where they're the better fit — qualify these out early instead of fighting>
## Their pitch against us — and the counter
- **They'll say:** "<likely objection>" → **Counter:** <response grounded in facts>
- **They'll say:** "<...>" → **Counter:** <...>
## Landmines to plant (fair, factual)
<questions a buyer should ask them that expose their real weaknesses —
e.g. "ask them what happens to your data if you cancel" — only verifiable ones>
## Objection handling
| Prospect says | Respond |
|---|---|
| "We already use <competitor>" | <switch-cost-aware response> |
| "<competitor> is cheaper" | <value reframe or honest concession> |
## Proof points
<our evidence: metrics, testimonials, case studies — only real ones; mark TBD if none yet>
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |