Token导航 LogoToken导航

Agent Skill · 研究检索

low-stock-alerts(库存不足警报)

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

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

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

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill low-stock-alerts

这个 Skill 是做什么的

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

low-stock-alerts 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于库存管理、电商运营和供应链预警等研究场景。通过关键词、任务或来源仓库进行信息筛选,需结合原始 README 确认具体用法。

安装命令为 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill low-stock-alerts。使用前建议确认权限范围、维护状态及是否触发联网或文件读写操作。

来源仓库内路径:skills/low-stock-alerts

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

low-stock-alerts 怎么安装?

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

low-stock-alerts 支持哪些 AI 工具?

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

low-stock-alerts 需要什么权限?

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

low-stock-alerts 是免费的吗?

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

low-stock-alerts 用的人多吗?

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

low-stock-alerts 安全吗?

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

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

值得选的地方

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

库存不足警报 · 本页

49019只读未明确通过

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

SKILL.md 原文

Low Stock Alerts

Overview

Low stock alerts notify you when inventory drops below a threshold so you can reorder before running out. Every major platform has this built in — Shopify, WooCommerce, and BigCommerce all send email notifications when stock falls below a configured level. For more advanced needs like demand-based thresholds, supplier PO automation, or team notifications in Slack, dedicated apps add those capabilities without custom code.

When to Use This Skill

  • When products are unexpectedly running out of stock and missing sales
  • When the current inventory workflow relies on manual checks rather than automated alerts
  • When you want demand-based reorder points rather than fixed thresholds
  • When the store has supplier lead times that need to be factored into when to reorder

Core Instructions

Step 1: Determine platform and choose the right tool

PlatformBuilt-in AlertsRecommended Extension
ShopifyShopify sends an email notification when stock hits zero; very limited threshold controlStocky (free, by Shopify) for configurable thresholds and PO automation; Back in Stock for customer notifications
WooCommerceWooCommerce emails the store admin when stock drops below the configured low-stock thresholdATUM Inventory Management for per-product thresholds, supplier emails, and reorder suggestions
BigCommerceBuilt-in low stock notifications per product with configurable thresholdMulti-Location Inventory app for location-specific alerts
Custom / HeadlessBuild a background job that checks levels against reorder pointsRequired when platform has no native alerting or you need supplier email automation

Step 2: Platform-specific setup


Shopify

Built-in low stock notification:

Shopify sends an email to the store admin when inventory hits zero, but doesn't support configurable thresholds natively.

  1. Go to Settings → Notifications → Scroll to Staff order notifications
  2. Ensure the admin email is set — Shopify will notify this address when stock reaches 0

Setting per-variant thresholds with Stocky:

  1. Install Stocky from the Shopify App Store (free)
  2. Open Stocky and go to Products
  3. For each product, set the Reorder point (the stock level that triggers an alert)
  4. Set the Reorder quantity (how many units to order when the alert fires)
  5. Stocky will flag products below their reorder point in the dashboard and can generate draft purchase orders automatically

Customer "back in stock" notifications:

  • Install Back In Stock (paid) or Klaviyo from the App Store
  • These apps show a "Notify me when available" button on out-of-stock products
  • Automatically email opted-in customers when stock is replenished

WooCommerce

Configure global low-stock threshold:

  1. Go to WooCommerce → Settings → Products → Inventory
  2. Enter a value in Low stock threshold (e.g., 10)
  3. Enter your notification email in Notification recipient(s) — comma-separate multiple emails
  4. WooCommerce sends an email when any product drops to or below this threshold

Set per-product thresholds:

  1. Go to WooCommerce → Products → [Product] → Inventory tab
  2. Enable Manage stock?
  3. Enter a Low stock threshold specific to this product (overrides the global setting)

Advanced alerting with ATUM:

  1. Install ATUM Inventory Management for WooCommerce (free)
  2. ATUM's dashboard shows all products at or below their reorder point in one view
  3. Per-product reorder point configuration under ATUM → Product Settings
  4. ATUM can also email your supplier directly when a product needs reordering (paid feature)

Demand-based thresholds:

  • Install Inventory Planner (Shopify/WooCommerce) for sales velocity-based reorder suggestions
  • Inventory Planner analyzes your sales history and suggests reorder points based on lead time × daily velocity + safety stock

BigCommerce

Set per-product low stock threshold:

  1. Go to Products → [Product] → Inventory tab
  2. Set the Low stock level field
  3. BigCommerce sends an automatic email notification to the store admin when stock crosses this threshold

Configure who receives alerts:

  1. Go to Store Setup → Store Settings → Miscellaneous
  2. Set Low stock email address to your purchasing team's email

For location-specific alerts:

  • Install the Multi-Location Inventory app
  • Set thresholds per location — useful when you stock the same SKU at multiple warehouses

Custom / Headless

For custom platforms, implement a background job that checks inventory levels against configured reorder points:

// jobs/checkStockLevels.ts — run every 15-30 minutes via cron
export async function checkStockLevels() {
  const levels = await db.inventoryLevels.findMany({
    include: { reorderConfig: true, variant: { include: { product: true } }, location: true },
    where: { reorderConfig: { isNot: null } },
  });

  const newAlerts = [];

  for (const level of levels) {
    const config = level.reorderConfig!;
    const available = level.onHand - level.reserved;

    // Dynamic reorder point based on sales velocity and lead time
    let reorderPoint = config.reorderPoint;
    if (config.useDynamicReorderPoint) {
      const velocity = await calculateDailySalesVelocity(level.variantId, 30); // 30-day rolling average
      reorderPoint = Math.ceil(velocity * config.leadTimeDays * 1.2); // 20% safety stock buffer
    }

    const alertType = available === 0 ? 'out_of_stock' : available <= reorderPoint ? 'low_stock' : null;
    if (!alertType) continue;

    // Only create a new alert if the previous one is resolved
    const existingAlert = await db.stockAlerts.findFirst({
      where: { variantId: level.variantId, locationId: level.locationId, alertType, resolvedAt: null },
    });

    if (!existingAlert) {
      newAlerts.push({ level, config, available, reorderPoint, alertType });
      await db.stockAlerts.create({ data: {
        variantId: level.variantId, locationId: level.locationId,
        alertType, triggeredAt: new Date(), availableAtTrigger: available,
      }});
    }
  }

  if (newAlerts.length > 0) await sendAlertNotifications(newAlerts);
}

// Calculate daily sales velocity from order history
async function calculateDailySalesVelocity(variantId: string, windowDays: number) {
  const since = new Date(Date.now() - windowDays * 86400000);
  const result = await db.orderLineItems.aggregate({
    where: { variantId, order: { createdAt: { gte: since }, status: { in: ['completed', 'shipped'] } } },
    _sum: { quantity: true },
  });
  return (result._sum.quantity ?? 0) / windowDays;
}

// Send consolidated alerts — group by supplier to avoid email spam
async function sendAlertNotifications(alerts: Alert[]) {
  const bySupplier: Record<string, Alert[]> = {};
  for (const alert of alerts) {
    const key = alert.config.supplierId ?? 'merchant';
    if (!bySupplier[key]) bySupplier[key] = [];
    bySupplier[key].push(alert);
  }

  for (const [supplierId, supplierAlerts] of Object.entries(bySupplier)) {
    const to = supplierId === 'merchant' ? process.env.MERCHANT_ALERT_EMAIL : (await db.suppliers.findById(supplierId))?.email;
    if (!to) continue;
    await emailService.send({ to, template: 'low-stock-alert', data: { alerts: supplierAlerts } });
  }
}

Step 3: Calculate dynamic reorder points (optional)

Fixed thresholds (e.g., "alert at 10 units") are simple but can be wrong — a product that sells 50 units per day needs a much higher threshold than one that sells 2 per week.

Formula:

Reorder Point = (Daily Sales Velocity × Lead Time Days) × 1.2 (20% safety buffer)

Example: Product sells 5 units/day, supplier lead time is 7 days

  • Demand during lead time: 5 × 7 = 35 units
  • Reorder point with safety buffer: 35 × 1.2 = 42 units

For Shopify: Use Inventory Planner app — it computes velocity-based reorder points automatically from your sales history.

For WooCommerce: ATUM Inventory Management can be configured with supplier lead times and suggests reorder points based on sales velocity.


Step 4: Automate reorder notifications to suppliers

Once an alert fires, you want to notify your purchasing team or supplier automatically.

Shopify + Stocky: Stocky generates draft purchase orders when stock falls below the reorder point. Your team reviews and sends the PO to the supplier from within Stocky.

WooCommerce + ATUM (paid): ATUM can email the configured supplier directly when a product needs reordering, including the suggested quantity.

Email workflow (any platform): Set the low-stock notification email directly to your supplier's ordering inbox — include the SKU, product name, and suggested reorder quantity in the notification template.

Best Practices

  • Set reorder points based on lead time and sales velocity — a fixed threshold of 10 units may be fine for slow movers but dangerously low for fast sellers; use the formula above as a starting point
  • De-duplicate alerts — platforms and custom solutions should only send one alert per SKU per incident, not an alert on every inventory decrement; resolve old alerts when stock is replenished
  • Consolidate supplier emails — one email with 5 low-stock SKUs from the same supplier is far less noisy than 5 separate emails
  • Set thresholds at the variant level, not just the product level — a shirt with 3 remaining in XL and 50 in M should alert only for XL
  • Review and update thresholds seasonally — a product that sells 2/day normally may sell 20/day during peak season; adjust thresholds before high-demand periods

Common Pitfalls

ProblemSolution
Alert fires repeatedly for the same SKUEnsure the platform only sends one alert per incident until stock is replenished; Shopify and WooCommerce do this correctly by default; custom builds need a resolvedAt guard
Dynamic reorder point too high during off-seasonUse a rolling 30-day window for velocity calculations; consider separate seasonal configurations for products with strong seasonality
Supplier emails go to spamUse an authenticated sending domain (SPF, DKIM, DMARC) for your alert emails; transactional email providers (SendGrid, Postmark) improve deliverability
Alert threshold too low — too many false alarmsStart with a threshold at 2× your typical order quantity from the supplier, then tune based on how often you're actually running out before the reorder arrives

Related Skills

  • @inventory-tracking
  • @multi-warehouse
  • @catalog-import-export

平台分布

Codex

35.71%
按下载量换算56

Claude

30.52%
按下载量换算48

Cursor

18.11%
按下载量换算28

Gemini CLI

10.04%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills