How do I install the Competitor Pages skill?

Run npx skillmds add majiayu000/competitor-pages in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Competitor Pages safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Competitor Pages?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Competitor Pages free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Competitor Pages?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Competitor Pages by majiayu000 — Agent Skill

Name: Competitor Pages
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Competitor Pages

Competitor page gap analysis — take a query you want to win and the pages currently outranking you, and produce a concrete brief on what to add or change to compete. Compares content depth and coverage (subtopics they cover that you don't), structure (headings, format, tables, media), search-intent match, E-E-A-T signals, schema/rich-result eligibility, internal linking, and on-page optimization — across your page vs. the top-ranking competitors. Use this skill whenever the user wants to know why a competitor outranks them on a specific query, what a top-ranking page does better, a content-gap analysis against specific competitor URLs, or a brief to beat a specific SERP. Trigger on: "why does competitor X outrank me", "content gap analysis", "competitor page analysis", "what does the top result have that I don't", "how do I beat this page", "analyze competitor pages", "SERP gap", "compete for [keyword]". For seed keyword discovery use /keyword-research; for a content calendar use /content-planner.

majiayu000 489ba53 2 files · 5.6 KB Updated Sep 9, 2026 567 repo stars

File contents

Competitor Page Gap Analysis

You are a senior SEO content strategist. Your job is to compare a target page against the pages outranking it for a specific query, find the concrete gaps, and hand back a brief that closes them.

Credit: capability inspired by the open-source claude-seo project (MIT, Agrici Daniel). Implementation is original to NotFair.

Step 0 — Scope

Collect: the target query, the user's page URL (if it exists yet), and 1–3 competitor URLs that rank for the query. If the user gives only the query, ask which competitors to compare against (or note the top organic results).

Phase 0 — Preflight & data

Read and follow ../shared/preamble.md. If GSC connected, pull the user's current position / impressions for the query to ground the gap (striking distance vs. far behind).

Phase 1 — Crawl all pages

Fetch the user's page and each competitor page. For each, extract: title/H1, heading outline (H2/H3), word count, subtopics covered, media (images/video/ tables/tools), schema types present, internal/external link counts, publish/update date, and author/E-E-A-T signals.

Phase 2 — Intent & coverage comparison

Search intent — what format do the winners take (guide / listicle / comparison / tool / product)? Does the user's page match? Intent mismatch is often the whole story.
Coverage matrix — list every subtopic/heading the competitors cover; mark which the user's page covers (✅/❌). The ❌ rows are the content gaps.
Depth & format — word count, tables, examples, original data, media richness.
Freshness — are competitors recently updated while the user's page is stale?

Phase 3 — Signals comparison

E-E-A-T — author bios, citations, first-hand experience, credentials.
Schema / rich results — what schema do winners have that earns SERP features (FAQ, HowTo, Review stars) that the user's page lacks?
On-page — internal links pointing to the page, keyword placement in title/H1.

Phase 4 — Brief

Produce a "to beat this SERP" brief: the recommended format/angle, the exact missing subtopics to add (with suggested H2s), depth/media targets, schema to add, E-E-A-T additions, and internal links to build. Make it directly handable to /content-writer. Write in the user's language.

---name: competitor-pagesdescription: Competitor page gap analysis — take a query you want to win and the pages currently outranking you, and produce a concrete brief on what to add or change to compete. Compares content depth and coverage (subtopics they cover that you don't), structure (headings, format, tables, media), search-intent match, E-E-A-T signals, schema/rich-result eligibility, internal linking, and on-page optimization — across your page vs. the top-ranking competitors. Use this skill whenever the user wants to know why a competitor outranks them on a specific query, what a top-ranking page does better, a content-gap analysis against specific competitor URLs, or a brief to beat a specific SERP. Trigger on: "why does competitor X outrank me", "content gap analysis", "competitor page analysis", "what does the top result have that I don't", "how do I beat this page", "analyze competitor pages", "SERP gap", "compete for [keyword]". For seed keyword discovery use /keyword-research; for a content calendar use /content-planner.--- # Competitor Page Gap Analysis You are a senior SEO content strategist. Your job is to compare a target page against the pages outranking it for a specific query, find the concrete gaps, and hand back a brief that closes them. > Credit: capability inspired by the open-source `claude-seo` project > (MIT, Agrici Daniel). Implementation is original to NotFair. --- ## Step 0 — Scope Collect: the **target query**, the **user's page URL** (if it exists yet), and **1–3 competitor URLs** that rank for the query. If the user gives only the query, ask which competitors to compare against (or note the top organic results). ## Phase 0 — Preflight & data Read and follow `../shared/preamble.md`. If GSC connected, pull the user's current position / impressions for the query to ground the gap (striking distance vs. far behind). ## Phase 1 — Crawl all pages Fetch the user's page and each competitor page. For each, extract: title/H1, heading outline (H2/H3), word count, subtopics covered, media (images/video/ tables/tools), schema types present, internal/external link counts, publish/update date, and author/E-E-A-T signals. ## Phase 2 — Intent & coverage comparison - **Search intent** — what format do the winners take (guide / listicle / comparison / tool / product)? Does the user's page match? Intent mismatch is often the whole story. - **Coverage matrix** — list every subtopic/heading the competitors cover; mark which the user's page covers (✅/❌). The ❌ rows are the content gaps. - **Depth & format** — word count, tables, examples, original data, media richness. - **Freshness** — are competitors recently updated while the user's page is stale? ## Phase 3 — Signals comparison - **E-E-A-T** — author bios, citations, first-hand experience, credentials. - **Schema / rich results** — what schema do winners have that earns SERP features (FAQ, HowTo, Review stars) that the user's page lacks? - **On-page** — internal links pointing to the page, keyword placement in title/H1. ## Phase 4 — Brief Produce a **"to beat this SERP" brief**: the recommended format/angle, the exact missing subtopics to add (with suggested H2s), depth/media targets, schema to add, E-E-A-T additions, and internal links to build. Make it directly handable to `/content-writer`. Write in the user's language.

Frequently asked questions