agentleFS
Sign inStart free
jwuthri-cloudjwuthri-cloud/Tracely-ai/.claude/skills/competitor-analysis/SKILL.md

competitor-analysis

Skill1.2k starsChanged 20 days agoMITView on GitHub

Analyze one competitor's organic footprint, ranking keywords, content themes, backlinks, and gaps.

We split this skill into the rules it gives an agent

12 rules. 0 are common, 4 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this for a named competitor.

    line 12
  2. Very specific:

    Call get_domain_overview for the competitor, passing provided location/language when supported.

    line 34
  3. Very specific:

    If comparing to the user, call get_domain_overview for the user's domain too — and if Search Console is connected, …

    line 35
  4. Very specific:

    Call get_ranked_keywords for the competitor.

    line 36
  5. Very specific:

    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 …

    line 37
  6. Very specific:

    Use find_serp_competitors when the competitor was supplied by the user but its search overlap is unclear.

    line 39
  7. Very specific:

    Call get_backlinks_overview for the competitor, especially if authority appears to explain rankings.

    line 47
  8. Very specific:

    Use get_serp_results for important shared or target keywords to compare positioning, passing provided location/language when supported.

    line 48
  9. Distinctive:

    Do not treat all competitor keywords as desirable.

    line 78
  10. Distinctive:

    Do not infer competitor page/content-type patterns from keyword rows alone.

    line 80
  11. Distinctive:

    Do not recommend copying content.

    line 82
  12. Distinctive:

    If the user's domain is unavailable, frame the analysis as competitor-only.

    line 83

“Common” is measured: kept by at least 6 in 10 of the 45 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenSEO 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.

Required inputs

  • projectId
  • Competitor domain
  • User's domain when comparison is requested
  • Optional topic/category/location/language

OpenSEO 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, and get_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.

Workflow

  1. Call get_domain_overview for the competitor, passing provided location/language when supported.
  2. If comparing to the user, call get_domain_overview for the user's domain too — and if Search Console is connected, get_search_console_performance for the user's real baseline.
  3. Call get_ranked_keywords for the competitor. Use filters like maxRank, minSearchVolume, excludeBrandTerms, and resultTypes to keep rows relevant.
  4. 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 lighter check is enough.
  5. For local SEO, use search_local_businesses and get_local_serp_results around the relevant business location(s) before drawing local-pack conclusions. Add get_google_business_questions only when Q&A evidence matters.
  6. Use find_serp_competitors when the competitor was supplied by the user but its search overlap is unclear.
  7. Group competitor keywords into themes:
    • Product/category terms
    • Alternatives/comparisons
    • Templates/tools/calculators
    • Educational guides
    • Branded demand
    • Local/neighborhood terms when relevant
  8. Call get_backlinks_overview for the competitor, especially if authority appears to explain rankings. Continue without backlink evidence if it is unavailable.
  9. Use get_serp_results for important shared or target keywords to compare positioning, passing provided location/language when supported.
  10. 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:

AreaCompetitor patternEvidenceOpenSEO 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

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.

Download now (ZIP)

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the jwuthri-cloud/Tracely-ai repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about jwuthri-cloud/Tracely-ai

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

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.

Check your setup, free