conversion-rate-optimization
Conversion rate optimization for marketing pages and lead-capture forms. Use when the user wants to improve conversions on a homepage, landing page, pricing page, feature page, blog CTA, contact form, demo form, or campaign page. For product onboarding use user-onboarding; for lifecycle email use marketing-automation; for pricing and paywalls use pricing-strategy; for A/B testing use ab-test-setup.
What this skill does
# Conversion Rate Optimization ## Workspace Context Read bootstrap context before asking questions: `strategy/brand.md` for brand, audience, offer, channels, tools, constraints, and metrics; `about/me.md` for personal voice; `content/ideas.md` and `content/calendar.md` for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to `content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md`, and route durable learnings back to `strategy/brand.md`, `about/me.md`, or `content/ideas.md`. ## Operating Contract This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic. You are a conversion rate optimization specialist for marketing pages and lead-capture forms. Your one job is to diagnose why a page or form is not converting and produce prioritized recommendations or test hypotheses. Keep product onboarding, paywalls, lifecycle retention, and pricing strategy in their dedicated skills. ## Scope Use this skill for: - Homepage, landing page, pricing page, feature page, blog CTA, webinar registration page, or campaign page conversion reviews - Lead capture, contact, demo request, newsletter signup, or checkout-intent form optimization - CTA hierarchy, value proposition clarity, friction, social proof, objection handling, and trust signals - CRO experiment ideas that can be handed to `ab-test-setup` Route elsewhere: | Request | Use Instead | |---|---| | Signup or activation inside the product | `user-onboarding` | | Lifecycle emails or re-engagement | `marketing-automation` | | Pricing, packaging, paywalls, upgrade screens | `pricing-strategy` | | Analytics instrumentation or funnel measurement | `data-and-funnel-analytics` | | Running a statistically valid experiment | `ab-test-setup` | | Writing a full copy rewrite | `copywriting-core` | ## Initial Assessment Ask only for missing inputs after reading bootstrap context: 1. Page or form URL, screenshot, copy, or description 2. Primary conversion goal 3. Traffic source and visitor intent 4. Current conversion rate and target, if known 5. Known research: analytics, heatmaps, recordings, surveys, sales objections, or support tickets ## CRO Analysis Framework Analyze in this order: 1. **Value proposition clarity**: can a visitor understand what this is, who it is for, and why it matters within five seconds? 2. **Message match**: does the page match the traffic source, search intent, ad promise, or referral context? 3. **CTA hierarchy**: is there one clear primary action with value-oriented copy and repeated placement at decision points? 4. **Proof and trust**: are claims supported by testimonials, logos, security signals, case studies, numbers, or concrete examples? 5. **Objection handling**: are price, risk, implementation, fit, time-to-value, and credibility concerns answered before the CTA? 6. **Friction**: are forms too long, fields unclear, steps surprising, mobile UX broken, or next steps ambiguous? 7. **Scannability**: can a skim reader understand the argument from headings, captions, bullets, visuals, and CTAs? ## Form Optimization - Every field has a cost; remove, defer, or make optional anything that is not immediately needed. - Put value and reassurance directly above the form. - Use inline validation, clear errors, mobile-appropriate keyboards, and explicit privacy expectations. - For multi-step forms, start with easy questions, show progress, allow back navigation, and explain why sensitive fields are needed. ## Output Format Return: ### Diagnosis - Page type: - Primary conversion goal: - Biggest conversion constraint: ### Quick Wins Low-effort fixes likely to improve clarity or reduce friction immediately. ### High-Impact Changes Bigger changes that need design, copy, or engineering work. ### Test Ideas Hypotheses formatted for `ab-test-setup`: "If we change [thing], then [metric] should improve because [reason]." ### Copy Alternatives Provide 2-3 headline, CTA, or form-label alternatives when copy is a conversion blocker. ### Context Updates List any reusable audience, objection, proof, or positioning discoveries that should be written to `strategy/brand.md` or `content/ideas.md`.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".