Communitygithub.com

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.

What is cta-audit?

cta-audit is a Claude Code agent skill that 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.

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

Ask in your favorite AI

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

Documentation

Landing Page CTA Audit

Purpose

Run a standalone, evidence-based audit of the CTA 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

Inventory primary and secondary CTAs, including hero, mid-page, final and sticky/floating instances where observable. Assess wording, action clarity, visibility/contrast based on available evidence, size and target usability, placement, frequency, consistency, offer relevance, destination/functionality and mobile usability if actually inspected.

Required deliverable

Show each CTA/location and its intended action when known; identify problem, recommended wording/presentation, rationale, priority and confidence. Include the preferred primary CTA and a module score. Mark destination/functionality as unverified if not tested.

Module-specific guidance

Make requested commitment explicit and truthful (e.g., whether the next step is a demo, quote, checkout or download). Avoid manufactured urgency and vague labels. Do not assume a button works from appearance alone.

Strategic diagnostic questions

  • Does the CTA label describe the next real step and set an accurate expectation about what happens after the click?
  • Is the requested commitment proportional to the information and trust established so far?
  • Do repeated CTA instances create a coherent path, or do competing labels/destinations fragment intent?
  • Is the call to action discoverable and operable in the tested context without relying on color alone?

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 4 individual skills — each has its own dedicated page.

Related Skills