Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

ab-split-test-engineeringab 分割测试工程

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

196

周安装

8

GitHub Stars

5

下载量

63
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ab-split-test-engineering(ab 分割测试工程)
来源仓库:https://github.com/dmend3z/tribo-skills
仓库路径:skills/ab-split-test-engineering
安装命令:
npx skills add https://github.com/dmend3z/tribo-skills --skill ab-split-test-engineering
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/dmend3z/tribo-skills --skill ab-split-test-engineering

简介

ab-split-test-engineering 提供基于 Neil Patel 方法论的 A/B 分割测试工程框架,覆盖全流程设计。

  • 适用于营销活动优化、落地页改进或产品功能迭代中的转化率提升实验规划。
  • 支持优先级排序、假设构建、样本量计算及结果显著性分析,输出可执行测试方案。
  • 需明确测试目标与核心指标,避免因多重比较导致统计偏差;建议设置足够运行时间。
  • 不处理实际流量分配,仅提供分析与建议,需结合平台工具实施具体实验。

SKILL.md

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. Prioritize with ICE Score: If you have multiple test ideas, use the ICE score to prioritize them based on their potential Impact, your Confidence in the hypothesis, and the Ease of implementation.
  4. Create Variations: Design and develop the challenger variation (B) to test against the current version (A). Ensure that only the element being tested is different between the two versions.
  5. Determine Sample Size: Use a statistical significance calculator to determine the number of visitors or conversions needed to run a statistically valid test.
  6. Run the Test: Use an A/B testing tool to randomly assign visitors to the control and variation. Run the test until you have reached the predetermined sample size.
  7. Analyze the Results: Once the test is complete, analyze the results to determine which version performed better. Use a statistical significance calculator to confirm that the results are statistically significant.
  8. Implement the Winner: If the variation is the clear winner, implement it on your website. If the results are inconclusive, use the learnings to formulate a new hypothesis and run another test.
  9. Document and Share: Document the test results, including the hypothesis, variations, results, and learnings. Share the results with your team to build a culture of testing and continuous improvement.

Templates & Frameworks

Hypothesis Template

  • Because we observed that [data/observation], we believe that [change] for [audience] will cause [impact]. We'll know this is true when we see [metric] change.

ICE Score Template

Test IdeaImpact (1-10)Confidence (1-10)Ease (1-10)ICE Score (Avg)
Change CTA button color5797.0
Redesign homepage9625.7

Examples

Example 1: Changing a CTA Button Color

  • Observation: The current blue CTA button on the pricing page has a low click-through rate.
  • Hypothesis: By changing the CTA button color to green, we will increase the click-through rate because green is more visually prominent and associated with a positive action.
  • Test: Run an A/B test with 50% of traffic seeing the blue button and 50% seeing the green button.
  • Result: The green button resulted in a 15% increase in click-through rate with 99% statistical significance.
  • Action: Implement the green button on the pricing page.

Example 2: Testing a New Headline

  • Observation: The bounce rate on the homepage is high.
  • Hypothesis: By changing the headline to be more benefit-oriented, we will decrease the bounce rate because visitors will better understand the value proposition.
  • Test: Run an A/B test with the current headline vs. a new, benefit-oriented headline.
  • Result: The new headline decreased the bounce rate by 20% with 95% statistical significance.
  • Action: Implement the new headline on the homepage.

Pro Tips from the Experts

"The biggest mistake I see people make is they give up after one or two tests. You have to keep testing. That's why I say, 'Always Be Testing.'" - Neil Patel
"Don't just look at the conversion rate. Look at the revenue per visitor. Sometimes a lower conversion rate with a higher average order value can be more profitable." - Neil Patel
"Your customers are the best source of ideas for A/B tests. Listen to their feedback, read their reviews, and watch their behavior on your site." - Neil Patel

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

39.05%
按下载量换算25

Claude

31.04%
按下载量换算20

Cursor

18.5%
按下载量换算12

Gemini CLI

9.16%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills