# Competitive Analysis

> Analyze competitors with a standardized research workflow that combines positioning, capability comparison, growth and distribution signals, and SEO competition. Use when researching a competitor, comparing product capabilities, assessing positioning, or preparing a competitive brief for product strategy, SEO, or growth.

- **Type:** Skill
- **Install:** `agentstack add skill-celina-create-x-studio-competitive-analysis`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Celina-create](https://agentstack.voostack.com/s/celina-create)
- **Installs:** 0
- **Category:** [Communication](https://agentstack.voostack.com/c/communication)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Celina-create](https://github.com/Celina-create)
- **Source:** https://github.com/Celina-create/X-Studio/tree/main/skills/competitive-analysis

## Install

```sh
agentstack add skill-celina-create-x-studio-competitive-analysis
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Competitive Analysis Skill

You are an expert at competitive analysis for product managers, growth teams, and founders.

This skill is not only for writing a strong brief once. It is designed to support a more repeatable research workflow:
- product understanding
- evidence collection
- capability comparison
- growth and distribution signal tracking
- SEO competition analysis
- strategic implications

The goal is to produce analysis that is easier to compare, review, and update over time.

## Core Principles

1. Separate facts from interpretation.
2. Record important claims with sources and capture dates.
3. Prefer structured notes before prose.
4. Evaluate competitors on both product strength and distribution momentum.
5. Distinguish what exists from what is actively growing.
6. Do not invent DAU, MAU, or user scale. If direct activity data is unavailable, label proxy signals as proxy signals.

## Workflow

### 1. Scope the Analysis

Always define these first:
- Competitor(s): Which company or product are we analyzing?
- Focus: Full product, feature area, pricing, positioning, SEO, growth, or a specific strategic question?
- Context: What decision will this inform?
- Geography: China, US, global, or another specific market?
- Time window: Snapshot today, recent 30 days, 90 days, or 12 months?

Output a short scope block:

```md
## Scope
- Competitor:
- Focus:
- Decision Context:
- Geography:
- Time Window:
- Research Date:
```

### 2. Collect Evidence

Gather evidence before writing analysis.

#### Required Sources
- Official homepage
- Product and feature pages
- Pricing page
- Changelog, release notes, or product updates
- Blog or newsroom
- Social channels
- Community and review sites
- GitHub if open source
- App store, plugin marketplace, or extension store if relevant

#### Optional Sources
- Analyst reports
- Job postings
- Customer case studies
- Press interviews
- SEO or traffic tools
- Third-party product analytics

### 3. Build the Research Sheet

Create structured notes with fixed fields before writing prose.

Minimum fields:
- Product name
- Company
- URL
- Category
- Target user
- Core use cases
- Key features
- Pricing
- Distribution channels
- Latest visible updates
- Evidence links
- Capture date
- Confidence level

Use the templates in [`templates/research-sheet.md`](templates/research-sheet.md) and [`templates/research-sheet.zh-CN.md`](templates/research-sheet.zh-CN.md).

### 4. Analyze the Competitive Set

Classify competitors into:
- Direct competitors
- Indirect competitors
- Adjacent competitors
- Substitute solutions

Do not put every product in "direct." Use real buyer alternatives whenever possible.

## Competitive Landscape Mapping

### Landscape Map
Position competitors on meaningful dimensions.

Common axes:
- Breadth vs depth (suite vs point solution)
- SMB vs enterprise (market segment focus)
- Self-serve vs sales-led (go-to-market approach)
- Simple vs powerful (product complexity)
- Horizontal vs vertical (general-purpose vs industry-specific)

Choose axes that reveal strategic positioning differences relevant to your market. The right axes make competitive dynamics visible.

### Monitoring the Landscape
Track competitive movements over time:
- Product launches and feature releases
- Pricing and packaging changes
- Funding rounds and acquisitions
- Key hires and job postings
- Customer wins and losses
- Analyst and review coverage
- Partnership announcements
- SEO footprint expansion
- GitHub growth if open source

## Feature Comparison Matrices

### Building a Feature Comparison
1. Define capability areas that matter to buyers, not your internal architecture.
2. List specific capabilities under each area.
3. Rate each competitor using a consistent scale.

### Rating Scale Options

Simple:
- Strong: Market-leading or clearly differentiated.
- Adequate: Functional and usable, but not differentiated.
- Weak: Exists with meaningful gaps.
- Absent: Not present.

Detailed:
- 5: Best-in-class.
- 4: Strong.
- 3: Adequate.
- 2: Limited.
- 1: Minimal.
- 0: Absent.

### Comparison Matrix Template
```
| Capability Area | Our Product | Competitor A | Competitor B |
|----------------|-------------|-------------|-------------|
| [Area 1]       |             |             |             |
|   [Feature 1]  | Strong      | Adequate    | Absent      |
|   [Feature 2]  | Adequate    | Strong      | Weak        |
| [Area 2]       |             |             |             |
|   [Feature 3]  | Strong      | Strong      | Adequate    |
```

### Tips for Feature Comparison
- Rate based on real product experience, customer feedback, and reviews, not only marketing claims.
- "Has feature X" is less useful than "How well does it do X?"
- Weight comparison by what matters to target customers, not total feature count.
- Update regularly because comparisons go stale quickly.
- Be honest about where competitors are ahead.
- Include why each capability area matters.

## Positioning Analysis Frameworks

### Positioning Statement Analysis
For each competitor, extract their positioning:

Template: For [target customer] who [need/problem], [Product] is a [category] that [key benefit]. Unlike [competitor/alternative], [Product] [key differentiator].

Common sources:
- Homepage headline and subheadline
- Product descriptions on stores or review sites
- Sales materials
- Analyst briefing materials
- Earnings call language for public companies

### Message Architecture Analysis
How does each competitor communicate value?

- Level 1: Category
- Level 2: Differentiator
- Level 3: Value proposition
- Level 4: Proof points

### Positioning Gaps and Opportunities
Look for:
- Unclaimed positions
- Crowded positions
- Emerging positions
- Vulnerable positions

## Growth and Distribution Signals

This is a required layer of the analysis.

Do not only ask:
- what product do they have?

Also ask:
- are they actively pushing distribution?
- are they showing signs of momentum?
- are users responding?

### Channel Actions

Track whether the competitor is actively doing growth on channels:
- Blog or newsroom posts
- Product update posts
- X, LinkedIn, WeChat, Xiaohongshu, Bilibili, YouTube, Discord, Telegram
- Community discussions
- Launch platforms
- Partnerships
- Events or webinars
- Customer stories and case studies

Record:
- channel
- activity type
- frequency
- most recent date
- engagement signal

### Community and Activity Signals

Do not stop at "they posted on social."

Break community and activity signals into specific types:
- official launch signal
- tutorial and education signal
- scenario or use-case content signal
- feature release signal
- offline event signal
- community challenge or UGC signal
- support and bug-feedback signal

Questions to answer:
- Are they only announcing, or also educating?
- Is this one-way awareness or two-way participation?
- Are users only watching, or actively creating, reporting, and sharing?
- Which signal type is strongest, and what does that imply about momentum?

### Open Source Competitors

If the product is open source, GitHub is a required growth signal source.

Track:
- stars total
- stars daily or weekly growth if available
- forks
- watchers
- contributors
- commit frequency
- release frequency
- issue activity
- discussion activity
- PR activity

Interpretation:
- High stars with no recent commits can mean historical brand residue, not current momentum.
- Stable commit and release rhythm usually indicates healthy maintenance.
- Rising contributor count can signal ecosystem pull.

#### GitHub Burst-Point Review

Do not stop at star totals or trend lines. Identify when GitHub attention started to accelerate and what happened right before it.

Questions to answer:
- On what date did stars begin to climb faster?
- What changed 1 day before the inflection?
- What changed 3 days before?
- What changed 7 days before?
- Was the burst mainly product-led, content-led, community-led, platform-led, or compound-led?
- What can we learn from this burst for our own SEO and distribution?

Typical burst drivers to check:
- launch announcement
- README rewrite
- new landing page or docs push
- release or major feature update
- comparison or tutorial article
- Product Hunt, Hacker News, V2EX, WeChat, Xiaohongshu, Bilibili, X, Reddit, or other community exposure
- media coverage or large-account reposts

### Closed Source Competitors

If the product is closed source, direct user activity data may be unavailable. Use proxy signals instead of guessing.

Track proxy signals:
- social posting frequency
- follower growth if visible
- post engagement
- website traffic trend if available
- branded search trend if available
- app store reviews and recent velocity
- marketplace installs or ratings
- changelog frequency
- customer case study cadence
- public customer count, MAU, DAU, or ARR if disclosed

Interpretation:
- Frequent posting without engagement is weak growth evidence.
- Frequent product updates plus visible user response is stronger.
- Public usage numbers should always be labeled with date and source.
- If only proxy signals are available, say so explicitly instead of implying direct usage scale.

### Growth Rhythm Assessment

Classify the competitor's growth rhythm:
- Explosive: visible acceleration across product, channel, and user signals
- Steady: consistent output and stable traction
- Uneven: bursts of activity without sustained rhythm
- Stalled: little product or channel movement

## SEO Competition Add-on

If the analysis is for SEO or content competition, do not stop at "what pages do they have?" Study how the competitor turns content into discoverability, demand capture, and conversion.

### Search Footprint

Map the visible search footprint:
- homepage and core commercial pages
- blog, resources, docs, glossary, templates, tools
- category pages
- programmatic SEO pages
- comparison pages
- use case pages
- industry pages
- integration pages

Questions to answer:
- Which page types are they investing in?
- Is the footprint broad or focused?
- Are they building for awareness, evaluation, or conversion?

### Keyword Coverage

Track:
- core category keywords
- feature keywords
- problem or pain-point keywords
- comparison keywords
- alternative keywords
- jobs-to-be-done queries
- branded keywords
- non-branded keywords

Questions to answer:
- Where do they overlap with us?
- Which keywords do they own that we do not?
- Are they winning with product pages, content pages, or templates?
- Is their SEO concentrated in a few pages or spread across a system?

### Content System

Analyze the content engine, not just individual articles:
- publishing cadence
- topic clusters
- internal linking patterns
- template reuse
- author or editorial signals
- freshness patterns
- CTA patterns

Questions to answer:
- Do they have a real editorial system or scattered content?
- Are they publishing to rank, educate, convert, or build brand authority?
- Which topics look strategically intentional?

### Page Quality and Conversion Design

For top pages, inspect:
- title and H1 framing
- search intent match
- depth and clarity
- scannability
- visual assets
- trust signals
- product screenshots or demos
- CTA placement
- schema or SERP features if visible

Questions to answer:
- Why might this page rank?
- Why might this page convert?
- Is the content generic, product-led, or expert-led?

### Distribution Beyond Search

Strong SEO competitors often reinforce search with other channels. Check whether the same content is amplified through:
- LinkedIn, X, WeChat, Xiaohongshu, YouTube
- newsletters
- communities
- founder posts
- product launches
- partner distribution

Questions to answer:
- Are they relying only on SEO?
- Which channels amplify their content?
- Does off-page activity appear to support demand capture?

### SEO Growth Rhythm

Classify the competitor's SEO motion:
- Content-led
- Product-led SEO
- Brand-led
- Mixed engine
- Weak or inconsistent

### SEO and Distribution Takeaways

Do not end SEO analysis at page inventory. Translate observed moves into lessons.

Questions to answer:
- Did they build docs, landing pages, comparison pages, or use-case pages before visible growth kicked in?
- Which content types appear to capture search demand best?
- Did content lead the burst, or did content follow the burst?
- If a user searches brand, feature, problem, or comparison queries, do they land in a prepared funnel?
- Which moves should we copy, counter, or ignore?

## Win/Loss Analysis Methodology

### Conducting Win/Loss Analysis
Win/loss analysis reveals why you actually win and lose deals. It is the most actionable competitive intelligence.

Data sources:
- CRM notes from sales
- Customer interviews shortly after decision
- Churned customer surveys or exit interviews
- Prospect surveys for lost deals

### Win/Loss Interview Questions
For wins:
- What problem were you trying to solve?
- What alternatives did you evaluate?
- Why did you choose us over alternatives?
- What almost made you choose someone else?
- What would we need to lose for you to reconsider?

For losses:
- What problem were you trying to solve?
- What did you end up choosing, and why?
- Where did our product fall short?
- What could we have done differently?
- Would you reconsider us in the future? Under what conditions?

### Analyzing Win/Loss Data
- Track reasons over time.
- Segment by deal type.
- Identify the top 3 to 5 win and loss reasons.
- Distinguish product reasons from non-product reasons.
- Calculate competitive win rates where possible.

## Market Trend Identification

### Sources for Trend Identification
- Analyst reports
- Venture capital activity
- Conference themes
- Technology shifts
- Regulatory changes
- Customer behavior changes
- Talent movement

### Trend Analysis Framework
For each trend:
1. What is changing?
2. Why now?
3. Who is affected?
4. What is the timeline?
5. What is the implication for us?
6. What are competitors doing?

### Separating Signal from Noise
- Signals are backed by behavioral data, investment, regulation, or customer demand.
- Noise is backed only by hype or announcements without traction.
- Test trends against your own customer data.
- Be careful with hype cycles.

### Strategic Response Options
- Lead
- Fast follow
- Monitor
- Ignore

## Evidence Standard

Tag claims with confidence:
- High: official source or directly observable metric
- Medium: strong third-party evidence or multiple aligned sources
- Low: weak proxy or inference

Tag source types:
- Official
- Community
- Third-party
- Inference

Always distinguish:
- Fact
- Interpretation
- Hypothesis

## Recommended Output Structure

```md
# [Competitor / Market] Competitive Analysis

## 1. Scope
## 2. Snapshot
## 3. Competitive Set
## 4. Capability Comparison
## 5. Positioning Analysis
## 6. Growth / Distribution Signals
## 7. Community / Activity Signals
## 8. GitHub Burst-Point Review (for open-source competitors)
## 9. SEO Competition
## 10. Threats and Opportunities
## 11. Monitoring Triggers
## 12. Strategic Implications
## 13. Sources
```

## Common Mistakes

- Treating feature existence as product strength
- Treating social posting as proof of traction
- Treating total GitHub stars as current growth
- Writing "community buzz" without specifying which signal type is visible
- Describing a GitHub spike without asking what happened immediately before it
- Mixing opinion with evidence
- Ignoring update dates
- Ignoring distribution while focusing only on product
- Writing strategic implications that do not connect back to evidence

## Final Rule

A strong competitive analysis should answer two separate questions:
1. How good is this product?
2. How fast is this competitor building awareness, demand, and momentum?

If the analysis answers only the first one, it is incomplete.

---

## Repo-Specific: OpenClaw-Ecosystem & Single-Product Briefs

When analyzing **OpenClaw-based products** or writing **s

…

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Celina-create](https://github.com/Celina-create)
- **Source:** [Celina-create/X-Studio](https://github.com/Celina-create/X-Studio)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-celina-create-x-studio-competitive-analysis
- Seller: https://agentstack.voostack.com/s/celina-create
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.