agentleFS
Eugenevdm01Eugenevdm01/eugenes-meta-agent/skills/landing-page-cro-analyst/SKILL.md

landing-page-cro-analyst

Skill4 starsChanged 6 months agoMITView on GitHub

Review landing page structure and identify test ideas. Compare split-test variants to improve conversion rates. Use when diagnosing low page conversion rates or planning A/B tests.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When diagnosing low landing page conversion rates despite high ad CTR.

    line 12
  2. Distinctive:

    When planning A/B tests for landing pages.

    line 13
  3. Distinctive:

    When reviewing a new landing page before launch.

    line 14
  4. Distinctive:

    When evaluating the performance of different page variants.

    line 15
  5. Distinctive:

    Check Message Match: Ensure the page aligns with the ad copy that drove the traffic.

    line 27
  6. Distinctive:

    Evaluate Trust Elements: Look for social proof, testimonials, guarantees, and security badges.

    line 29
  7. Distinctive:

    Analyze Mobile Usability: Ensure the page is optimized for mobile devices (e.g., readable text, clickable buttons).

    line 30
  8. Distinctive:

    If the page is fundamentally broken (e.g., form doesn't submit, page doesn't load), escalate immediately as a critical issue.

    line 47
  9. Distinctive:

    If the offer is weak or unclear, request clarification before suggesting minor tweaks.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Landing Page CRO Analyst

Purpose

Review landing page structure and identify test ideas. Compare split-test variants to improve conversion rates, reduce friction, and build trust.

When to Use This Skill

  • When diagnosing low landing page conversion rates despite high ad CTR.
  • When planning A/B tests for landing pages.
  • When reviewing a new landing page before launch.
  • When evaluating the performance of different page variants.

Inputs Required

  • Landing page URL or copy/design mockups.
  • Current conversion rate data (if available).
  • Traffic source and audience intent (e.g., cold Meta ads vs. warm email list).
  • The primary goal of the page (e.g., lead generation, sales, webinar registration).

Step-by-Step Workflow

  1. Analyze the Above-the-Fold Content: Evaluate the headline clarity, subheadline, and primary CTA. Does it immediately communicate value?
  2. Review the Offer Strength: Is the offer compelling and clearly articulated?
  3. Check Message Match: Ensure the page aligns with the ad copy that drove the traffic.
  4. Assess Friction Points: Identify any unnecessary form fields, confusing navigation, or slow load times (if visible).
  5. Evaluate Trust Elements: Look for social proof, testimonials, guarantees, and security badges.
  6. Analyze Mobile Usability: Ensure the page is optimized for mobile devices (e.g., readable text, clickable buttons).
  7. Develop Test Ideas: Formulate hypotheses for A/B testing based on identified weaknesses.

Output Format

Provide a structured CRO review containing:

  • What is working: Elements that are strong and should be kept.
  • What is hurting conversions: Identified friction points or weak elements.
  • What should be tested next: Prioritized list of A/B test ideas with hypotheses.
  • What should be changed immediately: Critical errors or obvious improvements.
  • What should not be changed yet: Elements that need more data before making a decision.

Decision Rules

  • Always diagnose before recommending changes. Do not guess. Use evidence from performance data.
  • Prioritize recommendations by highest impact, lowest effort, fastest feedback loop, and strongest expected lift.
  • Label recommendations as urgent, high priority, medium priority, low priority, or monitor only.

Escalation Rules

  • If the page is fundamentally broken (e.g., form doesn't submit, page doesn't load), escalate immediately as a critical issue.
  • If the offer is weak or unclear, request clarification before suggesting minor tweaks.

Templates & Resources

  • checklists/cro-audit.md: Checklist for reviewing landing pages.
  • templates/cro-report.md: Template for presenting CRO findings and test ideas.

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.