competitor-analysis
Skill2 starsChanged 20 days agoMITView on GitHub
Deep dive on one competitor's SEO: organic traffic, ranked keywords, top pages, content themes, backlinks, local visibility, and head-to-head SERPs against the user's site, ending in a plan to outrank them. Use when the user names a competitor domain and asks why it ranks, what it ranks for, how to beat it, or for a keyword gap. For a whole market, use competitive-landscape instead.
65 other projects use a version of this, 10 of them edited.
Adopted by
Most recently taken up by
- XuHo-IT/Content-Agent-Kittheir own version, first seen Nov 15, 2026
- Kuan-AI-com/agent-skillstheir own version, first seen Nov 15, 2026
- asospy/asospy-agent-skillstheir own version, first seen Nov 15, 2026
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
- foverse/seoverseedited, first seen Nov 8, 2026
Used with
Projects with it also use openseo-release-notes, openseo-review-web-content and 2 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
- +2 more from Jwuthri
Other versions65 projects use a version of this.
Word for word · 0
None found.
Edited · 10
- every-app/open-seo★ 28k54% same
- Jwuthri/Tracely-ai★ 1.3k91% same
- VladSez/easy-invoice-pdf★ 1.1k91% same
- jwuthri-cloud/Tracely-ai★ 97991% same
- petera2c/simple-table★ 23391% same
- foverse/seoverse★ 454% same
- kid7st/agenticseo★ 225% same
- ventra-rocket/EchoSEO★ 291% same
- ictlondon/kraftskills★ 069% same
- IsaacBell/ai-marketing-toolkit★ 091% same
Wrote their own version · 55
- langchain-ai/deepagents★ 31ksame name
- browserbase/agent-browse★ 3.7ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- OpenClaudia/openclaudia-skills★ 731same name
- vivy-yi/xiaohongshu-skills★ 455same name
- itseffi/agentic-os★ 114same name
- cognyai/claude-code-marketing-skills★ 106same name
- Infinite-Labs-AI/infinite-skills★ 43same name
- yuanhao667/Skills★ 10same name
- AppKittie/aso-mcp-skills★ 8same name
45 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 repository17 other files it gives its agents.
- ai-search-visibilitySkill
- client-seo-reportSkill
- competitive-landscapeSkill
- 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
24 rules. 0 are common, 10 are distinctive, and 14 are very specific to this project.
0
Common
Most of the 54 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use this for a named competitor.
- 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 38
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 39
When whoami returns mode: "self-hosted", there are no plan gates.
- Distinctive: line 43
Use this mode only when Step 0 finds no connection.
- Distinctive: line 47
Read the competitor's site: navigation, sitemap, blog, product, and comparison pages.
- Distinctive: line 49
Check live search results for target terms to compare the two sites head to head.
- Distinctive: line 50
Use the user's Search Console CSV exports, if any, as their own baseline.
- 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 86
Call get_domain_overview for the competitor, passing provided location/language when supported.
- Very specific: line 87
If comparing to the user, call get_domain_overview for the user's domain too — and if Search Console is connected, …
- Very specific: line 88
Call get_ranked_keywords for the competitor.
- Very specific: line 89
If comparing to the user, call get_ranked_keywords for the user's domain/page too, or use get_serp_results for the shared terms when a …
- Very specific: line 91
Use find_serp_competitors when the competitor was supplied by the user but its search overlap is unclear.
- Very specific: line 99
Call get_backlinks_overview for the competitor, especially if authority appears to explain rankings.
- Very specific: line 100
Use get_serp_results for important shared or target keywords to compare positioning, passing provided location/language when supported.
- Distinctive: line 135
Do not treat all competitor keywords as desirable.
- Distinctive: line 137
Do not infer competitor page/content-type patterns from keyword rows alone.
- Distinctive: line 139
Do not recommend copying content.
- Distinctive: line 140
If the user's domain is unavailable, frame the analysis as competitor-only.
“Common” is measured: kept by at least 6 in 10 of the 54 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 Competitor Analysis
Goal
Analyze one competitor deeply enough to decide what to learn from, avoid, counter-position against, or outrank.
Use this for a named competitor. For identifying the market leaders first, use competitive-landscape.
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 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 with PayPal; 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
- Read the competitor's site: navigation, sitemap, blog, product, and comparison pages.
- Map their page types, content themes, and positioning.
- Check live search results for target terms to compare the two sites head to head.
- Use the user's Search Console CSV exports, if any, as their own baseline.
- Frame the analysis as qualitative.
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 this competitor's traffic, ranked keywords, and backlink profile." 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- Competitor domain
- User's domain when comparison is requested
- Optional topic/category/location/language
HarborRank MCP tools
get_domain_overview: baseline organic traffic and keyword count.get_search_console_performance: when comparing to the user's own domain and Search Console is connected, use it as the first-party baseline (real clicks/impressions/CTR/position) instead of estimating the user's own performance from third-party data.get_ranked_keywords: exact keyword, URL, rank, intent, traffic, CPC, and SERP-type rows for the competitor domain or page.get_backlinks_overview: backlink/referring-domain profile.find_serp_competitors: validate whether the named competitor is a real search competitor across the target keyword set.search_local_businesses,get_local_serp_results, andget_google_business_questions: use for local SEO competitors when Maps/local-pack visibility, nearby businesses, categories, or Google Q&A matter.get_serp_results: validate direct head-to-head SERPs for important keywords.research_keywords: expand gaps or category terms when needed.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
- Call
get_domain_overviewfor the competitor, passing provided location/language when supported. - If comparing to the user, call
get_domain_overviewfor the user's domain too — and if Search Console is connected,get_search_console_performancefor the user's real baseline. - Call
get_ranked_keywordsfor the competitor. Use filters likemaxRank,minSearchVolume,excludeBrandTerms, andresultTypesto keep rows relevant. - If comparing to the user, call
get_ranked_keywordsfor the user's domain/page too, or useget_serp_resultsfor the shared terms when a lighter check is enough. - For local SEO, use
search_local_businessesandget_local_serp_resultsaround the relevant business location(s) before drawing local-pack conclusions. Addget_google_business_questionsonly when Q&A evidence matters. - Use
find_serp_competitorswhen the competitor was supplied by the user but its search overlap is unclear. - Group competitor keywords into themes:
- Product/category terms
- Alternatives/comparisons
- Templates/tools/calculators
- Educational guides
- Branded demand
- Local/neighborhood terms when relevant
- Call
get_backlinks_overviewfor the competitor, especially if authority appears to explain rankings. 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. - Use
get_serp_resultsfor important shared or target keywords to compare positioning, passing provided location/language when supported. - Produce an actionable plan:
- What they are doing well
- Where they are vulnerable
- Which pages/keywords to pursue
- What to avoid copying
Output format
Start with:
- Competitor snapshot
- Biggest lesson
- Best opportunity to beat them
Then include:
| Area | Competitor pattern | Evidence | HarborRank opportunity |
Include sections for:
- Top keyword themes
- Content/page types working for them
- Backlink/authority notes
- Head-to-head SERP observations
- Priority actions for the user
- Next workflow: end with one recommended next workflow, the reason for it, and the input it starts from. Default:
link-prospectingagainst the competitor's strongest pages, the ones that rank for the keywords the user wants, to find the sites that link to them. - 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: "What changed for
<competitor-domain>since <today's date>?" Say in one line why it needs that wait: ranking footprints shift month to month, and a month gives a fair comparison with this report. 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/<competitor-domain>-<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
- Do not treat all competitor keywords as desirable. Filter for business fit.
- Separate evidence from inference.
- Do not infer competitor page/content-type patterns from keyword rows alone; use SERP or web evidence for page-level claims.
- For local SEO, do not infer Maps/local-pack strength from national organic domain metrics alone; use local business and local SERP tools when the location is known or reasonably discoverable.
- Do not recommend copying content; recommend a stronger angle or better answer to the same intent.
- If the user's domain is unavailable, frame the analysis as competitor-only.
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.

