Claude Skill

conversion-rate-optimization

Optimize landing pages, forms, CTAs, and funnels - diagnosis, hypotheses, and test plans. Use when traffic exists but conversions lag.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_conversion-rate-optimization-e9c73a3.zip · 1 KB
Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/conversion-rate-optimization
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Conversion Rate Optimization (CRO)

Overview

CRO = removing friction and adding clarity where visitors already are. Diagnose before touching anything.

Landing page audit grid

Element Question
Headline does a stranger get the value in 5 seconds?
Subhead / hero who it's for + what changes for them
Proof logos, numbers, testimonials, cases near the claim they support
CTA one primary action, visible without scrolling, specific label
Friction form fields count, unclear pricing, dead ends
Objections are the top 3 objections answered on the page?
Speed / mobile loads fast, works on phone

Workflow

  1. Get data: where users drop (analytics), what they say (session notes, chat logs).
  2. Audit the page with the grid; fetch it with web_fetch for structure.
  3. Rank issues: high traffic × high friction first.
  4. Write hypotheses (growth-marketing experiment format) - copy changes usually beat design changes.
  5. Propose the test: A/B if traffic allows, before/after with a holdout period otherwise.
  6. Rewrite copy via copywriting-agent; measure and iterate.

Rules

  • Clarity beats persuasion tricks; specificity beats superlatives.
  • Never test tiny changes on tiny traffic - you'll never reach significance.
  • The form asks only for what sales actually uses.
Files (navin)
  • SKILL.md 1.6 KB
    ---
    name: conversion-rate-optimization
    description: Optimize landing pages, forms, CTAs, and funnels - diagnosis, hypotheses, and test plans. Use when traffic exists but conversions lag.
    metadata: {"navin":{"emoji":"🎚️","category":"marketing"}}
    ---
    
    # Conversion Rate Optimization (CRO)
    
    ## Overview
    
    CRO = removing friction and adding clarity where visitors already are. Diagnose before touching anything.
    
    ## Landing page audit grid
    
    | Element | Question |
    |---------|----------|
    | Headline | does a stranger get the value in 5 seconds? |
    | Subhead / hero | who it's for + what changes for them |
    | Proof | logos, numbers, testimonials, cases near the claim they support |
    | CTA | one primary action, visible without scrolling, specific label |
    | Friction | form fields count, unclear pricing, dead ends |
    | Objections | are the top 3 objections answered on the page? |
    | Speed / mobile | loads fast, works on phone |
    
    ## Workflow
    
    1. Get data: where users drop (analytics), what they say (session notes, chat logs).
    2. Audit the page with the grid; fetch it with `web_fetch` for structure.
    3. Rank issues: high traffic × high friction first.
    4. Write hypotheses (`growth-marketing` experiment format) - copy changes usually beat design changes.
    5. Propose the test: A/B if traffic allows, before/after with a holdout period otherwise.
    6. Rewrite copy via `copywriting-agent`; measure and iterate.
    
    ## Rules
    
    - Clarity beats persuasion tricks; specificity beats superlatives.
    - Never test tiny changes on tiny traffic - you'll never reach significance.
    - The form asks only for what sales actually uses.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related