Page Cro logo

Page Cro

Organization
Humblytics
page-cro

Page-level conversion rate optimization. Audits any landing page, homepage, pricing page, or product page for conversion issues. Analyzes copy, layout, CTAs, social proof, objection handling, and user flow. Provides specific recommendations to improve conversion rate. Use when reviewing a page for conversion improvements, auditing landing pages, or optimizing specific page elements. Triggers: page audit, landing page review, conversion audit, page optimization, CTA optimization, landing page CRO.

Overview

PublisherHumblytics
Repositoryhumblytics-marketing-skills
Skill namepage-cro
Stars
85
Forks
18
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Humblytics on GitHub. Read the source before you install it.

Installation

Install the Page Cro AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Humblytics/humblytics-marketing-skills/tree/main/skills/page-cro
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Humblytics/humblytics-marketing-skills.git /tmp/humblytics-marketing-skills
mkdir -p .claude/skills
cp -r /tmp/humblytics-marketing-skills/skills/page-cro .claude/skills/page-cro
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Page Cro in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Page Cro on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Page Cro is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Page CRO

Purpose

Perform deep conversion audits on individual pages — landing pages, homepages, pricing pages, product pages, signup flows. Identifies specific conversion barriers and delivers actionable recommendations for copy, layout, CTAs, social proof, and user experience improvements.

When to Use

  • Auditing a landing page before or after launch
  • Reviewing a pricing page for conversion optimization
  • Improving a homepage that has high traffic but low conversion
  • Optimizing a signup or onboarding flow
  • Reviewing a page that has declining conversion rates
  • Preparing recommendations before an A/B test

Before You Start

  1. Get the page URL or content — Either a live URL, screenshot, or the page code/copy
  2. Understand the page goal — What is the single most important action a visitor should take?
  3. Know the audience — Who lands on this page? What brought them here?
  4. Current performance — If available, get conversion rate, bounce rate, time on page, scroll depth from Humblytics
  5. Traffic sources — Where does traffic come from? This affects messaging expectations.
  6. Look for context — Check project docs for brand, product, and competitive positioning

The Page CRO Audit Framework

1. First Impression (0-5 seconds)

The most critical window. Within 5 seconds, a visitor decides to stay or leave.

Check:

  • Is the headline clear and specific? Does it communicate the value proposition in under 10 words?
  • Does the subheadline explain what the product does and for whom?
  • Is the CTA visible above the fold without scrolling?
  • Is there visual hierarchy? Does the eye know where to go?
  • Does the page match the traffic source? (Ad copy -> landing page message match)
  • Is the page loading fast? (>3 seconds kills conversion)

Common issues:

  • Headline is clever instead of clear
  • No CTA above the fold
  • Too many competing elements
  • Stock photography that says nothing
  • Message mismatch with the ad or link that brought them here

2. Value Proposition Clarity

Check:

  • Can a visitor explain what you do after reading the hero section?
  • Are benefits stated, not just features?
  • Is the "so what?" answered for every claim?
  • Is there specificity? (numbers, timeframes, outcomes)
  • Is the unique mechanism clear? (why you, not competitors)

The Clarity Test: Show the hero section to someone unfamiliar with the product for 5 seconds. Can they answer:

  1. What does this product do?
  2. Who is it for?
  3. Why should I care?

3. CTA Analysis

Check:

  • Is there one primary CTA per page section?
  • Does the CTA text describe the outcome, not the action? ("Start saving time" > "Sign up")
  • Is the CTA visually prominent? (contrast, size, whitespace)
  • Is the CTA repeated at logical points throughout the page?
  • Is the commitment level appropriate? (free trial vs demo vs purchase)
  • Is there a secondary CTA for those not ready? (learn more, see demo)

CTA copy hierarchy (from lowest to highest friction):

  1. "See how it works" — informational, lowest commitment
  2. "Start free trial" — action, moderate commitment
  3. "Get started free" — action, moderate commitment
  4. "Buy now" / "Subscribe" — transactional, highest commitment

Match CTA friction to audience awareness level.

4. Social Proof Audit

Check:

  • Are there customer testimonials? Are they specific and outcome-focused?
  • Are there logos of recognizable customers or press mentions?
  • Are there quantified results? ("Increased conversions by 34%")
  • Is social proof placed near the CTA? (reduces friction at decision point)
  • Are testimonials attributed? (name, company, photo)
  • Is there proof of scale? (number of customers, reviews, usage stats)

Social proof hierarchy (most to least persuasive):

  1. Case studies with specific ROI numbers
  2. Named testimonials with photos from recognizable companies
  3. Aggregate metrics ("10,000+ teams use Humblytics")
  4. Star ratings and review counts
  5. Logo walls
  6. Generic unnamed testimonials

5. Objection Handling

Every visitor has objections. The page must preemptively address them.

Common objections and how to handle:

ObjectionPage Element
"Is this worth the price?"ROI calculator, pricing comparison, money-back guarantee
"Will this work for me?"Case studies from similar companies, segment-specific proof
"Is this hard to set up?""Get started in 5 minutes", setup walkthrough, no-code messaging
"What if I don't like it?"Free trial, money-back guarantee, cancel anytime
"Is my data safe?"Security badges, compliance certifications, privacy messaging
"Why not [competitor]?"Comparison table, unique differentiators

Check:

  • Are the top 3-5 objections addressed on the page?
  • Is there a FAQ section targeting common concerns?
  • Are guarantees and risk-reversal elements present?
  • Is the objection handling placed before the final CTA?

6. Page Structure and Flow

The ideal page flow:

Hero (value prop + CTA)
↓
Social proof (logos or key metric)
↓
Problem agitation (why status quo is painful)
↓
Solution (how your product solves it)
↓
Features/Benefits (3-5 key capabilities)
↓
Social proof (detailed testimonials/case studies)
↓
Pricing or offer details
↓
Objection handling (FAQ)
↓
Final CTA

Check:

  • Does the page follow a logical narrative arc?
  • Is there visual variety between sections? (text, images, videos, graphics)
  • Are sections the right length? (not too dense, not too sparse)
  • Is the page length appropriate for the offer complexity?
  • Are there clear visual dividers between sections?
  • Does the page end with a strong CTA, not just fade out?

7. Copy Quality

Check:

  • Is the copy scannable? (short paragraphs, bullet points, bold key phrases)
  • Is it written in the customer's language, not internal jargon?
  • Are benefits tied to outcomes? ("Save 10 hours/week" > "Automated reporting")
  • Is there specificity? ("34% increase" > "significant improvement")
  • Does the tone match the audience? (enterprise = professional, startup = casual)
  • Is there unnecessary copy that could be cut?

The "So What?" test: After every claim, ask "so what?" If the answer is not self-evident, the copy needs to go one level deeper into the benefit.

8. Mobile Experience

Check:

  • Is the CTA visible and tappable on mobile without scrolling?
  • Is text readable without zooming?
  • Are forms usable on mobile? (appropriate input types, large tap targets)
  • Do images and videos display correctly?
  • Is page load time fast on mobile connections?
  • Are horizontal scroll issues absent?

9. Trust and Credibility

Check:

  • Professional design (no amateur red flags)
  • Working links and no broken images
  • Consistent branding
  • Clear company identity (who is behind this product?)
  • Privacy policy and terms accessible
  • Secure checkout indicators if applicable

10. Technical Performance

Check:

  • Page loads in under 3 seconds
  • No layout shift during loading (CLS)
  • Images are optimized and lazy-loaded
  • No JavaScript errors in console
  • Forms submit correctly
  • Analytics tracking is firing properly

Output Format

Present the audit as:

  1. Page Score — Overall conversion readiness (1-10) with one-line summary
  2. Critical Issues — Must-fix items that are likely hurting conversion now (top 3)
  3. High-Impact Improvements — Changes that would meaningfully improve conversion (3-5 items)
  4. Quick Wins — Small changes that can be made immediately (3-5 items)
  5. Detailed Findings — Section-by-section analysis with specific recommendations
  6. Rewritten Copy — If copy is the main issue, provide improved versions
  7. Next Steps — Prioritized action plan

For each finding, include:

  • What: The specific issue
  • Where: Page section or element
  • Why it matters: Impact on conversion
  • Recommendation: Specific fix
  • Priority: Critical / High / Medium / Low

Related Skills

  • copywriting — Rewrite page copy based on audit findings
  • ab-test-generator — Create A/B tests from audit recommendations
  • cro-optimizer — Analyze the page within the broader funnel context
  • ad-expert — Ensure message match between ads and landing pages

Shared Frameworks (REQUIRED reading)

Before recommending changes to a page, anchor against the shared primitives in skills/_shared/.

  • _shared/frameworks/preflight-checklist.md — verify URL, time range, conversion goal, vertical, and audience awareness level before producing findings. Generic page audits without preflight context produce generic recommendations.
  • _shared/frameworks/anti-patterns.md — critical for page audits. Read BEFORE recommending the canonical "best practice" version of any element:
    • Customer logos: LOST in most DoWhatWorks A/B tests when prerequisites unmet (segment match, brand recognition)
    • Hero video: net-negative on mobile due to 1s = -7% / 3s = -20% load penalty (Device Magic image-slider beat video by +35%)
    • Trust badges: Baymard's homemade padlock outperformed branded SSL seals — brand recognition drives lift, not certification
    • Generic testimonials (stock photos, anonymized "satisfied customer") actively hurt trust
    • "Free" in CTA copy: Unbounce platform-wide null/negative — context-dependent
  • _shared/frameworks/ice-confidence-rubric.md — anchor each finding's Confidence score on _shared/benchmarks/patterns.json evidence quality, not familiarity.
  • _shared/benchmarks/patterns.json — when flagging a friction or proposing a fix, match it to a pattern_id and cite the lift range. Categories most relevant to page-cro: social_proof, trust_signal, cta, headline, above_fold, form.

Frequently asked questions

What does the Page Cro AI skill do?

Page-level conversion rate optimization. Audits any landing page, homepage, pricing page, or product page for conversion issues. Analyzes copy, layout, CTAs, social proof, objection handling, and user flow. Provides specific recommendations to improve conversion rate. Use when reviewing a page for conversion improvements, auditing landing pages, or optimizing specific page elements. Triggers: page audit, landing page review, conversion audit, page optimization, CTA optimization, landing page CRO.

Why use Page Cro on TypingMind?

Because you install it once and use it with any model. Page Cro is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Page Cro in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Humblytics/humblytics-marketing-skills/tree/main/skills/page-cro. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Page Cro?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Page Cro?

As many as you like. As long as a model supports skills, you can use Page Cro with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Page Cro AI skill free?

Yes. It is published on GitHub by Humblytics under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇