agentleFS
busyeugenebusyeugene/content-marketing-skills/competitor-analysis/SKILL.md

competitor-analysis

Skill1 starsChanged 7 months agoMITView on GitHub

Use when the user wants a content marketing, SEO, and backlink competitive analysis. Profiles up to 10 competitors on content strategy, organic rankings, top pages, backlink profile, and voice/positioning, then writes a prioritized report with gaps to exploit.

  • Reads credentials

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

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Use AskUserQuestion for analysis angles (multi-select) and depth.

    line 36
  2. Distinctive:

    Ensure each domain is reachable.

    line 42
  3. Distinctive:

    Look for patterns: guest posts, podcast mentions, roundups, free tools, data studies.

    line 105

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

Competitor Analysis

Deep-profile up to 10 competitors across content, SEO, and backlinks. Output is a single markdown report that identifies gaps the user's brand can exploit and strengths to defend against.

Setup

Strongly recommended:

  • Ahrefs MCP — the official remote MCP server at https://api.ahrefs.com/mcp/mcp. Connect via Claude Code's MCP settings (OAuth, paid Ahrefs plan required). Use Site Explorer tools for organic keywords, top pages, backlinks, referring domains, organic competitors, and content gap. The archived npm package (github.com/ahrefs/ahrefs-mcp-server) is deprecated.
  • FIRECRAWL_API_KEY — scrape competitor blogs, landing pages, pricing, about pages.

Optional:

  • SE_RANKING_API_KEY — secondary rankings data and alerts.
  • TAVILY_API_KEY or EXA_API_KEY — surface mentions and brand signals not in Ahrefs.
  • JINA_API_KEY — higher Jina Reader quota for fallback scraping.

Inputs

  1. Own domain — the user's own site, used as the baseline for gap analysis.
  2. Competitor list — up to 10 domains. If the user doesn't know, call the Ahrefs MCP Site Explorer → organic competitors tool for suggestions and let the user confirm.
  3. Analysis angle — one or more of:
    • Content strategy (topics, cadence, formats)
    • Organic SEO performance
    • Backlinks and authority
    • Positioning and voice
    • Pricing and packaging
  4. Depth — fast (top-level metrics only), standard (metrics + top 20 pages each), deep (everything + full blog scrape).

Use AskUserQuestion for analysis angles (multi-select) and depth.

Process

1. Validate competitors

Ensure each domain is reachable. Drop any that 404 or block scraping; report which were dropped.

2. Metrics block (Ahrefs MCP)

For each competitor, call Site Explorer tools:

  • Overview → Domain Rating (DR), organic traffic, organic keyword count, referring-domain count
  • Top pages → top 20 organic pages with keyword, position, URL, traffic
  • Organic keywords → top 100 for overlap analysis
  • Refdomains → top 20 referring domains
  • All-backlinks (filtered last 30 days) → new backlinks count
  • Paid keywords (if exposed) → if running ads

Also call Site Explorer → content gap with own domain vs. all competitors. Capture keywords they all rank for that the user doesn't.

Exact MCP tool names vary by server version — enumerate once at session start and cache the mapping.

3. Content audit (Firecrawl)

For each competitor, fetch the blog index via the scraping fallback chain:

  • Try {domain}/blog, /resources, /learn, /insights, /news.
  • Parse the sitemap at /sitemap.xml as a fallback to enumerate posts.

For standard depth: scrape up to 20 recent posts per competitor. For deep: scrape up to 100.

For each post, extract:

  • Title, URL, publish date, author
  • Word count
  • Heading outline
  • Format (how-to / listicle / opinion / case study / news / comparison / tool page)
  • Top entities (top 15 content words minus stopwords)
  • Internal link count
  • Whether it has a CTA, and what kind (demo, lead magnet, newsletter)

Aggregate per competitor:

  • Publishing cadence (posts/month over the last 6 months)
  • Format mix (%)
  • Median word count
  • Topic clusters (group posts by dominant entity overlap)
  • Top-performing post (cross-reference with Ahrefs "Top pages")

4. Positioning and voice snapshot

For each competitor, scrape:

  • Home page
  • Pricing page (if public)
  • About / company page
  • One featured case study

From these, extract:

  • Primary claim (the one-sentence promise in the hero)
  • ICP language (who they say they're for)
  • Voice attributes (observed, not claimed — derive from sentence length, vocabulary, formality)
  • Proof strategy (logos, numbers, stories, awards)
  • Pricing model (free/freemium/quote/tiered — note if hidden)

5. Backlink profile (Ahrefs)

For each competitor, capture:

  • Top 20 referring domains by traffic
  • Top 20 pages by referring domains
  • Most common anchor texts
  • Recently acquired backlinks (last 30 days)

Look for patterns: guest posts, podcast mentions, roundups, free tools, data studies. These are the backlink plays the competitor is running right now.

6. Gap analysis

Combine everything into gap categories:

  • Keyword gaps — terms competitors rank for, user doesn't. Sorted by volume × relevance.
  • Topic gaps — topic clusters competitors cover heavily that the user under-covers.
  • Format gaps — formats competitors use that the user doesn't (e.g. 3 competitors have interactive calculators, user has none).
  • Backlink gaps — referring domains linking to ≥3 competitors but not to the user. These are realistic outreach targets.
  • Positioning gaps — unmet ICP segments or claims no one is making.

7. Strengths to defend

The inverse: where the user is ahead. Flag top 10 keywords where the user ranks top 3 and competitors are within striking distance — these need defense.

8. Write the report

Write to competitors/<YYYY-MM-DD>-report.md:

# Competitor Analysis — {own domain}

_Run: {YYYY-MM-DD}_
_Competitors analyzed: {n}_
_Depth: {fast/standard/deep}_

## Executive summary

- **Biggest gap to close:** {one line}
- **Biggest opportunity:** {one line}
- **Biggest threat:** {one line}
- **Top 3 recommended plays:** {bullets}

## Competitors at a glance

| Domain | DR | Organic traffic | Keywords | Ref domains | Posts/mo | Median word count | Primary claim |
|---|---|---|---|---|---|---|---|
| {domain} | 72 | 120k | 18k | 3.2k | 12 | 1,800 | {one line} |

## Per-competitor deep dive

### {domain}

**Positioning**
- Primary claim: {…}
- ICP language: {…}
- Voice: {observed attributes}
- Proof strategy: {…}
- Pricing: {…}

**SEO**
- DR / traffic / kw count
- Top 10 organic pages (table)
- New backlinks last 30 days: {n}

**Content**
- Cadence: {n}/mo
- Format mix: {breakdown}
- Topic clusters: {list}
- Best-performing post: [{title}]({url}) — {traffic}

**Recent plays** (backlink + content patterns from the last 30 days):
- {play 1}
- {play 2}

{repeat per competitor}

## Gap analysis

### Keyword gaps — top 30
| Keyword | Volume | KD | Competitors ranking | Recommendation |
|---|---|---|---|---|

### Topic gaps
- {cluster} — {n} competitors cover, 0 user posts. Priority: high.

### Format gaps
- {format} — used by {n} competitors.

### Backlink gaps — top 30 targets
| Referring domain | DR | Links to competitors | Outreach angle |

### Positioning gaps
- {observation}

## Strengths to defend

| Keyword | Our position | Closest competitor | Their trajectory |
|---|---|---|---|

## Recommended plays (90-day)

1. {play} — owner, effort, expected impact
2. …

## Sources

- Ahrefs metrics and gap analysis
- Firecrawl blog + positioning scrapes
- GSC / SE Ranking (if configured)
- Tavily/Exa brand mentions (if configured)

Also save raw data to competitors/<YYYY-MM-DD>-raw.json for future diffs.

9. Print summary

One block: number of competitors analyzed, biggest gap, biggest threat, report path.

Fallbacks

  • No Ahrefs: drop metrics block; use Firecrawl alone for content audit + positioning. Clearly mark the report as "content-only" and skip gap analysis that requires keyword data.
  • Competitor blocks scraping: fall back to Jina → Playwright; if all three fail, document which competitor was skipped and why.
  • Ahrefs content gap endpoint unavailable: compute gap manually from keyword lists (intersection minus own).
  • Deep depth times out: save partial results and continue.

Verification

  1. Report file exists with every competitor covered or explicitly marked as skipped.
  2. At-a-glance table has one row per competitor.
  3. At least one item in each of: keyword gaps, topic gaps, backlink gaps.
  4. Raw JSON file present alongside the report.
  5. Re-running in 30 days should allow diffing the two raw files to produce a progress delta.

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.