competitive-landscape
Skill2 starsChanged 52 days agoMITView on GitHub
Map SEO market leaders, winning content themes, keyword coverage, backlinks and strategic gaps across several competitors. Use when the user asks who is winning a search market or where the openings are.
- Reads credentials
20 other projects use a version of this, 10 of them edited.
Adopted by
Most recently taken up by
- foverse/seoverseedited, first seen Nov 8, 2026
- winsley-jeune/harborrank-skillsedited, first seen Oct 27, 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
- microsoft/aibast-agents-librarytheir own version, first seen Oct 13, 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 versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 10
- every-app/open-seo★ 28k58% same
- Jwuthri/Tracely-ai★ 1.3k49% same
- VladSez/easy-invoice-pdf★ 1.1k49% same
- jwuthri-cloud/Tracely-ai★ 97949% same
- petera2c/simple-table★ 23349% same
- foverse/seoverse★ 458% same
- ventra-rocket/EchoSEO★ 249% same
- winsley-jeune/harborrank-skills★ 215% same
- ictlondon/kraftskills★ 047% same
- IsaacBell/ai-marketing-toolkit★ 049% same
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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 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
12 rules. 0 are common, 3 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Use this when the user wants a market-level view across several competitors.
- Very specific: line 16
Use the installed agenticseo command.
- Very specific: line 26
Run agenticseo context first and ground the market read in it: the saved competitors are the starting roster, and the business and …
- Very specific: line 28
Before paying, check researchLog.
- Very specific: line 51
Use the provided keywords, or run agenticseo research to build 5–10 representative queries.
- Very specific: line 54
If the query set is already known, use agenticseo keywords to validate relative demand and difficulty, and agenticseo competitors to …
- Very specific: line 56
Run agenticseo serp for representative queries when live SERP composition, ranking URLs or SERP features need inspection.
- Very specific: line 65
Use agenticseo backlinks overview when backlink authority appears important or the user asks why a domain is winning.
- Very specific: line 72
If a report template applies (see seo-report), its sections and tone replace this list.
- Distinctive: line 86
Do not overstate exact traffic.
- Distinctive: line 87
If using a small query set, call the result directional.
- Distinctive: line 88
Do not assume a publisher is a product competitor.
“Common” is measured: kept by at least 6 in 10 of the 19 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
<!-- Adapted from OpenSEO plugins/openseo/skills/competitive-landscape/SKILL.md (https://github.com/every-app/open-seo, MIT, Copyright (c) 2026 Ben Senescu) for the AgenticSEO CLI. -->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.
Use the installed agenticseo command. Research lookups are billed by DataForSEO and need DATAFORSEO_API_KEY; each result states its cost and points to an evidence file.
Required inputs
- Topic, seed keywords, market/category or the user's domain
- Optional known competitors
- Optional location/language
Project context
- Run
agenticseo 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. If there is no project, set one up asseo-project-setupstep 1 describes. - 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
agenticseo competitorsand the site and confirm it, write it tocompetitorsin.agenticseo/context.json, then continue. Never front-load the full interview; suggestseo-project-setupat the end for the rest. - Before paying, check
researchLog. If the same research ran within the last 30 days, reuse its evidence and say so instead of buying it again. - On finish, write back what is durable: every confirmed competitor in
competitorswith a short note on why it matters, and remove entries you added that turned out irrelevant (leave entries the user added alone). Append{ "entryDate": "<today from agenticseo context>", "summary": "Competitive landscape: <market/query set>. Verdict: <conclusion>. Evidence: <paths>" }toresearchLog. Runagenticseo contextto validate.
Deliver as a report
Deliver through the seo-report skill. If that skill is not available, say so and stop before writing the report.
Commands
agenticseo research "SEED"...: discover representative market queries, up to 5 seeds per call.agenticseo keywords TERM...: validate a known query set with volume, difficulty, intent and trends.agenticseo serp "QUERY"...: live SERP composition and ranking URLs, up to 10 queries per call.agenticseo competitors KEYWORD...: the domains competing across a keyword set (up to 100 keywords); use this before counting SERPs by hand.agenticseo domain DOMAIN: size the organic footprint of candidate leaders.agenticseo gsc performance: when the user's own domain is in the comparison and Search Console is connected, anchor their position with first-party clicks, impressions and CTR rather than third-party estimates.agenticseo ranked DOMAIN: exact ranking keywords, URLs, ranks, intents and SERP result types for leaders.agenticseo backlinks overview DOMAIN: compare backlink and referring-domain strength where relevant.agenticseo local businesses,agenticseo local serpandagenticseo local questions: for local markets where proximity, Maps rankings, business categories, reviews or Google Q&A affect who is winning.agenticseo ai brand DOMAIN --competitors A,B: when the user asks who AI answers recommend, share of voice in ChatGPT and Google AI Overview. It is the most expensive lookup (about $0.84 with competitors); say so before running it.
Workflow
- Define the market query set:
- Use the provided keywords, or run
agenticseo researchto build 5–10 representative queries. - Include mixed intent: informational, commercial, comparison and tool/software terms when applicable.
- For local SEO, include neighborhood, city and service-area queries, and identify the priority locations or coordinates.
- Use the provided keywords, or run
- If the query set is already known, use
agenticseo keywordsto validate relative demand and difficulty, andagenticseo competitorsto identify recurring domains at scale. - For local SEO, run
agenticseo local businessesandagenticseo local serpfor the highest-priority location(s) before naming winners. Useagenticseo serpas a complement for organic pages, not as the only local evidence. - Run
agenticseo serpfor representative queries when live SERP composition, ranking URLs or SERP features need inspection. Keep it to about 10 queries; each is billed. - Identify recurring domains and group them by type:
- Direct product competitors
- Publishers/media
- Marketplaces/directories
- Communities/forums
- Documentation/resources
- For the strongest recurring domains, run
agenticseo domain; default to the top 3–5 domains before expanding. - For direct competitors and relevant publishers, run
agenticseo ranked. - Use
agenticseo backlinks overviewwhen backlink authority appears important or the user asks why a domain is winning. Continue with SERP and domain evidence if it fails. - Synthesize patterns: content types, themes, SERP formats, local-pack signals, authority advantages and underserved angles.
Output format
Title: Competitive Landscape: <market or category> — <date> (see seo-report).
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 change 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-clusteringor a content brief. - How this report was made: opens with the skill link line from
seo-report, pointing athttps://github.com/kid7st/agenticseo/blob/main/.agents/skills/competitive-landscape/SKILL.md("AgenticSEO Competitive Landscape skill"), then the query set used, the costs and evidence paths, 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; provider traffic figures are 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.
- Missing metrics are
unknown, never 0. On exit code 3, ask the user to fix the key; on exit code 4, report the error and any charged cost, and do not retry in a loop.
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.

