ab-split-test-engineering
A comprehensive skill for A/B split test engineering, following Neil Patel's methodology. It covers test prioritization (ICE scoring), statistical significance, sample size, hypothesis formation, variable isolation, multivariate vs. A/B decisions, test documentation, and conversion lift calculation. Use this skill to optimize web pages, ads, and emails for higher conversion rates.
What this skill does
# A/B Split Test Engineering
## Overview
This skill provides a structured approach to A/B split test engineering, enabling users to systematically improve their marketing campaigns and website performance. By leveraging Neil Patel's proven methodologies, this skill guides users through the entire testing process, from prioritizing tests to analyzing results and calculating conversion lift.
**Keywords**: A/B testing, split testing, conversion rate optimization, CRO, Neil Patel, ICE score, statistical significance, hypothesis testing, multivariate testing, landing page optimization, ad optimization, email optimization.
## Discovery & Planning Questions
1. What is the specific URL of the page, a description of the ad, or the subject of the email you want to A/B test?
2. What is the single most important metric you want to improve with this test? (e.g., increase click-through rate, reduce bounce rate, boost sales, increase form submissions)
3. Who is the target audience for this test? Please describe their demographics, interests, and online behavior.
4. Do you have any existing data, user feedback, or analytics (like heatmaps, scroll maps, or user recordings) that suggest a problem or opportunity?
5. What is your initial hypothesis? What specific element do you want to change, and why do you believe it will improve performance?
6. What is the typical weekly traffic to the page or the number of recipients for the email you plan to test? This helps in calculating the required sample size and test duration.
7. Are there any technical limitations, platform constraints, or specific A/B testing tools I should be aware of?
8. Are there any brand guidelines, such as specific colors, fonts, or messaging tones, that must be maintained in the test variation?
9. What is your timeline for this test, from implementation to conclusion?
10. What do you consider a successful outcome? Is there a specific percentage lift or target goal you are aiming for?
## Core Frameworks
This agent utilizes Neil Patel's comprehensive A/B testing methodology, which is a synthesis of best practices in conversion rate optimization. The core of this framework revolves around a data-driven and iterative approach to testing.
* **Neil Patel's A/B Testing Methodology:** A holistic framework that emphasizes a structured and continuous approach to testing. It involves identifying goals, forming hypotheses, creating variations, running tests with sufficient sample sizes, and analyzing results to make informed decisions.
* **ICE Scoring:** A prioritization framework used to rank A/B testing ideas. It stands for:
* **Impact:** How much of an impact will this test have on the key metric?
* **Confidence:** How confident are we that this test will produce a positive result?
* **Ease:** How easy is it to implement this test?
* **Statistical Significance Calculation:** The agent uses a statistical significance calculator, modeled after Neil Patel's tool, to ensure that test results are not due to random chance. This is crucial for making data-driven decisions with confidence.
## S-Tier Tactics (Must-Do)
* **Always Have a Clear Hypothesis:** Every test must start with a clear, testable hypothesis that states what you are changing, who you are changing it for, and what you expect the outcome to be.
* **Test One Variable at a Time:** For a true A/B test, only one element should be changed between the control and the variation. This allows you to attribute any change in performance to that specific element.
* **Run Tests for a Sufficient Duration:** Tests should be run for at least two weeks to account for fluctuations in traffic and user behavior. Ending a test prematurely can lead to misleading results.
* **Use a Structured Approach:** Follow a consistent and documented process for every A/B test. This includes planning, execution, analysis, and sharing of results.
* **Prioritize High-Impact Tests:** Focus your efforts on tests that have the potential to make the biggest impact on your key metrics. Use the ICE score to identify these opportunities.
* **Analyze Beyond Conversions:** While conversion rate is a key metric, also analyze other metrics like average order value, customer lifetime value, and bounce rate to get a complete picture of the test's impact.
* **Embrace Continuous Testing:** A/B testing is not a one-time event. It should be an ongoing process of iteration and improvement. As Neil Patel says, "Always Be Testing."
## A-Tier Tactics (Highly Effective)
* **Leverage User Behavior Data:** Use tools like heatmaps, scroll maps, and user recordings to identify user pain points and opportunities for testing.
* **Segment Your Results:** Analyze test results across different user segments (e.g., new vs. returning visitors, traffic source, device type) to gain deeper insights.
* **Consider Radical Redesigns:** While A/B testing is great for iterative improvements, don't be afraid to test radically different designs (multivariate testing) to achieve breakthrough results.
* **Personalize the User Experience:** Use dynamic content and personalization to tailor the user experience based on user data and behavior.
* **Test the Entire Funnel:** Don't just focus on a single page. Test the entire conversion funnel, from the initial ad or email to the final thank you page.
* **Run Tests Simultaneously:** To ensure a fair comparison, the control and variation should be run at the same time to the same audience.
## B-Tier Tactics (Good to Have)
* **Test Minor Elements:** While not as high-impact as other tests, testing minor elements like button color, font size, and image placement can still lead to incremental gains.
* **Incorporate Social Proof and Urgency:** Test the use of social proof (e.g., testimonials, reviews) and urgency (e.g., countdown timers, limited-time offers) to influence user behavior.
* **Optimize Form Fields:** Test different form lengths, field types, and layouts to reduce friction and increase form submissions.
* **A/B Test Email Elements:** For email campaigns, test different subject lines, send times, and content to improve open rates and click-through rates.
## Common Mistakes to Avoid (D-Tier)
* **Testing Without a Hypothesis:** Running tests without a clear hypothesis is like throwing darts in the dark. You might get lucky, but it's not a sustainable strategy.
* **Ending Tests Prematurely:** Don't stop a test as soon as you see a positive result. Wait for the test to reach statistical significance to ensure the result is not due to chance.
* **Testing Too Many Variables at Once:** In an A/B test, only one variable should be changed. If you change multiple variables, you won't know which one is responsible for the change in performance.
* **Ignoring Qualitative Data:** Quantitative data tells you what is happening, but qualitative data (e.g., user feedback, surveys) tells you why. Use both to get a complete picture.
* **Blindly Copying Competitors:** What works for your competitor may not work for you. It's important to understand the context and your own audience before running a test.
* **Making Decisions on Small Sample Sizes:** A small sample size can lead to misleading results. Use a sample size calculator to determine the appropriate sample size for your test.
* **Failing to Document Results:** Documenting your test results and learnings is crucial for building a knowledge base and avoiding repeating the same mistakes.
## Step-by-Step Workflow
1. **Define Your Goal:** Clearly define the primary metric you want to improve (e.g., increase conversion rate on the pricing page by 10%).
2. **Formulate a Hypothesis:** Based on your goal and user research, formulate a clear and testable hypothesis. For example: "By changing the call-to-action button color from blue to green, we will increase the click-through rate because green is more associated with 'go' and will stand out more on the page."
3. **PRelated 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".