competitive-landscape
Skill2 starsChanged yesterdayMITView on GitHub
Map who wins an SEO market across many competitors: recurring ranking domains, their organic footprint, winning content formats, backlinks, local pack leaders, and open gaps. Use when the user asks who ranks for a topic or market, who their SEO competitors are, or where the openings are. For a deep dive on one named competitor, use competitor-analysis instead.
22 other projects use a version of this, 11 of them edited.
Adopted by
Most recently taken up by
- teemukarjaluoto/seo-sauna-mcpedited, first seen Nov 16, 2026
- winsley-jeune/harborrank-skillsword for word, first seen Nov 15, 2026
- foverse/seoverseedited, first seen Nov 8, 2026
- jwuthri-cloud/Tracely-aiedited, first seen Oct 20, 2026
- Ultimate-Alchemy/claude-skillstheir own version, first seen Oct 15, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use openseo-release-notes, openseo-review-web-content and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JwuthriSkillopenseo-release-notes
Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.
Also in 6 projects that use this
JwuthriSkillopenseo-review-web-content
Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.
Also in 5 projects that use this
ten9876Skillpapercuts
Read-only AetherSDR issue triage that surfaces the UX papercuts, bugs, and regressions you can fix AND prove today with the agent automation bridge. Use when the user says $papercuts or /papercuts, or asks to "find papercuts", "what can I fix and prove today", "triage bridge-provable issues", "what UX bugs can the bridge close", "sort issues by priority I can knock out", or otherwise wants a curated, lifecycle-aware (design→code→prove) shortlist of issues — NOT the label-and-respond /triage workflow. This is the discovery step that feeds /fb. Strictly read-only: it never labels, comments, closes, or edits issues.
Also in 4 projects that use this
01claudingSkillseo-report
SEO reporting and analytics dashboard generation. Creates weekly digests, monthly performance reports, quarterly strategy reviews, and real-time dashboard templates. Use when user says "SEO report", "weekly digest", "monthly report", "dashboard", "SEO metrics", "performance summary".
Also in 3 projects that use this
- +2 more from Jwuthri
Other versions22 projects use a version of this.
Word for word · 1
- winsley-jeune/harborrank-skills★ 2100% same
Edited · 11
- every-app/open-seo★ 28k50% same
- Jwuthri/Tracely-ai★ 1.3k87% same
- VladSez/easy-invoice-pdf★ 1.1k87% same
- jwuthri-cloud/Tracely-ai★ 97987% same
- petera2c/simple-table★ 23387% same
- foverse/seoverse★ 450% same
- kid7st/agenticseo★ 225% same
- ventra-rocket/EchoSEO★ 287% same
- ictlondon/kraftskills★ 065% same
- IsaacBell/ai-marketing-toolkit★ 087% same
1 more not listed
Wrote their own version · 10
- sendaifun/solana-new★ 178same name
- didixuxu/didi-skills★ 83same name
- xfstudio/skills★ 9same name
- microsoft/aibast-agents-library★ 8same name
- ai4brands-design/claude-skills★ 2same name
- CodeWithBehnam/cc-docs★ 2same name
- Oceanjackson1/Claude-Skill★ 2same name
- garri333/Skills★ 1same name
- Samueladewole/claude-skills★ 0same name
- Ultimate-Alchemy/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- ai-search-visibilitySkill
- client-seo-reportSkill
- competitor-analysisSkill
- content-briefSkill
- google-business-profileSkill
- keyword-cannibalizationSkill
- keyword-clusteringSkill
- keyword-researchSkill
- lead-teardownSkill
- link-prospectingSkill
- local-seoSkill
- schema-markupSkill
- seo-auditSkill
- seo-coachSkill
- seo-contextSkill
- seo-project-setupSkill
- seo-proposalSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 10 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use this when the user wants a market-level view across several competitors.
- Very specific: line 18
If neither tool is available, or whoami fails because the user is not signed in, tell the user plainly: "HarborRank isn't connected, so I …
- Distinctive: line 29
Do not stop there. Continue in fallback mode (below).
- Very specific: line 35
If creditsRemaining will not cover the planned calls, give the user the estimate and ask before spending.
- Very specific: line 37
If a tool fails for insufficient credits, stop making paid calls, tell the user, and finish with free tools and the data you already have.
- Very specific: line 39
If the user asks to upgrade, change plan or buy credits, call get_upgrade_link (no credits) and give them the link.
- Very specific: line 40
When whoami returns mode: "self-hosted", there are no plan gates.
- Distinctive: line 44
Use this mode only when Step 0 finds no connection.
- Distinctive: line 48
Run the market query set through web search and note which domains keep appearing.
- Distinctive: line 50
Read the leaders' sites to identify the content formats, themes, and positioning that are working.
- Distinctive: line 51
Call the result directional.
- Distinctive: line 59
Start with the label Web-evidence only: no HarborRank data.
- Very specific: line 65
If the project's SEO folder has seo-context.md (see seo-context), read it first for the site, market, audience, competitors and goals, and …
- Very specific: line 88
Use provided keywords, or call research_keywords to build 5-10 representative queries.
- Very specific: line 91
If the query set is already known, use get_keyword_metrics to validate relative demand and difficulty and find_serp_competitors to identify …
- Very specific: line 93
Call get_serp_results for representative queries when live SERP composition, ranking URLs, or SERP features need inspection.
- Distinctive: line 107
Start with the market read:
- Distinctive: line 133
Do not overstate exact traffic when HarborRank returns estimates.
- Distinctive: line 134
If using a small query set, call the result directional.
- Distinctive: line 135
Do not assume a publisher is a product competitor.
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
HarborRank Competitive Landscape
Goal
Answer: "Who is winning this SEO market, what content is working for them, and where are the openings?"
Use this when the user wants a market-level view across several competitors. For a deep dive on one domain, use competitor-analysis.
Step 0: Check connection
Before any other step, confirm the HarborRank MCP tools are loaded. Look for get_domain_overview or list_leads among your tools, including deferred tools you can load (the name may carry a prefix such as mcp__harborrank__). If they are there, call whoami: it uses no credits, confirms the user is signed in, and returns creditsRemaining for budgeting the run. Do not call a research tool to test the connection.
If neither tool is available, or whoami fails because the user is not signed in, tell the user plainly: "HarborRank isn't connected, so I can't pull live HarborRank data yet." Then tell them how to connect it:
- Claude Code with the HarborRank plugin: run
/mcp, chooseharborrank, and sign in. - Claude Code without the plugin: run
claude mcp add --transport http --scope user harborrank https://app.harborrank.com/mcp, then/mcpto sign in. - Claude on the web, desktop or Cowork: open Customize, then Connectors, search for HarborRank, choose Connect, and sign in. New accounts start with a 7-day free trial.
- Cursor with the HarborRank plugin: open Cursor Settings, then MCP, and sign in to
harborrank. - Gemini CLI with the HarborRank extension: run
/mcp auth harborrank. - Other clients: add
https://app.harborrank.com/mcpas a remote MCP server. Setup for each client is at https://harborrank.com/docs/mcp.
Tell them what happens when they connect: they sign in to HarborRank with Google or email and start a 7-day free trial. Then they come back to this conversation and say "connected", and you pick up the task where it stopped.
Do not stop there. Continue in fallback mode (below). If the user connects HarborRank mid-task, run Step 0 again and switch to the full workflow.
Plan limits
On hosted HarborRank, research tools spend credits. New accounts start with a 7-day free trial (1,000 research credits, one project); paid plans start at $29/month with 15,000 credits. Search Console, saved keywords, rank tracker reads, and site crawls use no credits. A keyword search costs about 50 credits and a domain overview about 80. Full backlinks, lead research (research_lead), and Lighthouse checks need a paid plan; on Free, the backlinks tools return a preview (totals and the top 3 referring domains, about 50 credits) with an upgrade link.
- If
creditsRemainingwill not cover the planned calls, give the user the estimate and ask before spending. Use the free tools first. - If a tool replies that a feature "is included in paid plans", tell the user once which feature needs a paid plan and pass on the upgrade link from the reply, skip that tool for the rest of the run, and finish with the other evidence. Do not retry it.
- If a tool fails for insufficient credits, stop making paid calls, tell the user, and finish with free tools and the data you already have. If
whoamiwarns that credits are low, say so before a large run. - If a HarborRank tool says the free trial hasn't started, or that credits ran out, give the user the link from that reply exactly as written, as a clickable link, and wait for them to say they're done before calling HarborRank again. Don't switch to answering without HarborRank data unless they ask you to.
- If the user asks to upgrade, change plan or buy credits, call
get_upgrade_link(no credits) and give them the link. They pay on HarborRank by card; never say the upgrade is done untilwhoamishows the new plan. - When
whoamireturnsmode: "self-hosted", there are no plan gates.
Fallback mode (no HarborRank connection)
Use this mode only when Step 0 finds no connection. It works from web search, page reading, and files the user provides.
Can still do
- Run the market query set through web search and note which domains keep appearing.
- Group those domains by type: direct competitors, publishers, directories, communities, resources.
- Read the leaders' sites to identify the content formats, themes, and positioning that are working.
- Call the result directional.
Must not estimate
Traffic, search volume, keyword difficulty, CPC, keyword counts, rankings, backlink counts, Maps pack positions, and Q&A counts. Write unknown for each. A web search shows which pages appeared for a query when you searched, not their Google ranking: report it as "appeared in web search", never as a position.
Output
- Start with the label Web-evidence only: no HarborRank data.
- Name the source (URL or file) of every figure you report.
- End, after any recommended next workflow, with one sentence that names the numbers this report is missing: "Connect HarborRank (start with a 7-day free trial) to add each leader's organic footprint, traffic, and backlink strength." Do not add more sales copy than that.
Required inputs
If the project's SEO folder has seo-context.md (see seo-context), read it first for the site, market, audience, competitors and goals, and ask only for what it doesn't cover.
projectId- Topic, seed keywords, market/category, or user's domain
- Optional known competitors
- Optional location/language
HarborRank MCP tools
research_keywords: discover representative market queries.get_keyword_metrics: validate known query sets with volume, difficulty, intent, and trends.get_serp_results: identify recurring ranking domains across target queries.find_serp_competitors: compare domains competing across supplied keywords; use this before manual SERP counting when a keyword set is available.get_domain_overview: size organic footprint for candidate leaders.get_search_console_performance: when the user's own domain is in the comparison and Search Console is connected, anchor their position with first-party clicks/impressions/CTR rather than third-party estimates.get_ranked_keywords: find exact ranking keywords, URLs, ranks, intents, and SERP result types for leaders.get_backlinks_overview: compare backlink/referring-domain strength where relevant.search_local_businesses,get_local_serp_results, andget_google_business_questions: use for local SEO markets where proximity, Maps rankings, business categories, reviews, or Google Q&A affect who is winning.create_share_report: publish the finished work as a read-only page at a shareable link (see "Shareable report" below). Only after the user agrees.
Workflow
- Define the market query set:
- Use provided keywords, or call
research_keywordsto build 5-10 representative queries. - Include mixed intent: informational, commercial, comparison, and tool/software terms when applicable.
- For local SEO, include neighborhood/city/service-area queries and identify the priority locations or coordinates.
- Use provided keywords, or call
- If the query set is already known, use
get_keyword_metricsto validate relative demand and difficulty andfind_serp_competitorsto identify recurring domains at scale. - For local SEO, call
search_local_businessesandget_local_serp_resultsfor the highest-priority location(s) before synthesizing winners. Useget_serp_resultsas a complement for organic pages, not as the only local evidence. - Call
get_serp_resultsfor representative queries when live SERP composition, ranking URLs, or SERP features need inspection. Send at most 10 queries per call. - Identify recurring domains and group them by type:
- Direct product competitors
- Publishers/media
- Marketplaces/directories
- Communities/forums
- Documentation/resources
- For the strongest recurring domains, call
get_domain_overview; default to the top 3-5 domains before expanding. - For direct competitors and relevant publishers, call
get_ranked_keywords. - Use
get_backlinks_overviewwhen backlink authority appears important or the user asks why a domain is winning. On Free this returns a preview (totals and the top 3 referring domains); use it, note that the full profile needs a paid plan, and continue with SERP and domain evidence. - Synthesize patterns: content types, themes, SERP formats, local-pack signals, authority advantages, and underserved angles.
Output format
Start with the market read:
- Market leaders
- Most winnable opportunity area
- Biggest barrier to ranking
Then include:
| Domain | Type | Why they matter | Organic footprint | Winning themes | Weakness/gap |
Add:
- Query set used
- Content formats that are working
- Keyword/theme gaps
- Backlink or authority observations
- Next workflow: end with one recommended next workflow, the reason for it, and the input it starts from. Default:
competitor-analysison the most beatable direct competitor among the leaders, named explicitly. - Check back: end with one dated follow-up: the date (today plus 30 days, written out, for example "Monday, November 9") and the exact question to ask then: "Who moved in the
<market>landscape since <today's date>?" Say in one line why it needs that wait: a month of ranking changes is enough to see who is gaining. Add it to theFollow-upslist in the SEO folder'sREADME.md(create the list if it is missing) so the next session finds it. One follow-up only; don't add reminders or repeat it. If scheduled tasks are available (Cowork and the Claude apps on paid plans), offer once to make this a weekly scheduled task instead, named for the site, so the check runs by itself; the user reviews and confirms the schedule. - Where the output goes: the report as
competitors/landscape-<market-slug>-<YYYY-MM-DD>.md. Save it in the project's SEO folder (seeseo-project-setup); if there is none, ask once whether to create one or where to save instead. If the user prefers a doc or a sheet and a docs or spreadsheet tool is available, put reports in a doc and tables in a sheet instead. Tell the user where it was saved. - Shareable report: once the work is done, offer one time to publish it as a shareable report with
create_share_report: a read-only page at a link the user can send to a client, a boss or a teammate, no sign-in needed. Write it from this output: findings first, then next steps, then the supporting table. Publish only after the user says yes, and leave out their Search Console and Google Analytics numbers unless they agree to share them. Give them the link;delete_share_reportremoves it.
Guardrails
- Distinguish SEO competitors from business competitors.
- Do not overstate exact traffic when HarborRank returns estimates.
- If using a small query set, call the result directional.
- Do not assume a publisher is a product competitor; label domain types clearly.
- For local markets, distinguish organic-page winners from Maps/local-pack winners.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

