Systems Lab

Agent skill

gtmos-marketing-cro

Raise conversion on marketing pages and forms -- homepage, landing, pricing, feature and demo-request pages -- with a structured audit, prioritized fixes and test ideas, measured with real tracking data.

activeSelf-containedInstructions only1,099 words

Filed under Analytics and reporting.

From ay-automate/gtmos-skills · 107 skill entries · 0 · pushed 2026-11-02

What it does when it runs

Raise conversion on marketing pages and forms -- homepage, landing, pricing, feature and demo-request pages -- with a structured audit, prioritized fixes and test ideas, measured with real tracking data. With GTM OS connected it reads site tracking and sources (tracking.activity, tracking.sources), inbound form performance, and proposes page changes through the SEO & GEO engine for approval. Use for \"CRO\", \"conversion rate\", \"landing page optimization\", \"this page isn't converting\", \"improve signups\", \"form conversion\", \"demo requests are low\".

Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about gtmos-marketing-cro

Opens your assistant with this page's recorded context. Check the linked sources before relying on it.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/ay-automate/gtmos-skills.git /tmp/gtmos-skills
git -C /tmp/gtmos-skills sparse-checkout set "skills/gtmos-marketing-cro"
mkdir -p ~/.claude/skills/gtmos-marketing-cro
cp -R "/tmp/gtmos-skills/skills/gtmos-marketing-cro/." ~/.claude/skills/gtmos-marketing-cro/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 107 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add ay-automate/gtmos-skills
/plugin

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from ay-automate/gtmos-skills/blob/86780d2f545cdc0a1de971917aa04b41bb0b3ccd/skills/gtmos-marketing-cro/SKILL.md, which is licensed MIT (skill frontmatter). 1,099 words, 28 headings.

Conversion rate optimization

Part of GTM OS Skills. Adapted from cro in coreyhaines31/marketingskills (MIT, Copyright (c) 2025 Corey Haines). Changed for GTM OS: the operating section below, rewritten cross-references and tool pointers. Notices: THIRD-PARTY-NOTICES.md (installed beside the skills as THIRD-PARTY-NOTICES.md).

With GTM OS connected

Rules (GTMOS-RULES.md). Read policy.get_dry_mode first; in dry mode every effect stops at a draft. E-class operations are proposed and a different person approves them; never approve your own proposal. Numbers come only from operation results, named with the operation. Claims about results, customers or metrics must be backed by active proof from proof.list.

1. Measure. tracking.site.get Q (is the site tracked), tracking.sources Q and tracking.activity Q for visits and conversions by source, inbound form submissions from the webform connector as records and signals. Quote rates with their sample; small samples get "not enough data yet".

2. Audit. Apply the method below to the page. Copy suggestions pass brand.check_text; proof on the page comes from proof.list.

3. Change and test. Page changes for tracked pages go through seo_geo.publish_content_change E (approved by a person). Test design: gtmos-analytics-experiments.

Without GTM OS

Use the user's analytics (GA4 or similar) for the page's traffic and conversion, and follow the method below.


You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.

Reference Routing

Load the matching reference before recommending changes in these areas. Use the page analysis below for the initial diagnosis; references supply the detailed recommendations.

User intentLoadCovers
Lead, contact, demo, or quote form abandonment; fields, validation, mobile formsform.mdField decisions, form layouts, errors, trust, measurement, and form-specific experiments
Experiment ideas for a homepage, pricing, demo, landing, feature, or resource pageexperiments.mdHypotheses organized by page type and cross-page tests; use gtmos-analytics-experiments for test design and measurement

Initial Assessment

Check for context first: With GTM OS connected, read the org definitions named in With GTM OS connected above before asking anything. Without it, read .agents/product-marketing.md (or .claude/product-marketing.md) if it exists; gtmos-marketing-positioning writes that file. Ask only for what neither covers.

Before providing recommendations, identify:

  1. Page Type: Homepage, landing page, pricing, feature, blog, about, other
  2. Primary Conversion Goal: Sign up, request demo, purchase, subscribe, download, contact sales
  3. Traffic Context: Where are visitors coming from? (organic, paid, email, social)

CRO Analysis Framework

Analyze the page across these dimensions, in order of impact:

1. Value Proposition Clarity (Highest Impact)

Check for:

  • Can a visitor understand what this is and why they should care within 5 seconds?
  • Is the primary benefit clear, specific, and differentiated?
  • Is it written in the customer's language (not company jargon)?

Common issues:

  • Feature-focused instead of benefit-focused
  • Too vague or too clever (sacrificing clarity)
  • Trying to say everything instead of the most important thing

2. Headline Effectiveness

Evaluate:

  • Does it communicate the core value proposition?
  • Is it specific enough to be meaningful?
  • Does it match the traffic source's messaging?

Strong headline patterns:

  • Outcome-focused: "Get [desired outcome] without [pain point]"
  • Specificity: Include numbers, timeframes, or concrete details
  • Social proof: "Join 10,000+ teams who..."

3. CTA Placement, Copy, and Hierarchy

Primary CTA assessment:

  • Is there one clear primary action?
  • Is it visible without scrolling?
  • Does the button copy communicate value, not just action?
    • Weak: "Submit," "Sign Up," "Learn More"
    • Strong: "Start Free Trial," "Get My Report," "See Pricing"

CTA hierarchy:

  • Is there a logical primary vs. secondary CTA structure?
  • Are CTAs repeated at key decision points?

4. Visual Hierarchy and Scannability

Check:

  • Can someone scanning get the main message?
  • Are the most important elements visually prominent?
  • Is there enough white space?
  • Do images support or distract from the message?

5. Trust Signals and Social Proof

Types to look for:

  • Customer logos (especially recognizable ones)
  • Testimonials (specific, attributed, with photos)
  • Case study snippets with real numbers
  • Review scores and counts
  • Security badges (where relevant)

Placement: Near CTAs and after benefit claims

6. Objection Handling

Common objections to address:

  • Price/value concerns
  • "Will this work for my situation?"
  • Implementation difficulty
  • "What if it doesn't work?"

Address through: FAQ sections, guarantees, comparison content, process transparency

7. Friction Points

Look for:

  • Too many form fields
  • Unclear next steps
  • Confusing navigation
  • Required information that shouldn't be required
  • Mobile experience issues
  • Long load times

Output Format

Structure your recommendations as:

Quick Wins (Implement Now)

Easy changes with likely immediate impact.

High-Impact Changes (Prioritize)

Bigger changes that require more effort but will significantly improve conversions.

Test Ideas

Hypotheses worth A/B testing rather than assuming.

Copy Alternatives

For key elements (headlines, CTAs), provide 2-3 alternatives with rationale.


Page-Specific Frameworks

Homepage CRO

  • Clear positioning for cold visitors
  • Quick path to most common conversion
  • Handle both "ready to buy" and "still researching"

Landing Page CRO

  • Message match with traffic source
  • Single CTA (remove navigation if possible)
  • Complete argument on one page

Pricing Page CRO

  • Clear plan comparison
  • Recommended plan indication
  • Address "which plan is right for me?" anxiety

Feature Page CRO

  • Connect feature to benefit
  • Use cases and examples
  • Clear path to try/buy

Blog Post CRO

  • Contextual CTAs matching content topic
  • Inline CTAs at natural stopping points

Experiment Ideas

When recommending experiments, consider tests for:

  • Hero section (headline, visual, CTA)
  • Trust signals and social proof placement
  • Pricing presentation
  • Form optimization
  • Navigation and UX

For comprehensive experiment ideas by page type: See references/experiments.md


Task-Specific Questions

  1. What's your current conversion rate and goal?
  2. Where is traffic coming from?
  3. What does your signup/purchase flow look like after this page?
  4. Do you have user research, heatmaps, or session recordings?
  5. What have you already tried?

Related Skills

  • gtmos-content-copywriting: If the page needs a complete copy rewrite
  • gtmos-analytics-experiments: To properly test recommended changes

Form Optimization

When enrichment controls the next step after a lead form, use the revops inbound-routing playbook: preserve valid submissions, bound the lookup wait, and provide a useful fallback when qualification is unknown.

For detailed form CRO guidance — including field optimization, multi-step forms, error handling, and form-specific experiments — see references/form.md.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what gtmos-marketing-cro does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.

Build my GTM engine

Tell us what you want to improve. Fedor reviews the workflow and replies by email when there is a useful fit.

Fedor reviews every request personally. If there is a useful fit, he will reply by email.