aiskillstore/marketplace / skills/aaron-he-zhu/competitor-analysis
competitor-analysis
VerifiedUse when the user asks to "analyze competitors" or "竞品分析"; benchmarks competitor keywords, content, backlinks, AI citations, and traffic share into strengths, weaknesses, and an action plan. Not for a pairwise topic-coverage gap map — use content-gap-analysis. 竞品分析/竞争对手
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| references/analysis-templates.md | markdown | 3.7 KB |
| references/battlecard-template.md | markdown | 4.1 KB |
| references/example-report.md | markdown | 2.2 KB |
| references/positioning-frameworks.md | markdown | 4.7 KB |
| skill-report.json | config | 34.8 KB |
references/positioning-frameworks.md
View on GitHub# Positioning Frameworks
Use these compact frameworks to map competitor positioning, find white space, and turn differentiation into defensible messaging.
## Positioning Statements
```text
Classic:
For [target audience], [brand] is the [category] that [key benefit] because [proof].
Extended:
For [audience] who [need], [brand] is the [category] that [functional benefit],
unlike [alternative], because [unique capability]. This matters because [outcome].
Before/After/Bridge:
Before: [painful current state]
After: [desired state]
Bridge: [product] makes this possible by [mechanism].
PAS:
Problem: [struggle]
Agitation: [why it matters now]
Solution: [different solution]
```
## Positioning Map
1. Choose buyer-relevant, independent axes.
2. Plot direct competitors, indirect alternatives, and your current position.
3. Identify white space, crowded clusters, and places where the axis itself is wrong.
4. Pick a position that is capability-aligned, underserved, and defensible.
| Axis Pair | X-Axis | Y-Axis |
|-----------|--------|--------|
| Value | Price low -> high | Capability basic -> advanced |
| UX | Complex -> simple | Limited -> powerful |
| Audience | SMB -> enterprise | Point solution -> platform |
| Innovation | Established -> new | Niche -> broad |
| Anti-Pattern | Fix |
|--------------|-----|
| Aspiration map | Plot current position, then roadmap desired position |
| Vanity axes | Validate axes with customer language |
| Direct-only competitors | Include indirect tools, services, spreadsheets, and status quo |
| Static map | Refresh quarterly or after major competitor launches |
## Category Strategy
| Strategy | Use When | Messaging Pattern | Main Risk |
|----------|----------|-------------------|-----------|
| Win existing category | Product is clearly better in a known frame | `The best [category] for [audience]` | Expensive head-to-head competition |
| Create sub-category | Differentiator deserves its own label | `The first [new sub-category]` | Market may not search for it |
| Create new category | Existing categories mislead buyers | `Introducing [new category]` | High education cost |
| Reframe category | Existing frame favors incumbents | `Stop thinking [old]. Start thinking [new].` | Confusion if proof is weak |
Decision rule: if SEO demand and buyer language already exist, prefer existing category or sub-category. Use new-category moves only when product reality cannot fit the old frame.
## Differentiation Audit
| Dimension | Your Approach | Competitor Approach | Strength | Defensibility |
|-----------|---------------|---------------------|----------|---------------|
| Core technology | [tech] | [their tech] | Weak/Med/Strong | Easy/Hard |
| Target audience | [audience] | [audience] | Weak/Med/Strong | Easy/Hard |
| Pricing model | [model] | [model] | Weak/Med/Strong | Easy/Hard |
| Data/network | [advantage] | [advantage] | Weak/Med/Strong | Easy/Hard |
| Methodology | [framework] | [framework] | Weak/Med/Strong | Easy/Hard |
**Only-we test**: "Only [company] [does X] because [unique reason]." If a competitor can credibly say it, it is not a durable differentiator.
```text
Differentiation message:
We're the only [category] that [unique capability],
which means [customer benefit],
so you can [desired outcome].
```
## Messaging Vulnerability Scan
| Vulnerability | Evidence | Counter |
|---------------|----------|---------|
| Promise-reality gap | Reviews, support complaints, churn comments | Proof of delivery, customer evidence |
| Specificity gap | Vague claims, no metrics | Specific metric for a specific audience |
| Audience mismatch | Enterprise copy for SMB pain, or reverse | Speak to ignored segment |
| Legacy positioning | Old category story no longer fits | Position against their outdated frame |
| Feature overload | Feature list without outcome | Lead with business outcome |
| Price opacity | Hidden fees, unclear TCO | Transparent pricing or TCO comparison |
## Counter-Positioning Patterns
| Pattern | Use When | Example Shape |
|---------|----------|---------------|
| Contrast | Incumbent has clear weakness | `Unlike [competitor], we [strength].` |
| Flanking | Competitor ignores valuable segment | `Built specifically for [segment].` |
| Reframing | Their strength creates downside | `[Feature] sounds good until [consequence].` |
| Elevation | Feature war is crowded | `What matters is [higher-level outcome].` |
| Specificity | Competitor is vague | `[metric] for [audience] in [timeframe].` |
## Combined Workflow
1. Map the category and competitor positions.
2. Choose category strategy.
3. Draft a positioning statement.
4. Run the differentiation audit and only-we test.
5. Identify messaging vulnerabilities.
6. Convert the result into battlecards.
7. Re-check quarterly.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |