Token导航 LogoToken导航

Agent Skill · 开发

ab-testing-pricing(AB 测试定价)

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

ab-testing-pricing 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 17,281。

总安装 423周安装 18GitHub Stars 19下载 148核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill ab-testing-pricing

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

针对价格策略的 A/B 测试技能,在多个平台实现受控的价格对比实验。支持跨客户群体和产品类别的价格敏感性测试,降低决策风险。指导正确设置实验参数,确保结果可靠且不影响用户体验。多数平台无原生价格测试功能,需借助专用应用或自定义方案实施。

ab-testing-pricing 属于开发类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/ab-testing-pricing

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill ab-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

ab-testing-pricing 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill ab-testing-pr…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ab-testing-pricing 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

ab-testing-pricing 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

ab-testing-pricing 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

ab-testing-pricing 用的人多吗?

公开数据是累计安装 423 次,近一周安装 18 次,下载 148 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

ab-testing-pricing 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
ab-testing-pricing

AB 测试定价 · 本页

42319需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

A/B Testing Pricing

Overview

Price A/B testing lets you run controlled experiments — showing one price to a segment of visitors and a different price to another — before committing to a permanent change. This is one of the highest-leverage optimizations available, but also one of the riskiest: a poorly executed test destroys customer trust and produces misleading data. Most platforms do not have native price A/B testing, so this requires either a dedicated app or a custom implementation. This skill walks you through setting up price experiments correctly on each major platform.

When to Use This Skill

  • When you need data-driven evidence for a price change before rolling it out site-wide
  • When testing price sensitivity across different customer segments or product categories
  • When evaluating the revenue impact of a new pricing model (e.g., switching from $49.99 to $45.00)
  • When running multiple concurrent price experiments on different products without interference
  • When regulatory or ethical requirements demand that price tests are documented, time-limited, and reversible

Core Instructions

Step 1: Determine the merchant's platform and choose the right approach

PlatformRecommended ToolWhy
ShopifyIntelligems or Neat A/B Testing appNative Shopify apps that handle price variant assignment, session stickiness, and statistical reporting without custom code
Shopify PlusIntelligems + Shopify FunctionsShopify Functions allow server-side price overrides — the most reliable approach on Plus
WooCommerceNelio A/B Testing plugin or Split HeroWordPress-native experiment plugins with WooCommerce price testing support
BigCommerceIntelligems (supports BigCommerce) or Google Optimize alternativesBigCommerce's Price Lists API can set variant-specific prices per customer segment
Custom / HeadlessBuild with your own session bucketing + platform pricing APIFull control but requires custom statistical tracking

Step 2: Design the experiment

Before setting up any tool, define these parameters:

  1. Hypothesis — "Reducing the price from $49.99 to $44.99 will increase revenue per visitor by more than 5%"
  2. Primary metric — Revenue per visitor (RPV), not just conversion rate. A lower price converts better but may earn less per order
  3. Traffic split — 50/50 is standard; never run more than 2 variants simultaneously on the same product
  4. Minimum duration — At least 7 days to capture weekday/weekend variation; ideally 14 days
  5. Minimum sample size — Calculate using a significance calculator (use abtestguide.com). Aim for at least 100 conversions per variant before declaring a winner
  6. Exclusion rules — Existing customers who paid the old price should not be shown the new price mid-experiment

Step 3: Platform-specific setup


Shopify

Option A: Intelligems (recommended for most merchants)

Intelligems is the leading Shopify app for price testing. It handles session stickiness, statistical significance, and integrates with Shopify's checkout natively.

  1. Install Intelligems from the Shopify App Store
  2. Go to Intelligems → Tests → New Price Test
  3. Select the product(s) to test
  4. Set your variant prices (e.g., $49.99 vs $44.99)
  5. Set traffic split (50/50 recommended)
  6. Set a start date and estimated end date based on your sample size calculator
  7. Intelligems assigns visitors to variants via a persistent cookie and reports RPV, conversion rate, and statistical significance in their dashboard

Key settings to configure:

  • Sticky bucketing — ensure the same visitor always sees the same price (enabled by default)
  • Returning customer exclusion — under Advanced Settings, exclude customers who have previously purchased the product at the original price
  • Minimum detectable effect — set to the minimum revenue change that would justify the price change (e.g., 5%)

Option B: Neat A/B Testing

A lighter-weight alternative if you only need simple price split tests:

  1. Install Neat A/B Testing from the App Store
  2. Create a test targeting a specific product or collection
  3. Set the price variant and traffic split
  4. Monitor results in the Neat dashboard

Option C: Shopify Plus — Shopify Functions (advanced)

For Plus merchants who need full control:

  1. Create a Shopify Function (Discount Function type)
  2. The function receives cart context and customer ID
  3. Use deterministic hashing on the customer/session ID to assign to a variant
  4. Apply a fixed-amount or percentage discount equal to the price difference
  5. Track conversions via Shopify's order webhook + a custom analytics store

WooCommerce

Option A: Nelio A/B Testing plugin

  1. Install Nelio A/B Testing from the WordPress plugin directory
  2. Go to Nelio A/B Testing → Add New Experiment → WooCommerce Product Experiment
  3. Select the product and set the alternative price
  4. Configure the conversion goal (purchase of that product)
  5. The plugin tracks sessions and reports conversion rates with statistical significance

Option B: Manual with Google Optimize (sunsetted) replacements

Since Google Optimize was discontinued in 2023, consider:

  • VWO (Visual Website Optimizer) — supports WooCommerce price testing via JavaScript
  • AB Tasty — enterprise-grade with WooCommerce native integration
  • Convert.com — WooCommerce-compatible with server-side testing support

Important WooCommerce note: Client-side price changes (JavaScript-based) are cosmetic only — they do not change the actual checkout price. Always ensure your A/B testing tool changes the price at the WooCommerce product level or through the woocommerce_get_price filter, not just the displayed number.


BigCommerce
  1. Use BigCommerce's Price Lists feature (available on Plus and above):

- Go to Products → Price Lists → Add Price List - Create a price list for your "treatment" price - Assign the price list to a specific customer group

  1. Split customers into control/treatment groups by assigning them to the customer group
  2. Track conversions using BigCommerce's built-in analytics or Google Analytics with custom dimensions

Alternatively, use Intelligems for BigCommerce which manages the visitor bucketing automatically.


Custom / Headless

For headless storefronts, you need to implement session bucketing, price resolution, and conversion tracking:

import crypto from 'crypto';

// Deterministic variant assignment by session ID
function assignVariant(
  experimentId: string,
  sessionId: string,
  variants: { id: string; weight: number }[]  // weights must sum to 100
): string {
  const hash = parseInt(
    crypto.createHash('sha256')
      .update(`${experimentId}:${sessionId}`)
      .digest('hex')
      .slice(0, 8),
    16
  ) % 100;

  let cumulative = 0;
  for (const variant of variants) {
    cumulative += variant.weight;
    if (hash < cumulative) return variant.id;
  }
  return variants[variants.length - 1].id;
}

// Usage: get the price for a visitor
const variantId = assignVariant('exp_price_widget_pro', sessionId, [
  { id: 'control',   weight: 50 },  // $49.99
  { id: 'treatment', weight: 50 },  // $44.99
]);

const prices = { control: 4999, treatment: 4499 };  // cents
const priceForVisitor = prices[variantId];

Track conversions and calculate statistical significance:

// Two-proportion z-test for statistical significance
function zTest(
  controlConversions: number,
  controlVisitors: number,
  treatmentConversions: number,
  treatmentVisitors: number
): { pValue: number; significant: boolean } {
  const p1 = controlConversions / controlVisitors;
  const p2 = treatmentConversions / treatmentVisitors;
  const pPooled = (controlConversions + treatmentConversions) / (controlVisitors + treatmentVisitors);
  const se = Math.sqrt(pPooled * (1 - pPooled) * (1 / controlVisitors + 1 / treatmentVisitors));
  if (se === 0) return { pValue: 1, significant: false };
  const z = Math.abs((p2 - p1) / se);
  // Approximate p-value (two-tailed)
  const pValue = 2 * (1 - normalCDF(z));
  return { pValue, significant: pValue < 0.05 };
}

Use your platform's pricing API (Shopify Admin API, BigCommerce Catalog API) to push price updates once a winner is declared.

Step 4: Monitor and conclude the experiment

Track these metrics during the experiment:

MetricWhere to find it
Revenue per visitor (RPV)Intelligems dashboard; or calculate from your orders data
Conversion rate by variantYour A/B tool's analytics
Statistical significance (p-value)Your A/B tool; aim for p < 0.05
Sample size per variantEnsure you hit your pre-calculated minimum before concluding

Declare a winner only when:

  • You have reached the pre-calculated minimum sample size (not before)
  • The p-value is below 0.05
  • The experiment has run for at least 7 days

After declaring a winner, update the product price permanently and end the experiment.

Best Practices

  • Use Revenue Per Visitor (RPV), not just conversion rate — a lower price may convert better but generate less revenue; RPV captures the full picture
  • Require sticky bucketing — once a session is assigned to a variant, always show the same price; inconsistent prices destroy trust and distort results
  • Pre-register your minimum sample size — decide before the experiment starts how many conversions you need; stopping as soon as p < 0.05 (peeking) inflates false positive rates
  • Exclude existing customers — showing an existing customer a price lower than what they paid triggers complaints and churn
  • Run only one experiment per product at a time — overlapping experiments on the same product create interaction effects that make results uninterpretable
  • Pause experiments during promotions — site-wide sales or marketing campaigns confound price experiment results
  • Log the variant assignment on every order — store the variant ID in the order metadata so you can later audit revenue attribution

Common Pitfalls

ProblemSolution
Visitor sees different price on refreshEnsure your A/B tool uses persistent cookies or server-side session storage for bucketing
Peeking — stopping at first p < 0.05Pre-register a minimum conversion count (e.g., 200 per variant) and only check significance after reaching it
Price change only affects the product page, not checkoutEnsure the test tool changes the actual price, not just a displayed number — verify in the cart and checkout
Bots inflate visitor counts and skew resultsFilter bot traffic before recording impressions; most A/B tools have bot filtering built in
Experiment runs during a flash salePause all price experiments during site-wide promotions

Related Skills

  • @dynamic-pricing
  • @price-rules-engine
  • @coupon-management
  • @discount-engine
  • @demand-forecasting

平台分布

Codex

33.61%
按下载量换算50

Claude

27.59%
按下载量换算41

Cursor

19.85%
按下载量换算29

Gemini CLI

9.43%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills