Token导航 LogoToken导航

Agent Skill · 研究检索

social-proof-widgets(社会证明小部件)

social-proof-widgets 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

social-proof-widgets 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 56,028。

总安装 465周安装 19GitHub Stars 19下载 150核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill social-proof-widgets

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于社会证明组件设计、用户反馈展示或转化优化研究等场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。安装前需确认权限范围、维护状态,以及是否涉及联网或文件操作。

social-proof-widgets 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/social-proof-widgets

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

social-proof-widgets 怎么安装?

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

social-proof-widgets 支持哪些 AI 工具?

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

social-proof-widgets 需要什么权限?

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

social-proof-widgets 是免费的吗?

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

social-proof-widgets 用的人多吗?

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

social-proof-widgets 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

研究检索类 Skill 对比

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

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
social-proof-widgets

社会证明小部件 · 本页

46519需要联网未明确通过

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

SKILL.md 原文

Social Proof Widgets

Overview

Social proof widgets — recent purchase notifications, visitor counts, review badges, and low-stock indicators — reduce purchase anxiety and increase conversion rates by 10–30% on product pages. For Shopify and WooCommerce, dedicated apps (Fomo, TrustPulse, ProveSource) install these widgets without code. Building custom widgets is only necessary for headless stores with specific design requirements.

When to Use This Skill

  • When product pages have good traffic but low conversion rates
  • When launching a new product that lacks reviews and needs other trust signals
  • When testing whether social proof elements meaningfully impact CVR (A/B test required)
  • When wanting to add real-time purchase notifications
  • When building a low-stock urgency display based on actual inventory data

Core Instructions

Step 1: Choose the right social proof tool

PlatformBest ForShopifyWooCommerceBigCommercePrice
FomoReal-time purchase notificationsApp StorePluginVia JS$19+/mo
TrustPulseRecent purchases + live visitor count—PluginVia JS$5+/mo
ProveSourceAll platforms, highly customizableApp StoreVia JSVia JSFree tier; $20+/mo
Judge.meReview count badge + verified buyer badgeApp StorePluginApp MarketplaceFree tier; $15/mo
CustomHeadless stores, specific design needsVia APIVia APIVia APIDev cost

Recommendation: Use Fomo for Shopify (best purchase notifications) and TrustPulse for WooCommerce. For review badges, use your existing review platform (Judge.me, Yotpo) — they include star rating badges automatically.

Step 2: Set up social proof widgets


Shopify with Fomo
  1. Install Fomo from the Shopify App Store
  2. Go to Fomo → Events → Shopify Orders — Fomo automatically imports recent orders from your store
  3. Configure the notification template:

- Display: first name and city (e.g., "Sarah from Chicago just purchased…") - Show the product name and image - Display within the last 48 hours

  1. Go to Fomo → Design to customize the position and style of the notification toast (bottom-left by default)
  2. Go to Fomo → Rules and set:

- Show only on product pages (URL contains /products/) - Hide on cart and checkout pages - Minimum 3 notifications to show before displaying the widget (prevents showing a widget with only 1 event)

  1. Go to Fomo → A/B Testing to split-test the widget against a control group — always measure lift before enabling sitewide

WooCommerce with TrustPulse
  1. Install TrustPulse from the WordPress plugin directory
  2. Go to TrustPulse → Create Campaign and select Recent Activity
  3. Configure:

- Data source: WooCommerce Recent Orders - Display: customer name, city, product purchased - Show: orders from the last 7 days

  1. Set targeting rules: show only on product and shop pages; exclude checkout
  2. For the visitor count widget, create a second On Fire campaign: "X people looking at this right now" — set a minimum visitor threshold of 5 before displaying

BigCommerce with ProveSource
  1. Sign up for ProveSource and add the JavaScript snippet to your store via Storefront → Script Manager
  2. Connect your BigCommerce store to ProveSource via the integration settings
  3. Configure recent purchase notifications and visitor count widgets from the ProveSource dashboard

Custom / Headless

For headless stores, build a social proof API and client widget:

// GET /api/products/:id/social-proof
// Returns real data only — never fabricate counts
export async function getProductSocialProof(req: Request, res: Response) {
  const productId = req.params.id;

  const [recentOrders, reviewSummary, stockLevel] = await Promise.all([
    db.orderLineItems.findAll({
      where: { productId, createdAt: { gte: subHours(new Date(), 48) } },
      include: ['order.shippingAddress'],
      limit: 10,
    }),
    db.productReviews.aggregate(productId),
    db.productVariants.findMinStock(productId),
  ]);

  // Anonymize PII — first name and city only
  const recentPurchases = recentOrders.map(item => ({
    firstName: item.order.shippingAddress.firstName,
    location: `${item.order.shippingAddress.city}, ${item.order.shippingAddress.stateCode}`,
    timeAgo: formatTimeAgo(item.createdAt),
    productName: item.productName,
  }));

  return res.json({
    recentPurchases,
    reviews: { average: reviewSummary.avgRating, total: reviewSummary.total },
    stockLevel: {
      isLow: stockLevel > 0 && stockLevel <= 5,
      quantity: stockLevel,
      isSoldOut: stockLevel === 0,
    },
  });
}

Client-side purchase notification toast — using DOM methods to prevent XSS:

class SocialProofToast {
  private queue: Array<{ firstName: string; location: string; productName: string; timeAgo: string }> = [];
  private isShowing = false;

  async init(productId: string) {
    const response = await fetch(`/api/products/${productId}/social-proof`);
    const data = await response.json();
    this.queue = data.recentPurchases.slice(0, 5);
    this.showNext();
  }

  private showNext() {
    if (this.queue.length === 0 || this.isShowing) return;
    const purchase = this.queue.shift()!;
    this.isShowing = true;

    const toast = document.createElement('div');
    toast.className = 'sp-toast';

    const strong = document.createElement('strong');
    strong.textContent = `${purchase.firstName} from ${purchase.location}`; // textContent prevents XSS

    const span = document.createElement('span');
    span.textContent = ` purchased ${purchase.productName}`;

    const time = document.createElement('time');
    time.textContent = purchase.timeAgo;

    toast.appendChild(strong);
    toast.appendChild(span);
    toast.appendChild(time);
    document.body.appendChild(toast);

    setTimeout(() => {
      toast.remove();
      this.isShowing = false;
      setTimeout(() => this.showNext(), 8000); // 8-second gap between toasts
    }, 5000);
  }
}

Step 3: Add low-stock urgency indicators

Low-stock messaging ("Only 3 left!") drives urgency effectively — but only show real inventory counts. Fake urgency destroys trust when customers notice it.

In Shopify: Install Urgency Bear or Hurrify from the Shopify App Store — they read your actual Shopify inventory and display "Only X left" messages on product pages.

In WooCommerce: Enable WooCommerce's built-in low-stock display:

  1. Go to WooCommerce → Settings → Products → Inventory
  2. Enable Show stock management at product level
  3. Enable Enable low stock threshold and set to 5
  4. WooCommerce automatically shows "Only 3 in stock" on product pages when inventory falls below the threshold

Custom thresholds: Use CSS to style the low-stock message based on quantity levels.

Step 4: A/B test social proof impact

Always test before deploying sitewide. Both Fomo and TrustPulse have built-in A/B testing.

For manual A/B testing:

  1. Enable the widget for 50% of visitors using your platform's experimentation tool
  2. Measure for at least 2 weeks and 200+ conversions per group
  3. Compare conversion rate, AOV, and revenue per visitor between the groups
  4. Only keep the widget if it shows statistically significant lift (p < 0.05)

Best Practices

  • Only show real data — fabricated purchase counts or invented visitor numbers erode trust when discovered; use a minimum threshold (5+ events) before showing any widget
  • Anonymize purchase notifications — show first name and city only; never include order IDs, full names, or email addresses
  • Load social proof asynchronously — fetch after page load using requestIdleCallback; never block the critical render path
  • Hide the widget on cart and checkout pages — showing purchase notifications during checkout distracts from conversion; disable on these pages
  • Cap notification frequency — show a maximum of 3 toasts per page session with 8+ second gaps between them
  • Use textContent for all customer-derived data — prevents XSS vulnerabilities; never use innerHTML with customer names or locations

Common Pitfalls

ProblemSolution
Toast notifications feel spammyLimit to 3 per session; add 8-second gaps; hide on cart/checkout
Widget hurts conversion (A/B test shows negative lift)Disable immediately; test with different placement, copy, or timing before abandoning
Review badge not appearing in Google search resultsEnsure AggregateRating schema is server-rendered (not just client-side JS); verify with Google Rich Results Test
Low-stock indicator showing wrong quantitySubscribe to inventory change webhooks rather than polling; stale data creates false urgency
Social proof widget slowing page loadLoad all social proof widgets asynchronously after page interactive; use requestIdleCallback or setTimeout(fn, 0)

Related Skills

  • @review-generation-engine
  • @conversion-rate-optimization
  • @exit-intent-popups
  • @ugc-campaign-management
  • @ab-testing-ecommerce

平台分布

Codex

38.69%
按下载量换算58

Claude

29.14%
按下载量换算44

Cursor

20.36%
按下载量换算31

Gemini CLI

9.02%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills