Token导航 LogoToken导航

Agent Skill · 研究检索

push-notifications(推送通知)

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

push-notifications 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为操作浏览器;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 55,945。

总安装 466周安装 20GitHub Stars 19下载 163核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill push-notifications

这个 Skill 是做什么的

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

push-notifications 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。适用于推送通知相关的资料搜索与内容筛选,可结合来源仓库和原始 README 进一步核验具体用法。

通过 npx skills add 命令从 GitHub 仓库安装,支持主流 AI 宿主环境集成调用。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/push-notifications

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要操作浏览器,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

push-notifications 怎么安装?

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

push-notifications 支持哪些 AI 工具?

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

push-notifications 需要什么权限?

权限级别是操作浏览器。该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

push-notifications 是免费的吗?

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

push-notifications 用的人多吗?

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

push-notifications 安全吗?

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

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
push-notifications

推送通知 · 本页

46619操作浏览器未明确通过

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

SKILL.md 原文

Push Notifications

Overview

Web push notifications deliver timely messages to subscribers even when they are not on your site — for back-in-stock alerts, price drops, and cart reminders. Push requires explicit browser permission, making the opt-in prompt timing critical. For Shopify, WooCommerce, and BigCommerce, dedicated push notification apps (PushOwl, OneSignal) handle all the subscriber management, triggering logic, and delivery without custom service worker code.

When to Use This Skill

  • When adding back-in-stock notifications to replace static "notify me" email forms
  • When recovering abandoned carts via a browser push channel alongside email
  • When building a price-watch feature for wishlisted items
  • When email deliverability is poor and a supplemental channel is needed
  • When targeting mobile-first markets where push opt-in rates exceed email opt-in

Core Instructions

Step 1: Choose the right push notification platform

PlatformBest ForShopifyWooCommerceBigCommercePrice
PushOwlShopify-native, back-in-stock + abandonmentApp Store——Free tier; $19+/mo
OneSignalAll platforms, free tier, highly configurableVia JS tagPluginVia JS tagFree tier; $9+/mo
Klaviyo Web PushAlready using Klaviyo for emailApp StorePluginApp MarketplaceIncluded in Klaviyo
PushEngageWooCommerce + segmented campaigns—PluginVia JS tagFree tier; $9+/mo

Shopify recommendation: Use PushOwl — it's the most integrated Shopify push app with built-in back-in-stock, cart abandonment, and shipping alerts.

WooCommerce recommendation: Use PushEngage or OneSignal — both have WordPress plugins and handle subscriber management automatically.

Step 2: Set up push notifications


Shopify with PushOwl
  1. Install PushOwl from the Shopify App Store
  2. Go to PushOwl → Settings → Opt-in Prompt and configure:

- Delay the prompt: set it to trigger after a customer views 2+ pages or adds an item to cart - Opt-in message: "Get notified when items are back in stock and for price drops"

  1. Go to PushOwl → Automations → Back in Stock and enable it — PushOwl automatically adds a "Notify Me" button to out-of-stock products and fires the push when inventory is replenished
  2. Go to PushOwl → Automations → Cart Abandonment and enable it:

- Set timing: 1 hour after abandonment, then 24 hours - Customize the notification message and the cart recovery URL

  1. Go to PushOwl → Campaigns to send broadcast push notifications for sales, new arrivals, or flash discounts

WooCommerce with PushEngage
  1. Install PushEngage from the WordPress plugin directory (free tier available)
  2. Go to PushEngage → Settings → Subscription Prompt and configure the opt-in dialog
  3. Enable automated campaigns:

- Go to PushEngage → Automation → Cart Abandonment and set the timing and message - Go to PushEngage → Automation → Back in Stock and enable it (requires WooCommerce stock event integration)

  1. For price drop alerts: go to PushEngage → Automation → Price Drop Alert and enable subscriber opt-in per product
  2. Use PushEngage → Broadcast to send manual push campaigns to all subscribers

BigCommerce with OneSignal
  1. Sign up for OneSignal at onesignal.com and create a Web Push app
  2. Go to OneSignal → Settings → Web Push → Setup and follow the HTTPS domain verification
  3. Add the OneSignal JavaScript snippet to your BigCommerce store via Storefront → Script Manager: <script src="https://cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.js" defer></script> <script> window.OneSignalDeferred = window.OneSignalDeferred || []; OneSignalDeferred.push(async function(OneSignal) {await OneSignal.init({appId: "YOUR_APP_ID"});}); </script>
  4. For back-in-stock: use BigCommerce webhooks to trigger a OneSignal API call when product stock transitions from 0 to available
  5. For cart abandonment: use BigCommerce's Abandoned Cart webhook + OneSignal REST API to send cart recovery pushes

Custom / Headless

For headless stores, implement push using the Web Push API directly:

// Service worker — save as /sw.js in your public directory
self.addEventListener('push', (event) => {
  const data = event.data?.json() ?? {};
  event.waitUntil(
    self.registration.showNotification(data.title, {
      body: data.body,
      icon: data.icon ?? '/icons/icon-192.png',
      image: data.image,
      data: { url: data.url },
      actions: data.actions ?? [],
    })
  );
});

self.addEventListener('notificationclick', (event) => {
  event.notification.close();
  event.waitUntil(clients.openWindow(event.notification.data?.url ?? '/'));
});
// Server-side push sending using the web-push library
import webpush from 'web-push';

webpush.setVapidDetails(
  'mailto:admin@yourstore.com',
  process.env.VAPID_PUBLIC_KEY!,
  process.env.VAPID_PRIVATE_KEY!
);

// Generate VAPID keys once: npx web-push generate-vapid-keys

async function sendPushNotification(subscription: PushSubscription, payload: {
  title: string;
  body: string;
  url: string;
  icon?: string;
}) {
  try {
    await webpush.sendNotification(subscription, JSON.stringify(payload));
  } catch (err: any) {
    if (err.statusCode === 410) {
      // Subscription expired — remove from database
      await db.pushSubscriptions.deleteByEndpoint(subscription.endpoint);
    }
  }
}

// Triggered when inventory transitions from 0 to > 0
async function notifyBackInStock(productId: string) {
  const product = await db.products.findById(productId);
  const waitlist = await db.pushWaitlist.findByProduct(productId);

  for (const entry of waitlist) {
    const sub = await db.pushSubscriptions.findByUserId(entry.userId);
    if (!sub) continue;
    await sendPushNotification(sub, {
      title: 'Back in stock!',
      body: `${product.name} is available again`,
      url: `${process.env.STORE_URL}/products/${product.slug}`,
      icon: product.images[0]?.url,
    });
  }
}

Step 3: Optimize opt-in timing

The most critical factor for push notification effectiveness is when you show the permission prompt. Never ask on the first page load.

Best triggers for the opt-in prompt:

  • After the visitor has viewed 3+ products
  • Immediately after a customer adds an item to cart
  • When a customer views an out-of-stock product (context: "Get notified when it's back")
  • On the order confirmation page ("Get shipping updates and deals via browser push")

In PushOwl: go to Settings → Opt-in Prompt → Advanced and set the trigger condition. In PushEngage: go to Subscription Prompt → Display Rules and set page view count or cart event triggers.

Step 4: Set up the highest-converting push campaigns

Priority order by conversion rate:

  1. Back-in-stock alerts — highest CTR (15–25%); customers opted in specifically for this product
  2. Cart abandonment — set for 1 hour and 24 hours after abandonment; use urgency in the second push ("Your cart expires soon")
  3. Price drop alerts — customers watching a specific product convert at 10–20% when notified of their target price
  4. Shipping updates — low-friction way to grow push subscribers (capture at order confirmation); keeps brand top-of-mind

In PushOwl: all four are available as pre-built automations under Automations — enable them and customize the message.

Step 5: Measure push performance

MetricHealthy TargetWhere to Find
Opt-in rate5–15% of new visitorsApp dashboard
Back-in-stock click rate15–25%PushOwl/PushEngage analytics
Cart abandonment recovery rate2–5%App analytics
Unsubscribe rate per campaign< 2%App analytics

If unsubscribe rate is above 2%, reduce push frequency or improve message relevance.

Best Practices

  • Never request permission on first page load — acceptance rates jump from ~5% to ~25% when shown after a user action like adding to cart
  • Limit to 2 push notifications per day per user maximum — excessive frequency is the top driver of opt-out
  • Set a TTL on time-sensitive notifications — flash sale pushes should expire when the sale ends; PushOwl and PushEngage both support notification expiry
  • Keep notification body under 100 characters — longer bodies are truncated on Android; test on mobile before deploying
  • Use "Notify me" at the product level for out-of-stock — this captures high-intent subscribers with context; generic sitewide opt-ins perform worse

Common Pitfalls

ProblemSolution
Low opt-in rateMove the permission prompt to after add-to-cart or product view #3; never show on first load
iOS users not receiving pushWeb push on iOS requires iOS 16.4+ and the user must install the site as a PWA (Add to Home Screen); this is a browser limitation
Push notifications not firing for back-in-stockVerify the inventory webhook is connected in PushOwl/PushEngage settings; check the app's automation logs
High unsubscribe rateReduce push frequency; add preference management so subscribers can choose which notification types they receive
Duplicate subscriptions in the databaseFor custom implementations, use upsert keyed on (userId, endpoint)

Related Skills

  • @email-marketing-automation
  • @cart-abandonment-recovery
  • @sms-marketing
  • @exit-intent-popups
  • @customer-retention-engine

平台分布

Codex

36.12%
按下载量换算59

Claude

28.83%
按下载量换算47

Cursor

20.66%
按下载量换算34

Gemini CLI

9.66%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

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

继续浏览同类 Skills