mcpbeat Sign in

Competitor Pages Skill for Claude

> 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 "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.

881 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3345
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/nowork-studio/NotFair --skill competitor-pages

The instruction itself

7 sections, as written by the author

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.

Other skills for the same job

different authors, same section of the catalogue
Internal Comms
by anthropics
vendor ×13

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

6k tokens
Competitive Ads Extractor
by frostant
×10

Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.

2k tokens
Lead Research Assistant
by frostant
×8

Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.

2k tokens
Developer Growth Analysis
by frostant
×6

Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.

4k tokens
App Store Optimization
by alirezarezvani
×3

Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store

55k tokens scripts
Deeptools
by christophacham
×3

NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.

21k tokens scripts
Pymatgen
by christophacham
×3

Materials science toolkit. Crystal structures (CIF, POSCAR), phase diagrams, band structure, DOS, Materials Project integration, format conversion, for computational materials science.

26k tokens scripts
Enhance Prompt
by google-labs-code
vendor ×2

Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.

3k tokens

How to use it

Copy the folder

Take nowork-studio/competitor-pages from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.