domains / marketing / competitor-analysis / competitor-analysis
The four copies share the name and the broad goal of analyzing competitors, but they are materially different procedures for different surfaces and toolchains. phuryn is a generic product-market competitive brief (5 direct competitors, positioning, pricing, differentiation). aaron-he-zhu is an SEO/GEO benchmark (keywords, backlinks, traffic share, AI citations, Immediate/Short-term/Long-term plan, memory handoff). appeeky is App Store/ASO-specific (App IDs, metadata, screenshots, ratings, monetization). browserbase is a tool-bound pipeline that requires BROWSERBASE_API_KEY and the browse CLI, auto-discovers competitors, and compiles an HTML report with a matrix and mentions feed. No single copy is the procedure the others reproduce; each contains steps and constraints the others lack, so crowning one would hide real alternatives.
| Repository | Path |
|---|---|
| phuryn/pm-skills | pm-market-research/skills/competitor-analysis/SKILL.md |
| aaron-he-zhu/aaron-marketing-skills | seo-geo/survey/competitor-analysis/SKILL.md |
| appeeky/aso-skills | skills/competitor-analysis/SKILL.md |
| browserbase/skills | skills/competitor-analysis/SKILL.md |
| Role | Repository | Path |
|---|---|---|
| peer | phuryn/pm-skills | pm-market-research/skills/competitor-analysis/SKILL.md |
| peer | aaron-he-zhu/aaron-marketing-skills | seo-geo/survey/competitor-analysis/SKILL.md |
| peer | appeeky/aso-skills | skills/competitor-analysis/SKILL.md |
| peer | browserbase/skills | skills/competitor-analysis/SKILL.md |
| inferior | sickn33/agentic-awesome-skills | plugins/agentic-awesome-skills-claude/skills/competitor-analysis/SKILL.md |
| adapter | sickn33/agentic-awesome-skills | skills/competitor-analysis/SKILL.md |
# Competitor Analysis
Analyze competitors for the user's product, app, or website. Choose the lane that matches the user's context, then follow the steps below.
## 1. Determine Scope and Lane
- Ask for the user's product/company, target market or country, and any known competitor names or URLs.
- If the user is doing App Store optimization, use the ASO lane. If the user is doing SEO/GEO, use the SEO lane. If the user wants a general product-market brief, use the Product lane. If the user has Browserbase credentials and wants an automated HTML report, use the Browserbase lane.
- If the user does not know their competitors, help identify them:
- Product: web search for direct competitors in the market segment.
- SEO: infer from target keywords or SERP analysis.
- ASO: category chart, keyword overlap, Apple's "You Might Also Like," or user perception.
- Browserbase: use the discovery pipeline (alternatives, precise category, comparison-page graph).
- Recommend analyzing 3-5 competitors: 2 direct, 1-2 aspirational, 1 emerging.
## 2. Gather Data
- Product lane: research each competitor's positioning, features, pricing, go-to-market, funding, and customer feedback. Use web search and any user-provided data.
- SEO lane: capture domain age, estimated traffic, domain authority, keyword rankings, content strategy, backlink profile, technical SEO, and AI citation presence. Label every metric Measured, User-provided, or Estimated.
- ASO lane: capture App ID, title, subtitle, description, screenshots, app preview video, icon, ratings, reviews, chart position, downloads, revenue, update frequency, and monetization model.
- Browserbase lane: use `browse cloud search` and `browse cloud fetch` to gather marketing surface, external signals, public benchmarks, and strategic diffs. Write one markdown file per competitor.
## 3. Analyze
- Product: assess strengths, weaknesses, pricing, competitive threats, and differentiation opportunities. Map unmet needs, feature/pricing/UX gaps, underserved segments, and channel opportunities.
- SEO: compare keyword rankings, content volume, backlink quality, technical SEO, and AI citation coverage. Identify keyword gaps, content recommendations, and linkable assets.
- ASO: compare metadata, creative strategy, ratings/reviews, growth signals, and monetization. Identify keyword gaps, creative edges, feature gaps, and market gaps.
- Browserbase: synthesize per-competitor deep dives, a side-by-side feature/pricing matrix, and a chronological mentions feed.
## 4. Output
- Product: Market Overview, Competitive Set Summary, per-competitor profiles (strengths, weaknesses, pricing, threats), Differentiation Opportunities, and Competitive Positioning Recommendation.
- SEO: Executive Summary, comparison table, CITE comparison, strengths to learn, weaknesses to exploit, keyword opportunities, content recommendations, and Immediate/Short-term/Long-term plan. Emit a handoff summary to memory/research/.
- ASO: Executive Summary, Competitive Position Map, Top Opportunities (Quick Win, Keyword Gap, Creative Edge, Feature Gap, Market Gap), and Threats to Monitor.
- Browserbase: HTML report with overview, per-competitor deep dives, matrix, and mentions views. Save to ~/Desktop/{company_slug}_competitors_{YYYY-MM-DD}/.
## 5. Quality Bar
- Every strength or weakness must tie to a labeled metric and a named competitor.
- Distinguish direct competitors from indirect alternatives.
- Validate insights across multiple sources.
- Flag emerging competitors and long-term competitive dynamics.
## Conflicts
- phuryn/pm-skills specifies exactly 5 direct competitors and a strategic product brief; aaron-he-zhu specifies 3-5 competitors with SEO/GEO metrics and an action plan; appeeky/aso-skills requires App IDs and ASO-specific comparisons; browserbase/skills requires BROWSERBASE_API_KEY and outputs an HTML report. These are different procedures for different surfaces and cannot be averaged into a single step.