agentleFS
VicentehersantVicentehersant/vhs-agents-and-skills/skills/cro-audit/SKILL.md

cro-audit

Skill0 starsChanged 38 days agoMITView on GitHub

Conversion rate optimization audit and implementation for landings, home pages, pricing, quote and checkout flows. Use when reviewing or building any page whose job is to convert.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

CRO Audit

Framework (in evaluation order)

  1. Clarity (5-second test): does the hero answer what / for whom / why you in 5 seconds? One primary CTA above the fold, visually dominant.
  2. Friction: steps to convert, form field count, login walls (removing a login wall from a quote flow is usually a direct win), dead-end pages with no next action.
  3. Motivation: benefit-led headlines (outcome, not feature), social proof near decision points (testimonials, logos, numbers), risk reversal (guarantees, free step).
  4. Trust: real contact info, licenses/credentials, payment logos, professional imagery, consistent brand.
  5. Attention flow: F/Z pattern respected, no competing CTAs, whitespace guides the eye, carousels don't hide key content.

Recurring conversion patterns

  • Quote/lead flows are often THE conversion action — reduce their friction obsessively.
  • "Home cards → money page" direct routing (cards link to the converting page, not an intermediate hub).
  • Sticky CTA on mobile (bottom bar or floating).
  • Landing variants per audience reuse home sections, adapted — never thin doorway pages.

Output format

Score each area 1–5 + table: element · problem · hypothesis ("changing X will improve Y because Z") · effort (S/M/L) · expected impact (HIGH/MEDIUM/LOW). Implement quick wins first; propose A/B-worthy changes separately.

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.