Skip to main content
skill CX Codex

competitor-research · kostja94 — Claude Code skill: what it does, how to install

Competitor research skill for Claude Code that benchmarks market rivals. It triggers on requests concerning competitor keywords, content gaps, link overlap, substitutes, and search visibility.

MIT 1,400 installs ★ 1,129 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add kostja94/marketing-skills --skill competitor-research -a claude-code
Open on GitHub

What competitor-research does

Guides structured competitive discovery across direct rivals, indirect products, and manual workflow alternatives. The skill inspects migration portals, software directories, app stores, and search ad copy, verifying real product behavior before accepting parity claims.

Two distinct analytical perspectives are supported: a product view focusing on switching friction, and a marketing perspective mapping shared audience reach. It details targeted tactics such as search operator parsing with site:competitor.com alongside SERP overlap reviews to spot rank opportunities in positions 4 through 10.

While public pages and search engine results suffice for baseline research, comprehensive keyword overlap and backlink auditing rely on external data from services like Ahrefs or Semrush. For generating full editorial calendars, the workflow defers to the companion content-strategy skill.

What it helps with

  • identify market substitutes and direct competitors for a product
  • uncover content and keyword gaps against search leaders
  • map rival backlink targets for outreach campaigns
  • evaluate competitor positioning and user switching barriers

Example prompts for the agent

  • Run a competitor analysis for our project and list direct substitutes
  • Audit content gaps against our top SERP competitors
  • Inspect distribution listings and browser extensions of competing tools

How to install competitor-research

1Skills CLI (Vercel)

npx skills add kostja94/marketing-skills --skill competitor-research -a claude-code

2Manually: put the files in place

~/.claude/skills/competitor-research/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/competitor-research/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about competitor-research

How to install competitor-research in Claude Code?

Run npx skills add kostja94/marketing-skills --skill competitor-research -a claude-code. Alternatively, copy the skill definition into ~/.claude/skills/competitor-research/SKILL.md.

What does competitor-research do?

It directs the assistant through competitive intelligence workflows covering product positioning, SERP footprints, backlink profiles, and feature comparisons.

What is required to run deep keyword and backlink audits?

General positioning reviews work directly from public URLs and search queries. Deep link gap and keyword overlap tracking require data from external platforms like Semrush or Ahrefs.

Source text

SKILL.md · MIT
---
name: competitor-research
description: When the user wants to find competitors for a product or website, assess substitutes, or analyze competition for content, search visibility, backlinks or positioning. Also use when the user mentions "competitor analysis," "competitor research," "competitor keywords," "competitor backlinks," "link gap," "content gap," "competitor content," "competitive analysis," or "competitor comparison." For content roadmap, use content-strategy.
metadata:
  version: 2.0.0
---

# Competitor Research

Guides competitor research for SEO, content, backlinks, and positioning. Use when planning content, auditing articles, building links, or evaluating market position.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

For marketing engagements, lead with the content and distribution view. Use product comparisons to identify meaningful differences and claims the client can support. For a positioning or replacement question, lead with the product view. Use [research workflow](references/research-workflow.md) to select the evidence, follow discoveries and assemble the final report. The SEO and backlink methods below are optional modules selected by scope.

## Discover competitors and classify relationships

Start with the reference product or URL, market and user task. Inspect the product page to establish the input, outcome and intended user. Set the comparison unit (company, product, capability or feature). For an unknown site or ambiguous brand, verify identity before adding candidates.

Choose a product view for user choice, replacement and switching costs; choose a marketing/content view for who attracts the same audience or answers the same question. For a baseline study, maintain one register and derive both views.

1. Start with known products, manual alternatives and adjacent steps in the user workflow. Inspect navigation, templates, integrations, comparison, alternatives, migration and support pages. Identify unexpected pages and examine the action a user can take there.
2. For a promising finding, record the actual URL and what it demonstrates. Search the specific feature, user problem or output in the target market, then inspect at least one new candidate when attainable. Trace the chain from original page through query to new evidence. Stop at the agreed boundary or when new sources repeat existing tasks and relationships.
3. For each material candidate record the comparison unit and task, relationship (direct, indirect, manual substitute, upstream, downstream or platform), coverage (whole or partial, with scope), surface (product, search, community or other evidenced channel), source URL, date and confidence. Leave uncertain relationships pending. Vendor mentions establish leads; check the other product or independent task evidence before claiming substitutability. An import list establishes supported sources, not parity or market share.
4. Deliver the register, strongest discovery trail and open checks. Offer comparison pages for substantiated evaluation needs, alternatives pages for supported replacement tasks and migration pages for executable transfer paths. Hand keyword-research the source URL, observed action, inferred need and concrete seed when a finding warrants query validation.

### Search from a known brand and from a user task

- Search "[brand] alternatives". Capture the publisher, the reference product, named replacements and the job each claims to replace. Check both vendor comparison pages and third-party lists. Follow promising names to their official product or feature pages.
- Search the competitor brand and relevant branded variants in the target market. Inspect placements explicitly labeled as ads. Record query, locale, date, advertiser, visible destination and promoted benefit. An ad impression supports competition for that search opportunity; the advertiser's selected keyword, match type and spend remain unknown. If ads cannot be inspected, mark coverage pending. If an ad promises a different workflow, investigate that relationship separately.
- Search "best [specific feature or job]" and "best [tool] for [audience or constraint]". Extract products and the reasons for inclusion, then check the claimed capability at the source. Use the new feature or use case as the next query to discover specialist providers beyond familiar brands.

Keep the discovery surface distinct from the competitive relationship. Deduplicate products across ads, lists and alternative pages while retaining each independent source and what it establishes.

### Discover products through their distribution channels

Map the task to the device or host where the user performs it. For each relevant environment, inspect the native marketplace or in-product add-on catalog: mobile app stores, browser extensions, collaboration or CRM marketplaces, integration directories and connector/template galleries. Start with categories, collections, related apps, publisher portfolios and host recommendations as well as native search. Follow the tools and endpoints named by a connector into their own listings. For private or login-only catalogs use available authorized access or request a listing/export when needed; mark unchecked surfaces explicitly.

Record the store and locale, host, listing URL or stable ID, publisher, workflow step, inputs and outputs. Distinguish first-party features, standalone apps, extensions of known products, third-party connectors and recipes. Group multiple distribution listings under the same product while preserving channel-specific capabilities. A listing supports availability and stated scope; user reviews provide leads for use cases to verify. Record whether discovery used the native catalog or only a publicly indexed listing.

## Research Types

| Type | Purpose | Output |
|------|---------|--------|
| **Keyword/topic** | Topics competitors rank for; gaps | Keyword opportunities; content ideas |
| **Content** | Structure, length, gaps vs top rankers | Length target; H2 structure; content gaps |
| **Backlink** | Link profile; sites linking to competitors | Link gap; outreach targets |
| **Pricing** | Competitor pricing, positioning | Pricing context; differentiation |
| **SEO metrics** | Organic traffic, rankings vs competitors | Benchmark; opportunity areas |

## Competitor Keyword / Topic Analysis

| Method | Practice |
|--------|----------|
| **Reverse engineering** | Analyze competitor titles, H1, URL; identify topics they rank for |
| **SERP overlap** | Keywords with overlapping top-ranking pages → same cluster; #4–10 = opportunity |
| **site: operator** | `site:competitor.com` to see indexed pages |
| **Tool** | Ahrefs, Semrush—competitor keyword overlap, gap analysis |

**Output**: Keyword opportunities; topics competitors cover that you don't.

## Competitor Content Analysis

| Element | Check |
|---------|-------|
| **Word count** | Top 10 average; length target for your content |
| **H2 structure** | Topics covered; structure to adopt |
| **Content gaps** | What top rankers cover that you miss |
| **Keyword placement** | Primary keyword in title, H1, first 100 words |
| **Format** | Lists, tables, FAQ; match or improve |

**Use when**: Auditing or creating articles; see **article-page-generator** for Research Phase integration.

### Competitor Article Fetch Workflow (for Article Analysis)

When analyzing or auditing a single article, use this lightweight workflow to obtain competitor articles:

1. **Obtain URLs**: From the user, relevant Contextus competitor or content modules, or web search for `"[target keyword]"` to find top-ranking pages
2. **Fetch content**: Use mcp_web_fetch or WebSearch to fetch 2–3 top-ranking pages
3. **Analyze**: Word count, H2 structure, keyword placement, content gaps, CTA, schema
4. **Output**: Competitor URLs, brief structure comparison, content gaps, length target, keyword opportunities

**Output format**: Competitor URLs; word count and H2 structure per URL; content gaps vs your article; recommended length target; keyword opportunities (terms top rankers use that your article misses).

## Competitor Backlink Analysis

| Action | Purpose |
|--------|---------|
| **Compare profiles** | Your backlinks vs competitors |
| **Link gap** | Sites linking to competitors but not you |
| **Opportunity** | Outreach to those sites; content they might link to |

**Tools**: Ahrefs, Semrush—Link Intersect, competitor backlink reports. See **backlink-analysis**.

## Competitor Pricing

| Use | Practice |
|-----|----------|
| **Positioning** | Where you sit vs competitors |
| **Differentiation** | Value prop when price differs |
| **Alternatives pages** | Who to include; how to position |

See **pricing-strategy**, **alternatives-page-generator**.

## Data Sources

| Source | Use |
|--------|-----|
| **SimilarWeb** | Traffic, engagement, traffic sources by domain |
| **Ahrefs** | Competitor domains, backlinks, DR |
| **SEMrush** | Organic competitors, traffic share |
| **GA** | Referral traffic, acquisition by source |
| **PostHog** | Competitor feature usage (if tracked) |

## Report Workflow

1. **Parse** — Read Excel/CSV, infer domain, visits, traffic sources, etc. from headers
2. **Enrich** — Web search, visit competitor sites; read root `{project}.md` if present
3. **Build** — Structure data for report
4. **Generate** — Output report in chosen format

## Output Format

- **Competitors** identified
- **Research type** (keyword, content, backlink, pricing)
- **Findings** (gaps, opportunities, benchmarks)
- **Recommendations** (content to create, links to pursue, positioning)

### Report Structure Reference

| Section | Content |
|---------|---------|
| Executive Summary | Key findings (top 3), top 3 recommendations |
| Competitor Overview | Competitor, category, market position, key strength |
| Product Comparison | Feature/capability vs Us vs Competitors |
| SWOT Analysis | Our strengths/weaknesses/opportunities/threats; competitor deep dives |
| Marketing & Messaging | Value prop, target audience, key channels |
| Gaps & Opportunities | Gap, opportunity, priority |
| Prioritized Recommendations | Recommendation, impact, effort, owner |

## Related Skills

- **keyword-research**: Competitor reverse; keyword discovery
- **article-page-generator**: Competitor article analysis in Research Phase
- **content-strategy**: Competitor analysis for topic mapping
- **content-optimization**: Competitor length and structure as reference
- **backlink-analysis**: Competitor backlink comparison; link gap
- **seo-monitoring**: Competitive comparison; organic vs competitors
- **alternatives-page-generator**: Competitor selection; comparison framing
- **migration-page-generator**: Competitor migration paths
- **pricing-strategy**: Competitor pricing context
- **affiliate-marketing**: Find affiliates promoting competitors
- **directories**: Competitor info for directory submissions

© kostja94 · MIT · kostja94/marketing-skills

Similar skills

All skills for SEO and GEO →

competitor-research by other authors comes first.

competitor-research kostja94 Guides competitor research for SEO, content, backlinks, and positioning. It identifies keyword gaps and analyzes top-ranking articles before publishing. CX Codex +1 1,400installs competitor-research tubelab competitor-research — a Claude Code skill that finds YouTube channels competing for the same viewers and compares them with a target channel. It surfaces topics where rivals get stronger results. CX Codex +1 ★ 288repo stars competitor-analysis every-app competitor-analysis is a Claude Code skill that maps one competitor's organic footprint: keywords, backlinks, content themes, and gaps. Point it at a domain for an action plan. CX Codex +1 7,600installs seo-competitor rampstackco seo-competitor is a Claude Code skill that compares your site with competitors across search, content, backlinks, and technical foundations. It surfaces gaps and prioritizes them. CX Codex +1 309installs semrush-research OpenClaudia semrush-research pulls domain metrics, keyword difficulty, backlinks, and competitor search data via the SemRush API. Useful for running SEO intelligence without leaving the terminal. CX Codex +1 504installs competitor-profiling coreyhaines31 The competitor-profiling skill for Claude Code, Codex, and Cursor builds dated competitor profiles. Use it to examine rivals’ pricing, positioning, features, reviews, and SEO. CX Codex +1 107,300installs competitor-alternatives Alireza Rezvani competitor-alternatives creates competitor comparison and alternative pages for SEO and sales enablement across four distinct layout formats. CX Codex +1 600installs competitive-landscape every-app competitive-landscape — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode that maps SEO market leaders, their winning content themes, and gaps in keyword coverage. CX Codex +1 7,500installs

From the same set132

The whole set →
terms-page-generator terms-page-generator — a stub skill for building a Terms page. The rules moved to Pagina, and this entry only points you at page-builder. CX Codex +1 1,600installs legal-page-generator legal-page-generator — a stub skill: legal page construction moved to Pagina, and this entry only points at the replacement package. CX Codex +1 1,600installs brand-visual-generator brand-visual-generator is a Claude Code skill for defining, auditing, and applying a brand’s visual identity. It activates for work on typography, color palettes, design systems, frontend style, or branded slides. CX Codex +1 1,500installs conversion-optimization conversion-optimization guides conversion rate optimization, hypothesis design, and A/B test planning. Useful when users drop off during signups, checkout, or landing page visits. CX Codex +1 1,500installs robots-txt A skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that handles robots.txt configuration and auditing. CX Codex +1 1,400installs seo-strategy seo-strategy — a skill that plans SEO from scratch, audits an existing site and tells you what to do next. Useful when you don't know where to start. CX Codex +1 1,400installs schema-markup schema-markup generates Schema.org JSON-LD structured data for rich snippets and AI search engines. Helps match page content to supported search engine formats. CX Codex +1 1,400installs generative-engine-optimization generative-engine-optimization — a skill that walks through GEO and AEO strategy: how to get cited in Claude, Perplexity, AI Overviews and Copilot answers instead of only ranking. CX Codex +1 1,400installs

Project sponsors

Companies that keep this analytics open