rediumvex/ai-marketing-claude · Archived

market-landing

Conversion rate optimization audit for a single landing page.

First seen May 17, 2026

Installation

$ npx skills add rediumvex/ai-marketing-claude --skill market-landing

Summary

  • Conversion rate optimization audit for a single landing page.
  • Invoke whenever the user says "landing page", "CRO", "why isn't this converting", "fix my landing page", or runs `/market landing <url>`.
  • Produces LANDING-CRO.md with a conversion score, a priority grid of issues (impact vs effort), and specific rewrites for the hero, social proof, CTAs, and form.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from rediumvex/ai-marketing-claude · top by installs.

npx skills add rediumvex/ai-marketing-claude

Browse all from rediumvex/ai-marketing-claude

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 44
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,784 B
  • docs SUMMARY.md 382 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Market Landing — CRO Analysis

Deliver a conversion-focused teardown of a single page. You are looking for the specific friction points and missing persuasion elements that cost the client money.

Workflow

  1. Fetch the page: python3 scripts/analyze_page.py <url>.
  2. Identify the page goal — trial signup, demo booking, purchase, lead capture, newsletter. If unclear, ask once.
  3. Walk the page as a first-time visitor would:

- 3-second test: Does the hero answer "what is this, who is it for, what do I do next"? - 30-second test: Is there enough to make me curious and reduce risk? - 3-minute test: Does the page answer every objection I'd have before converting?

The 10 CRO Dimensions (score each 0–10)

# Dimension Look for
1 Hero clarity Specific outcome + audience in the headline. Subhead elaborates.
2 Value proposition Differentiated, proven, not generic "best-in-class"
3 Primary CTA Value-driven text (not "Submit"), visible above fold, one dominant action
4 Secondary paths Clear but subordinated (e.g., "See pricing" below trial CTA)
5 Social proof Logos, testimonials with real names/photos, counts, ratings
6 Objection handling FAQ, comparison, guarantees, risk reversal
7 Form friction Minimum fields, clear purpose, progress signaling, inline validation
8 Trust architecture HTTPS, privacy link, security badges, compliance signals
9 Urgency / scarcity Honest, specific (not fake countdowns)
10 Visual hierarchy Eye flows top → CTA → proof → deeper info → CTA repeat

Priority Grid

Plot every issue on an impact × effort grid:

High impact │ QUICK WINS      │ MAJOR PROJECTS
            │ (do this week)  │ (plan this month)
            ├─────────────────┼─────────────────
Low impact  │ FILL-INS        │ SKIP
            │ (when bored)    │ (don't bother)
            └─────────────────┴─────────────────
              Low effort        High effort

Every finding goes in one cell. This is the most valuable part of the report — the client can see what to do first without asking.

Output: LANDING-CRO.md

# Landing Page CRO — [Brand]
**URL:** [url]  |  **Page goal:** [trial / demo / purchase / lead]
**Date:** [YYYY-MM-DD]

## Conversion Score: [X]/100

[2-sentence diagnosis: the biggest leak and the biggest quick win.]

## Dimension Scores
| # | Dimension | Score | Finding |
|---|---|---|---|
| 1 | Hero clarity | X/10 | ... |
...

## Priority Grid

### Quick Wins (high impact, low effort)
1. **[Fix name]** — Current: "[quoted copy]" → Proposed: "[new copy]". Expected lift: [reasoned estimate].
...

### Major Projects (high impact, high effort)
1. ...

### Fill-ins (low impact, low effort)
1. ...

## Hero Rewrite
**Current:**
> [exact quote of H1 + subhead + CTA]

**Proposed:**
> **[new H1]**
> [new subhead]
> [Primary CTA] · [Secondary link]

**Why:** [what changed and why it should convert better]

## CTA Audit
| CTA | Location | Current Text | Proposed Text | Reason |
|---|---|---|---|---|
| Primary | Hero | "Get Started" | "Start Free — No Card" | Risk reversal + specificity |

## Social Proof Gap
[What's present, what's missing, what to add first.]

## Form Friction
[Field-by-field audit if a form is present.]

## A/B Test Recommendations
Three tests ranked by expected impact, each with: hypothesis, variant, primary metric, minimum sample size (assuming baseline CR of X%).

Anti-patterns to flag

  • "Learn more" as the only CTA (no commitment signal)
  • Hero video that autoplays with sound
  • Forms asking for phone number before value is established
  • Testimonials without names or photos ("– Happy Customer")
  • Countdown timers that reset on reload (deceptive)
  • "Trusted by thousands" with no logos or numbers
  • Multiple competing CTAs above the fold
  • Legal disclaimers above the CTA (poisons conversion intent)

Quality Bar

Quote the actual copy before rewriting it. Never hallucinate a "current" headline. If the page has strengths, name them — an honest CRO audit protects what's working and fixes what isn't.