agentleFS
oegeyilmaz9oegeyilmaz9/seo-aeo-geo-ultimate/skills/seo-competitor-pages/SKILL.md

seo-competitor-pages

Skill6 starsChanged 3 months agoApache-2.0View on GitHub

Use when researching, briefing, or drafting fair comparison, versus, or alternative pages using dated, attributable product evidence; avoid unsupported superiority claims, copied competitor content, and artificial SEO comparisons.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-image-gen, seo-sxo and 8 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.
  • timruebenachSkill

    seo-image-gen

    AI image generation for SEO assets: OG/social preview images, blog hero images, schema images, product photography, infographics. Powered by Gemini via nanobanana-mcp. Requires banana extension installed. Use when user says \"generate image\", \"OG image\", \"social preview\", \"hero image\", \"blog image\", \"product photo\", \"infographic\", \"seo image\", \"create visual\", \"image-gen\", \"favicon\", \"schema image\", \"pinterest pin\", \"generate visual\", \"banner\", or \"thumbnail\".

    Also in 16 projects that use this

  • timruebenachSkill

    seo-sxo

    Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".

    Also in 17 projects that use this

  • indranilbanerjeeSkill

    seo-drift

    Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"

    Also in 17 projects that use this

  • mangollcSkill

    seo-backlinks

    Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.

    Also in 16 projects that use this

  • +6 more from timruebenach

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read markdown-delivery-contract.md for every task.

    line 10
  2. Distinctive:

    Create useful comparison-page plans and reviewable drafts for a reader making a real choice.

    line 17
  3. Very specific:

    Read references/comparison-evidence-protocol.md before drafting factual comparisons.

    line 19
  4. Distinctive:

    If a competitor fact cannot be verified or may have changed, label it unknown, omit it, or ask for an approved source.

    line 25
  5. Distinctive:

    Choose fair structure: Use methodology, use-case guidance, eligibility/constraints, and transparent comparison rows.

    line 31
  6. Distinctive:

    Draft with attribution: Write factual copy in neutral language, preserve product/brand names correctly, cite sources where readers need …

    line 32
  7. Distinctive:

    Do not claim “best,” “cheaper,” “more secure,” “#1,” migration ease, feature parity, or performance superiority without scoped support and …

    line 37
  8. Distinctive:

    Never fabricate rankings, review aggregates, customer quotes, pricing, availability, integrations, or competitor weaknesses.

    line 38
  9. Distinctive:

    Do not use SEO demand as permission to create a misleading or thin comparison page.

    line 39
  10. Distinctive:

    Do not imply search ranking, AI citation, referral, or conversion outcomes from publishing the page.

    line 40

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

Comparison and Alternative Pages

Markdown delivery contract

Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats.

Lane outputs: comparison-research.md; comparison-decisions.md (combine small related steps with stable section links). Keep comparison Markdown and HTML claims identical, source-dated, attributable and fair. Map comparison intent to a substantive owner; do not copy competitors or invent relative product capabilities.

Purpose

Create useful comparison-page plans and reviewable drafts for a reader making a real choice. The page should make its evidence, scope, and trade-offs clear; it is not a vehicle for unverified claims or competitor disparagement.

Read references/comparison-evidence-protocol.md before drafting factual comparisons.

Input gate

Require the reader/use case, entities/products compared, locale, comparison date, company-owned facts, independently verifiable competitor sources, the user’s actual alternatives/criteria, legal/brand constraints, and review owner. Quote or summarize only what the cited source supports and preserve price, availability, plan, market, and feature scope.

If a competitor fact cannot be verified or may have changed, label it unknown, omit it, or ask for an approved source. Never “complete” a table from memory or an AI answer.

Workflow

  1. Frame reader value. State who is deciding, what decision they need to make, and why a comparison is useful beyond a brand-versus-brand keyword.
  2. Build a fact matrix. Separate company facts, competitor facts, common capabilities, meaningful differences, limitations, and subjective fit. Every material row gets a source and “as of” date/scope.
  3. Choose fair structure. Use methodology, use-case guidance, eligibility/constraints, and transparent comparison rows. Include alternatives that may genuinely fit the reader; do not hide disqualifying conditions.
  4. Draft with attribution. Write factual copy in neutral language, preserve product/brand names correctly, cite sources where readers need them, and distinguish opinion from verified fact. Do not copy a competitor’s copy, table, screenshots, reviews, or trademarks beyond authorized/legally reviewed use.
  5. Review and release plan. Require product, legal/brand, factual, localization, and accessibility review as appropriate. Send site implementation through seo-content and seo-action-plan.

Guardrails

  • Do not claim “best,” “cheaper,” “more secure,” “#1,” migration ease, feature parity, or performance superiority without scoped support and approval.
  • Never fabricate rankings, review aggregates, customer quotes, pricing, availability, integrations, or competitor weaknesses.
  • Do not use SEO demand as permission to create a misleading or thin comparison page.
  • Do not imply search ranking, AI citation, referral, or conversion outcomes from publishing the page.

Formal evidence handoff

When this work needs a cross-team, approval-ready plan, package evidence-bound findings as an immutable seo-findings.json bundle using the checked-out suite contract. Let <suite-root> mean ${CLAUDE_PLUGIN_ROOT} in Claude Code. In Codex, read .seo-suite-runtime.json beside this SKILL.md when present and use its suite_root value; otherwise use the absolute repository checkout. Keep every referenced capture/source below raw/, retain declined claims and limitations, and run python "<suite-root>/scripts/validate_seo_findings.py" validate-findings <bundle>/seo-findings.json --bundle <bundle>. Send only a passing bundle to seo-action-plan; otherwise label the handoff provisional.

Output

Return a source/date-stamped fact matrix, reader-oriented outline, claim/approval ledger, draft options if requested, and implementation/review handoff. Unverified rows are explicit gaps, not recommendations.

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.