ferdinandobons/startup-skill / startup-competitors
startup-competitors
VerifiedDeep competitive intelligence for any market. Analyzes competitors' products, pricing, customer sentiment, GTM strategy, and growth signals using real web data. Produces battle cards, pricing landscape, and feature matrix. Use when the user wants to understand their competitive landscape, analyze competitors, compare products in a market, or research who they're competing against. Triggers for "who are my competitors", "competitive analysis", "competitor research", "battle cards", "pricing comparison", "competitor pricing", "market players", "competitive intelligence", "competitive landscape", "who else is in this space", "competitive moat", or any request to profile, compare, or map competitors in a category. Works standalone — no prior startup-design session needed.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.2 KB |
| references/honesty-protocol.md | markdown | 4.8 KB |
| references/research-principles.md | markdown | 2.8 KB |
| references/research-scaling.md | markdown | 4.3 KB |
| references/research-synthesis.md | markdown | 8.5 KB |
| references/research-wave-1-profiles-pricing.md | markdown | 6.8 KB |
| references/research-wave-2-sentiment-mining.md | markdown | 6.8 KB |
| references/research-wave-3-gtm-signals.md | markdown | 7.2 KB |
| references/verification-agent.md | markdown | 5.1 KB |
references/research-synthesis.md
View on GitHub# Synthesis & Battle Cards
After ALL waves complete (6 agents), synthesize the raw findings into polished deliverables. This step creates the real analytical value — it connects dots across data sources to surface opportunities that individual research pieces can't reveal on their own.
## Synthesis Protocol
### Before Writing
1. Read ALL raw files in `{project-name}/raw/` before writing anything
2. Look for patterns across sources — what themes repeat?
3. Identify contradictions between sources and explain which you trust more
4. Connect the dots: pricing gaps + customer complaints + hiring signals = opportunities
### Cross-Wave Connections to Look For
These are the high-value insights that come from combining data:
- **Complaint + Pricing = Opportunity:** Customers complain about a feature AND the competitor charges a premium for it → undercut with better value
- **Hiring + Product Direction = Threat:** Competitor hiring AI engineers + recent AI mentions in changelog → they're coming for that space
- **Churn Signal + Switching Cost = Wedge:** People want to leave but data portability is hard → build easy migration as a differentiator
- **Content Gap + Search Volume = Quick Win:** Nobody ranks for a high-volume term → own it early
- **Review Pattern + Missing Feature = MVP Feature:** Multiple competitors lack something customers want → build it first
- **Funding + Team Size = Reality Check:** Well-funded competitor with 100+ engineers → don't compete on features, compete on focus
### Confidence Rating
Rate every major claim:
- **High:** Multiple Tier 1/2 sources agree, recent data
- **Medium:** Some evidence but gaps, or sources partially disagree
- **Low:** Limited data, mostly inferred, or data older than 12 months
---
## Output File: competitors-report.md
Structure:
```markdown
# Competitive Intelligence Report: {market/product}
*Skill: startup-competitors | Generated: {date}*
## Executive Summary
{5 sentences max: market concentration, key finding, biggest opportunity, biggest risk, overall assessment}
## Market Concentration
- **Structure:** fragmented / consolidating / dominated
- **Number of active players:** {count}
- **Funding concentration:** {is money flowing in or drying up?}
- **Entry barriers:** low / medium / high — {why}
## Key Players at a Glance
| Competitor | Stage | Funding | Strength | Weakness | Threat |
|-----------|-------|---------|----------|----------|--------|
| ... | ... | ... | ... | ... | H/M/L |
## Adjacent Solutions & Substitutes
{Broader platforms, manual alternatives, and tools from neighboring categories that compete for the same budget or job. Include: what job they solve, why buyers consider them, and how they compare to direct competitors.}
## Strategic Opportunities
For each opportunity:
### Opportunity: {name}
- **What:** {description}
- **Evidence:** {data points from research}
- **Confidence:** High / Medium / Low
- **How to exploit:** {specific recommendation}
## Strategic Risks
For each risk:
### Risk: {name}
- **What:** {description}
- **Evidence:** {data points}
- **Severity:** High / Medium / Low
- **Mitigation:** {how to protect against it}
## Competitive Moat Assessment
Evaluate the market on 5 moat dimensions:
| Moat Type | Present in Market? | Who Has It | Strength |
|----------|-------------------|-----------|----------|
| Network effects | yes / no | {who} | strong / weak |
| Switching costs | yes / no | {who} | strong / weak |
| Data moat | yes / no | {who} | strong / weak |
| Brand/trust | yes / no | {who} | strong / weak |
| Economies of scale | yes / no | {who} | strong / weak |
{Paragraph explaining what this means for a new entrant}
## Data Gaps & Research Limitations
Aggregate all data gaps from raw research files into a single section. For each gap:
- What data is missing
- Why it matters for decision-making
- How to fill it (specific actions the founder can take)
This section is mandatory — every competitive analysis has blind spots. Being explicit about them builds trust and prevents false confidence.
## Red Flags
- {flag 1 — things that should worry the founder}
- {flag 2}
## Yellow Flags
- {flag 1 — things to watch}
- {flag 2}
```
---
## Output File: competitive-matrix.md
```markdown
# Competitive Feature Matrix: {market}
## Feature Comparison
| Feature | {Your Product} | {Comp 1} | {Comp 2} | {Comp 3} | {Comp 4} |
|---------|---------------|----------|----------|----------|----------|
| {feature 1} | {rating} | {rating} | ... | ... | ... |
| {feature 2} | ... | ... | ... | ... | ... |
Rating scale: Strong / Adequate / Weak / Missing / Unknown
## Gap Analysis
Features where no competitor excels (all Weak or Missing):
- {gap 1} — {opportunity implication}
- {gap 2} — {opportunity implication}
## Differentiation Opportunities
Based on the matrix, the clearest paths to differentiation:
1. {opportunity — what to build and why}
2. {opportunity}
3. {opportunity}
```
---
## Output File: pricing-landscape.md
```markdown
# Pricing Landscape: {market}
## Market Pricing Overview
- **Dominant value metric:** {what most charge for}
- **Price range:** {lowest — highest for comparable tiers}
- **Median price point:** {for standard tier}
- **Free tier prevalence:** {X of Y competitors offer free}
## Tier-by-Tier Comparison
| | {Comp 1} | {Comp 2} | {Comp 3} | {Comp 4} |
|---|----------|----------|----------|----------|
| Free tier | {what's included} | ... | ... | ... |
| Entry tier | ${price} — {limits} | ... | ... | ... |
| Mid tier | ${price} — {limits} | ... | ... | ... |
| Top tier | ${price} — {limits} | ... | ... | ... |
| Enterprise | {custom?} | ... | ... | ... |
## Value Metric Analysis
| Competitor | Value Metric | Why It Works/Doesn't | Impact on Scaling |
|-----------|-------------|---------------------|-------------------|
| ... | per seat | {analysis} | {how costs grow} |
## Pricing Psychology in Use
| Tactic | Used By | How |
|--------|---------|-----|
| Anchoring | {who} | {details} |
| Decoy tier | {who} | {details} |
| Charm pricing | {who} | {details} |
| Annual lock-in | {who} | {discount %} |
## Switching Cost Matrix
| Competitor | Technical Cost | Contractual Cost | Emotional Cost | Overall |
|-----------|---------------|-----------------|----------------|---------|
| ... | H/M/L | H/M/L | H/M/L | H/M/L |
## Pricing Whitespace
{Where there's room to position on price — underserved segments, untried models, price points nobody occupies}
## Recommendations
- **If competing on price:** {strategy}
- **If competing on value:** {strategy}
- **If competing on model:** {alternative pricing approach that no competitor uses}
```
---
## Post-Synthesis Verification
After writing all deliverables and battle cards, run the Verification Agent protocol. See `references/verification-agent.md` for the full process. The verification step checks all deliverables for unlabeled claims, internal contradictions, confidence rating consistency, and startup-competitors-specific coherence (battle card vs. report consistency, matrix vs. profiles alignment, pricing landscape vs. profiles consistency, cross-deliverable opportunity/risk traceability).
---
## Output File: battle-cards/{competitor-name}.md
One battle card per competitor. Keep each to ONE page — these are reference tools for quick use, not deep research docs.
```markdown
# Battle Card: {Competitor Name}
*Last updated: {date}*
## At a Glance
- **What they do:** {one sentence}
- **Founded:** {year} | **Funding:** {total} | **Team:** ~{size}
- **Price:** {range} | **Model:** {value metric}
- **Best for:** {their ideal customer}
## Their Strengths (be honest)
- {strength 1 — with evidence}
- {strength 2}
- {strength 3}
## Their Weaknesses (your openings)
- {weakness 1 — with evidence from reviews/forums}
- {weakness 2}
- {weakness 3}
## How to Win Against Them
Specific talking points when a prospect is evaluating both:
- **When they say "{objection},"** respond: {counter with evidence}
- **When they say "{objection},"** respond: {counter}
- **Lead with:** {your strongest differentiator vs. this specific competitor}
## When They Win Over You
Be honest about when the competitor is the better choice:
- {scenario 1 — e.g., "Enterprise teams needing SSO and audit logs"}
- {scenario 2}
## Their Customers' Top Complaint
"{verbatim quote from review}" — {source}
This matters because: {strategic implication}
## Key Vulnerability
{The single biggest weakness you can exploit — with evidence}
## Churn Signals
Why their customers leave:
- {reason 1} — frequency: common / occasional
- {reason 2}
## Watch For
{What this competitor is likely to do next based on strategic signals}
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |