competitive-landscape
Skill0 starsChanged 19 days agoMITView on GitHub
Map SEO market leaders, winning content themes, keyword coverage, backlinks, and strategic gaps.
23 other projects use a version of this, 12 of them edited.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- harborrank/harborrank-skillsedited, first seen Nov 16, 2026
- winsley-jeune/harborrank-skillsedited, 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
Used with
Projects with it also use openseo-release-notes, openseo-review-web-content and 3 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
- +2 more from Jwuthri
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 12
- every-app/open-seo★ 28k96% same
- Jwuthri/Tracely-ai★ 1.3k88% same
- VladSez/easy-invoice-pdf★ 1.1k88% same
- jwuthri-cloud/Tracely-ai★ 97988% same
- petera2c/simple-table★ 23588% same
- foverse/seoverse★ 496% same
- harborrank/harborrank-skills★ 226% same
- kid7st/agenticseo★ 249% same
- ventra-rocket/EchoSEO★ 288% same
- winsley-jeune/harborrank-skills★ 226% same
2 more not listed
Wrote their own version · 11
- 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
- AtilaMedeiros/skills★ 1same name
- garri333/Skills★ 1same name
- Samueladewole/claude-skills★ 0same name
1 more not listed
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 repository11 other files it gives its agents.
- ai-prompt-researchSkill
- ai-visibility-auditSkill
- competitor-analysisSkill
- keyword-clusteringSkill
- keyword-researchSkill
- link-prospectingSkill
- local-seoSkill
- seo-auditSkill
- seo-coachSkill
- seo-project-setupSkill
- seo-reportSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 4 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
7
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 25
Call get_project_context first and ground the market read in it, the saved competitors are the starting roster, and the business and …
- Distinctive: line 27
Before spending credits, check the research log.
- Very specific: line 49
Use provided keywords, or call research_keywords to build 5-10 representative queries.
- Very specific: line 52
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 54
Call get_serp_results for representative queries when live SERP composition, ranking URLs, or SERP features need inspection.
- Very specific: line 63
Use get_backlinks_overview when backlink authority appears important or the user asks why a domain is winning.
- Very specific: line 70
If a report template applies (see seo-report), its sections and tone replace this list.
- Distinctive: line 84
Do not overstate exact traffic when SEO Sauna returns estimates.
- Distinctive: line 85
If using a small query set, call the result directional.
- Distinctive: line 86
Do not assume a publisher is a product competitor.
“Common” is measured: kept by at least 6 in 10 of the 22 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
SEO Sauna 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.
Required inputs
projectId- Topic, seed keywords, market/category, or user's domain
- Optional known competitors
- Optional location/language
Project context
The project-context tools are free and shared with the app and other agents.
- Call
get_project_contextfirst and ground the market read in it, the saved competitors are the starting roster, and the business and positioning decide who counts as a competitor. - This skill needs competitors. If none are saved, run a minimal inline setup: ask the user who they compete with, or infer a shortlist from
find_serp_competitorsand the site and confirm it, write it back withupdate_project_context(addCompetitors), then continue the landscape work. Never front-load the full interview; suggestseo-project-setupat the end for the rest. - Before spending credits, check the research log. If the same research ran within the last 30 days, reuse that result and say so instead of re-buying it.
- On finish, write back what is durable with
update_project_context, every confirmed competitor viaaddCompetitorswith a short note on why they matter, plusremoveCompetitorsfor entries you added that turned out irrelevant (leave rows the user added alone), and append a research log entry:{ appendResearchLog: { summary: "Competitive landscape: <market/query set>. Verdict: <conclusion>" } }.
Deliver as a report
Deliver through the seo-report skill, saving with skill: "competitive-landscape". If that skill is not available, say so and stop before writing HTML.
SEO Sauna 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.
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. Backlinks may be unavailable if the account has not enabled that data; continue with SERP/domain evidence if it fails. - Synthesize patterns: content types, themes, SERP formats, local-pack signals, authority advantages, and underserved angles.
Output format
h1: the market or category.
If a report template applies (see seo-report), its sections and tone replace this list.
Sections in this order:
- The market read, one or two opening sentences naming the leaders, the most winnable area, and the biggest barrier.
- Who is winning, a table of domain, type, organic footprint, winning themes, and the gap. Label domain types explicitly.
- Why they win, one finding per pattern, the Fix pointing at what the user should do instead.
- Gaps and openings, a table of theme, demand, and who currently owns it, plus a bar chart when a handful of themes carry the demand.
- What to do next, an ordered list ending in the next workflow to run: competitor analysis, keyword clustering, or a content brief.
- How this report was made, opens with the fixed line from
seo-report(workflow name "Competitive Landscape"), then the query set used, and a note calling the read directional when the query set was small.
Guardrails
- Distinguish SEO competitors from business competitors.
- Do not overstate exact traffic when SEO Sauna 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.

