Communitygithub.com

competitor-benchmarking-audit

Compare an audited landing page with competitors supplied by the user, focusing on positioning, offer, messaging, page structure, trust, CTA and experience. Use when asked for competitor benchmarking of landing pages.

What is competitor-benchmarking-audit?

competitor-benchmarking-audit is a Claude Code agent skill that compare an audited landing page with competitors supplied by the user, focusing on positioning, offer, messaging, page structure, trust, CTA and experience. Use when asked for competitor benchmarking of landing pages.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/ashokgmorais-cmd/Landing-Page-Intelligence/tree/HEAD/skills/competitor-benchmarking-audit

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Landing Page Competitor Benchmark Audit

Purpose

Run a standalone, evidence-based audit of the Competitor Benchmarking module for an existing landing page. The purpose is to diagnose the current experience and recommend practical improvements, not to build a replacement page.

How to run this skill independently

This skill audits only its named module. Do not assume any other module has been run. Begin with the user's request and supplied materials. If essential context is missing, ask only for information that materially affects this module; do not block on analytics or details that are unavailable. If the page URL is inaccessible, request screenshots, a recording, exported page text, or HTML. Work within the evidence available and label the scope limitation.

Useful context, when available: business/brand and industry; target audience and geography; page URL or assets; product/service and business model; primary conversion goal; offer/price; campaign or traffic source; brand constraints; relevant competitors; and analytics/testing data. Mark missing data Not provided or Unavailable rather than guessing. Distinguish business-provided claims from your own page observations.

Evidence and integrity rules

  • Separate Observed (directly visible/tested), Reported (provided by the business), Inference/Hypothesis (plausible but unverified), and Recommendation.
  • Tie important findings to a page section, element, source URL, supplied asset or test result. Quote exact copy only if it is available; otherwise label a paraphrase.
  • Explain what is present, why it matters to the relevant user/task, and what to change. Avoid treating every weakness as a proven conversion loss.
  • Do not invent business facts, results, analytics, guarantees, user research, certifications, or test outcomes. Avoid causal and uplift claims unless supported by valid experiments.
  • If only static screenshots or text are available, do not claim to have tested links, forms, responsive behavior, performance, keyboard access, or assistive technology.
  • Consider audience, offer, conversion goal, traffic context and accessibility needs where supplied. State assumptions and material limitations.

Priorities, confidence and scoring

Use priority P0 Critical (serious broken/usability/trust issue requiring immediate attention), P1 High (important, potentially consequential), P2 Medium (valuable after higher priorities), P3 Low (minor refinement/longer-term). Use confidence High (directly observable/measured), Medium (reasonable evidence with gaps), or Low (limited evidence or substantial assumptions).

Score applicable criteria from 0–5: 0 missing/broken/critically deficient; 1 very poor; 2 below expectations; 3 acceptable; 4 very good; 5 excellent. Mark unassessable items N/A and exclude them from the denominator. Calculate the module score as (points earned ÷ maximum applicable points) × 100, rounded to a whole number; state the numerator/denominator or list scored criteria. If nothing can reasonably be scored, report Not Evaluated, not 0. Do not treat this diagnostic score as an industry benchmark or a forecast of conversion performance.

Output format

Write a self-contained, client-ready Markdown audit with a title, audit scope/evidence basis, concise summary, strengths, prioritized findings/recommendations (prefer a table where useful), module score, overall evidence confidence, and limitations/next evidence needed. Keep advice specific and actionable. Do not produce a full multi-module report or score unless the user explicitly asks for one.

Module-specific review checklist

Compare only the target page and competitor pages the user identifies or authorizes. Examine headline/positioning, target audience, value proposition, offer and pricing presentation, benefits, CTA strategy, page structure, visual presentation, trust signals, UX, differentiation and conversion journey. Note date and access limits.

Required deliverable

Present a side-by-side comparison with source URLs and observed evidence; audited-page strengths; competitor advantages; competitive gaps; differentiation opportunities; recommendations, priority, confidence and a module score. Separate a visible page feature from a claim about commercial performance.

Module-specific guidance

Do not claim that competitors convert better, earn more, or are more effective without valid comparative data. Do not copy competitor wording or proprietary material. Treat inaccessible, dynamic or stale pages as limitations; do not silently substitute a different competitor.

Strategic diagnostic questions

  • Are these truly relevant alternatives for the same audience, need, price tier and decision context?
  • Which differences are category table stakes, and which could become a credible, defensible point of differentiation?
  • What can be observed from public page presentation, and what cannot be inferred about conversion, operations, or business performance?
  • Is the recommendation to imitate a feature, or to address an unmet customer need with a distinct position?

Final quality check

Before delivering, confirm that the review stayed within this module, every material conclusion is evidence-labelled, all recommendations are actionable and appropriately prioritized, unknowns remain unknown, N/A items were excluded from scoring, and the score calculation is correct. If the user asks for a full 12-module audit, explain that this skill covers one module and can be run alongside the other skills in this repository.

Individual skills in this repo

This repo contains 7 individual skills — each has its own dedicated page.

complete-audit

Conduct a comprehensive evidence-based landing-page audit across all 12 modules in one invocation, including UX, CRO, copy, CTAs, trust, mobile, performance, competitors, offer, message match, accessibility and an optimization roadmap. Use when asked for a full or complete 12-module landing-page audit.

content-copywriting-audit

Review landing-page messaging and copy for clarity, relevance, persuasion, structure, benefits, objections and CTA support; provide targeted replacement copy. Use when asked to critique or optimize copy on an existing landing page.

cro-audit

Evaluate conversion barriers and opportunities on an existing landing page, including goal clarity, friction, competing actions, forms, offer presentation and objection handling. Use when asked for a conversion-rate-optimization audit or conversion-focused review; do not promise uplift.

cta-audit

Audit the clarity, placement, consistency, accessibility and destination of calls to action on an existing landing page. Use when asked to evaluate or improve landing-page buttons, links, forms or conversion prompts.

message-match-audit

Assess whether an existing landing page matches the promise and expectations of its traffic sources, ads, campaign creative, email or search intent. Use when asked for message-match or traffic-alignment review.

performance-audit

Assess available technical performance evidence for an existing landing page, including Core Web Vitals, loading behavior, assets, scripts and likely bottlenecks. Use when asked to audit landing-page speed or performance.

ux-audit

Audit landing-page usability, information architecture, hierarchy, readability, navigation, cognitive load and visitor flow. Use when asked to assess or improve the user experience of an existing landing page, using a URL, screenshots, recordings or supplied page content.

Related Skills