agentleFS
UXMagicaiUXMagicai/seosorted-skills/skills/competitor-analysis/SKILL.md

competitor-analysis

Skill0 starsChanged 39 days agoMITView on GitHub

Analyze SEO competitors with SEOsorted — side-by-side Domain Rating, traffic, ranking keywords and links, keyword gaps, who ranks for the money keywords on Google today, audit benchmarks, backlink gaps and AI share of voice — and turn them into a plan. Use when the user asks who their SEO competitors are, how they compare, why competitors outrank them, competitor traffic or keywords, or a competitive SEO analysis.

64 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-project-setup, app-marketing-context and 10 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.
  • JwuthriSkill

    seo-project-setup

    Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.

    Also in 11 projects that use this

  • appeekySkill

    app-marketing-context

    When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.

    Also in 6 projects that use this

  • appeekySkill

    metadata-optimization

    When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.

    Also in 6 projects that use this

  • JwuthriSkill

    openseo-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

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 11 projects that use this

  • MicrosoftSkill

    competitive-landscape

    Use when a branch manager asks something like \"Who are we up against in each metro\"

    Also in 11 projects that use this

  • +5 more from Jwuthri
  • +1 more from appeeky

The file

Files
SKILL.md

Competitor analysis

Steps

  1. Who. manage_competitors operation: "list" for tracked competitors. To find who really competes in search, check_google_results operation: "results" with keyword for 2–3 money keywords (1 keyword lookup credit each) — the domains in the top 10 are the search competitors, not only business rivals. Add missing ones with manage_competitors operation: "add" and url (EDITOR); unmeasured ones with operation: "score", then poll check_job_status.
  2. Side by side. analyze_any_domain operation: "compare" with domains: [the site, up to 4 competitors] — authority, traffic, keywords and links (1 keyword lookup credit per domain).
  3. Keyword gap. analyze_any_domain operation: "keyword_gap" with domain (the site), competitor and mode: "missing" — keywords they rank for and the site does not (1 credit). mode: "shared" shows both positions where they compete head-on.
  4. Their best pages. analyze_any_domain operation: "pages" with the competitor's domain (1 credit) — the topics driving their traffic.
  5. Where each ranks. check_google_results operation: "rank" with keywords (up to 20) and domain — run it for the site and the main competitor (1 credit per keyword).
  6. Benchmarks. audit_my_site operation: "report" for audit scores against competitors, if benchmarked.
  7. Links. manage_competitors operation: "backlink_gap" with url set to the strongest competitor (paid plans; pass on any upgrade link).
  8. AI search. track_ai_search_visibility operation: "summary" for share of voice against the same competitors.

Tell the user the credit total before steps 2–5; they share the keyword lookup allowance.

Output

  • Table: competitor, Domain Rating, estimated traffic, ranking keywords, AI share of voice, where they are ahead.
  • Top 3 reasons they outrank the user, each backed by a number from the tools.
  • Actions: keyword gaps (→ keyword-research, save with research_keywords operation: "save"), comparison pages (→ comparison-pages), link gaps (→ backlinks, backlink-outreach), technical gaps (→ seo-audit).

Traffic and keyword figures are modelled estimates for one Google market; say so.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.