agentleFS
Eugenevdm01Eugenevdm01/eugenes-meta-agent/skills/split-test-evaluator/SKILL.md

split-test-evaluator

Skill4 starsChanged 6 months agoMITView on GitHub

Compare ad and landing page variants to determine likely winners and stop premature conclusions. Use when evaluating A/B tests or multivariate experiments.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When evaluating the results of an A/B test (e.g., two different ad creatives, headlines, or landing pages).

    line 12
  2. Distinctive:

    When deciding whether to scale a winning variant or pause a losing one.

    line 13
  3. Distinctive:

    When determining if a test has reached statistical significance.

    line 14
  4. Distinctive:

    When planning a new split test to ensure proper design and measurement.

    line 15
  5. Distinctive:

    Review Test Design: Ensure the test is structured correctly (e.g., only one variable changed, sufficient sample size).

    line 27
  6. Distinctive:

    Evaluate Downstream Impact: Check if the winning variant also performs well further down the funnel (e.g., does a higher CTR lead to more …

    line 30
  7. Distinctive:

    Never declare a winner prematurely based on small sample sizes or insignificant differences.

    line 43
  8. Distinctive:

    Always consider the downstream impact.

    line 44
  9. Distinctive:

    If a test shows a statistically meaningful loss (e.g., a new landing page significantly underperforms the control), escalate immediately to …

    line 47
  10. Distinctive:

    If the test design is flawed (e.g., multiple variables changed simultaneously), flag it and recommend a redesign.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Split-Test Evaluator

Purpose

Compare ad and landing page variants to determine likely winners, stop premature conclusions, and ensure statistical significance before making decisions.

When to Use This Skill

  • When evaluating the results of an A/B test (e.g., two different ad creatives, headlines, or landing pages).
  • When deciding whether to scale a winning variant or pause a losing one.
  • When determining if a test has reached statistical significance.
  • When planning a new split test to ensure proper design and measurement.

Inputs Required

  • The hypothesis being tested (e.g., "A shorter form will increase conversion rate").
  • The variable being tested (e.g., headline, image, CTA color).
  • The success metric (e.g., Cost Per Lead, Conversion Rate, Click-Through Rate).
  • The minimum data needed (e.g., 100 conversions per variant).
  • The winning condition (e.g., 95% statistical significance).
  • The next action after the result (e.g., scale the winner, test a new variable).

Step-by-Step Workflow

  1. Review Test Design: Ensure the test is structured correctly (e.g., only one variable changed, sufficient sample size).
  2. Analyze Data: Compare the performance of the variants against the success metric.
  3. Calculate Significance: Determine if the difference in performance is statistically significant (using a calculator or formula).
  4. Evaluate Downstream Impact: Check if the winning variant also performs well further down the funnel (e.g., does a higher CTR lead to more qualified leads?).
  5. Make a Decision: Recommend whether to declare a winner, continue testing, or pause the test.

Output Format

Provide a structured evaluation report containing:

  • Test Overview: Hypothesis, variable, and success metric.
  • Results Summary: Performance data for each variant.
  • Significance Analysis: Statistical confidence level and whether the test is conclusive.
  • Downstream Impact: Any observed effects on subsequent funnel stages.
  • Recommendation: Clear action (e.g., "Declare Variant A the winner and scale budget").

Decision Rules

  • Do not suggest random changes. Keep testing structured.
  • Never declare a winner prematurely based on small sample sizes or insignificant differences.
  • Always consider the downstream impact; a winning ad (high CTR) might produce lower-quality leads than a losing ad (lower CTR).

Escalation Rules

  • If a test shows a statistically meaningful loss (e.g., a new landing page significantly underperforms the control), escalate immediately to pause the test.
  • If the test design is flawed (e.g., multiple variables changed simultaneously), flag it and recommend a redesign.

Templates & Resources

  • templates/split-test-report.md: Template for presenting split test results.
  • scripts/calculate-significance.py: (Optional) Script to calculate statistical significance.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.