Page CRO

Conducts detailed audits of landing pages to identify conversion blockers and recommends prioritized fixes based on proven CRO principles and benchmarks.

Security Scan

The skill's requirements and instructions are coherent with a landing-page CRO audit: it is instruction-only, requests no credentials, and does not install software — though some parts are vague about data sources and runtime capabilities.

Purpose & Capability

Name and description (landing page CRO audits) match the SKILL.md steps (fetch page, run heuristics, prioritise fixes). The skill does not request unrelated credentials, binaries, or config paths.

Instruction Scope

The instructions are high-level and stay within the CRO domain, but they are vague about runtime behavior: 'Fetch URL and analyse' and 'Benchmark against industry conversion rates' do not specify how pages are fetched (static HTML vs. JS-rendered), what benchmark data sources are used, or where results/benchmarks are obtained. This grants the agent broad discretion to access arbitrary URLs and external benchmark sources when invoked.

Install Mechanism

There is no install spec and no code files — nothing will be written to disk or installed. This is the lowest-risk install profile.

Credentials

The skill requests no environment variables, credentials, or config paths. Nothing appears disproportionate to a CRO audit.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request permanent presence or elevated privileges, and it does not modify system or other-skill configurations.

Scan Findings in Context

[no-findings] expected: The static regex scanner had no code to analyze (instruction-only skill), which is expected for a skill composed solely of runtime instructions.

Assessment

This skill appears to do what it says, but consider these before installing: 1) The skill will need to fetch whatever URL you ask it to audit — avoid submitting private or internal URLs unless you trust the agent. 2) The SKILL.md is vague about benchmark sources and how dynamic pages will be rendered; ask the publisher (or test) how industry conversion rates are sourced and whether the agent executes JavaScript or only analyses raw HTML. 3) Because it can access arbitrary URLs when invoked, be mindful of sensitive data you paste into prompts. 4) No credentials or installs are required, so there is no immediate credential-exfiltration signal — still review outputs for accidentally disclosed content. If you need stricter controls, run audits on a sandboxed agent or provide only non-sensitive public URLs.

Page CRO Skill

Trigger

Audit any landing/product page for conversion blockers.

Trigger phrases: "audit this page", "conversion audit", "why isn't this converting", "page CRO", "landing page review"

Process

1. Load page: Fetch URL and analyse structure, copy, layout, CTAs
2. Heuristic evaluation: Check against 40+ conversion principles
3. Identify blockers: Categorise as critical, warning, or opportunity
4. Benchmark: Compare against industry conversion rates
5. Recommend: Specific, prioritised fixes with expected impact

Audit Framework

Above the Fold (most critical)

• Value proposition clear within 5 seconds
• Primary CTA visible without scrolling
• Headline matches visitor intent / ad copy
• No competing CTAs or distractions

Trust Signals

• Social proof present (testimonials, logos, numbers)
• Security indicators (SSL, payment badges)
• Risk reducers (guarantee, free trial, no credit card)

Copy

• Benefit-led, not feature-led
• Specific numbers over vague claims
• Addresses primary objection
• Scannable (subheadings, bullets, short paragraphs)

CTA

• Action-oriented button text (not "Submit")
• Contrasting colour
• Repeated at logical intervals
• Microcopy addresses friction ("No credit card required")

Mobile

• Touch-friendly tap targets (44px+)
• No horizontal scroll
• CTA accessible on mobile viewport
• Images load quickly

Output Format

# CRO Audit: [URL]

## Conversion Score: [X/100]

## Critical (fix today)
1. [Issue] → [Specific fix] — Expected impact: [High]

## Warnings (fix this week)
1. [Issue] → [Specific fix] — Expected impact: [Medium]

## Opportunities (test these)
1. [Opportunity] → [How to test]

## Recommended A/B Tests
1. [Test idea] — [Hypothesis] — [Estimated lift]