Agent skill · Backend & API

seo-competitor

Run a competitive SEO analysis comparing the user's site to chosen competitors across SERP overlap, content depth, backlink profiles, technical posture, and brand presence. Use this skill whenever the user wants to analyze competitors, find content gaps, identify backlink opportunities, understand why competitors outrank them, or benchmark against the rest of their category. Triggers on competitor analysis, competitive analysis, SERP analysis, content gap, backlink gap, why is X ranking, who is winning the SERP, beat my competitor, benchmark, market positioning. Also triggers when planning a c

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill seo-competitor --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/seo-competitor/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# SEO Competitor Analysis Compare a site to its competitors and find the gaps worth closing. Stack-agnostic. Tool-friendly but tool-optional. --- ## When to use - Identifying which competitors to study - Finding content gaps (topics they cover, you do not) - Finding backlink gaps (sites linking to them, not you) - Understanding why a specific competitor outranks the user - Benchmarking authority, technical posture, and content depth ## When NOT to use - Single-page optimization (use `seo-onpage`) - Initial keyword research with no competitors yet identified (use `seo-keyword` first to find them) - Auditing one's own existing content (use `seo-content-audit`) --- ## Required inputs - The user's site - 3 to 5 named competitors (or the topic area, if competitors are not yet identified) - Access to a keyword tool, a backlink tool, and any crawler If competitors are unknown, start by listing the top 10 ranking domains for the user's top 10 priority keywords. Pick the 3 to 5 that appear most often. Where competitor traffic estimation is the input you need (relative scale, channel mix, audience overlap), Similarweb MCP is the strongest source. Pair with Ahrefs (for backlink and keyword ov

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 5 angles
  5. 1. SERP overlap
  6. 2. Content depth
  7. 3. Backlink profile
  8. 4. Technical posture
  9. 5. Brand and entity strength
  10. Workflow
  11. Failure patterns
  12. Output format
  13. Reference files
Ships with 2 files
  • references/competitive-audit-template.md
  • references/content-gap-method.md
More from claude-skills
All skills →
About this skill
What does the seo-competitor skill do?

Run a competitive SEO analysis comparing the user's site to chosen competitors across SERP overlap, content depth, backlink profiles, technical posture, and brand presence. Use this skill whenever the user wants to analyze competitors, find content gaps, identify backlink opportunities, understand why competitors outrank them, or benchmark against the rest of their category. Triggers on competitor analysis, competitive analysis, SERP analysis, content gap, backlink gap, why is X ranking, who is winning the SERP, beat my competitor, benchmark, market positioning. Also triggers when planning a c

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill seo-competitor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going