Token导航 LogoToken导航

Agent Skill · 开发

demand-forecasting(需求预测)

demand-forecasting 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

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

总安装 724周安装 29GitHub Stars 19下载 234核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill demand-forecasting

这个 Skill 是做什么的

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

demand-forecasting 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。

它提供需求预测指导,基于历史销售数据和季节性模式预测库存需求,适用于库存管理优化场景。使用方式包括分析库存短缺或过剩原因、设置自动化补货逻辑和优化再订购点,减少运营成本。使用时需要确认历史数据质量和业务规则,避免过度依赖直觉判断而忽视实际数据驱动决策。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/demand-forecasting

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

demand-forecasting 怎么安装?

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

demand-forecasting 支持哪些 AI 工具?

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

demand-forecasting 需要什么权限?

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

demand-forecasting 是免费的吗?

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

demand-forecasting 用的人多吗?

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

demand-forecasting 安全吗?

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

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

值得选的地方

  • 同时适配 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有提醒
demand-forecasting

需求预测 · 本页

72419需要联网未明确通过

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

SKILL.md 原文

Demand Forecasting

Overview

Demand forecasting uses historical sales data, seasonal patterns, and lead times to predict how much inventory you'll need and when to reorder. Chronic stockouts or overstock situations are usually a sign that reorder points are based on intuition rather than data. Purpose-built inventory planning tools handle this for most merchants — custom forecasting code is only necessary for unique operational requirements.

When to Use This Skill

  • When chronic stockouts or overstock situations indicate that current reorder points are set incorrectly
  • When building automated replenishment recommendations to reduce manual inventory review
  • When planning inventory for seasonal peaks (Black Friday, back-to-school, holiday season)
  • When you have 12+ months of sales history and want to extract meaningful demand patterns
  • When integrating with supplier lead times and purchase order workflows for end-to-end replenishment

Core Instructions

Step 1: Determine your platform and choose the right forecasting tool

PlatformRecommended ToolWhy
ShopifyInventory Planner (Shopify App Store) or CogsyInventory Planner connects directly to Shopify, analyzes 12+ months of sales history, calculates reorder points, and generates purchase orders
WooCommerceATUM Inventory Management (free/premium) or Inventory PlannerATUM provides reorder point management natively in WooCommerce; Inventory Planner has a WooCommerce connector for advanced forecasting
BigCommerceInventory Planner or LinnworksBoth have BigCommerce native integrations and handle multi-location inventory forecasting
Multi-channelSkubana (now Extensiv) or LinnworksHandles inventory forecasting across Shopify, WooCommerce, Amazon, and eBay from a single dashboard
Custom / HeadlessBuild a time-series analysis layer on top of your order databaseUse moving averages, seasonal decomposition, and safety stock formulas against your historical sales data

Step 2: Set up sales history data collection

Accurate forecasting requires clean historical data. Before running any forecast:

  1. Ensure cancelled and refunded orders are excluded from your sales totals — most forecasting tools handle this automatically when connected to your platform
  2. Tag promotional periods — flash sales, holiday spikes, and influencer-driven demand should be flagged as abnormal; they inflate baseline demand estimates if included uncritically
  3. You need at least 6 months of history for basic seasonal pattern detection; 12+ months is required to see year-over-year trends
Shopify

Using Inventory Planner:

  1. Install Inventory Planner from the Shopify App Store (14-day free trial, then $99+/month)
  2. Inventory Planner pulls your full Shopify sales history automatically on connection
  3. Connect your suppliers in Inventory Planner → Suppliers with their lead times (e.g., Supplier A = 14 days, Supplier B = 7 days)
  4. Set your desired service level (e.g., 95% — meaning you want to have stock for 95% of demand scenarios) in Settings → Forecasting
  5. Inventory Planner calculates reorder points and recommended order quantities per SKU, updated daily

Shopify Analytics (built-in, no app needed for basic trends):

  1. Go to Analytics → Reports → Inventory
  2. The "Days of inventory remaining" report shows how many days of stock you have at current sell-through rate
  3. Go to Analytics → Reports → Sales over time → group by product to see monthly sales trends
  4. Use these as inputs for manual reorder decisions if you don't want to pay for a forecasting app
WooCommerce

Using ATUM Inventory Management (free tier available):

  1. Install ATUM Inventory Management for WooCommerce from WordPress.org (free) or purchase the premium version
  2. ATUM adds a master inventory list view with real-time stock levels, daily sales rates, and low-stock alerts
  3. In ATUM → Settings → Reorder Points, configure your reorder levels and safety stock per SKU
  4. ATUM's premium Purchase Orders module generates POs automatically when stock hits the reorder point

Using Inventory Planner for WooCommerce:

  1. Connect Inventory Planner to WooCommerce via their native API connector
  2. Same workflow as Shopify — Inventory Planner analyzes your WooCommerce sales history and generates forecasts
BigCommerce

Using Inventory Planner:

  1. Connect Inventory Planner via the BigCommerce API (Inventory Planner → Settings → Connect Store)
  2. Inventory Planner pulls sales history from BigCommerce and generates replenishment recommendations

BigCommerce built-in low-stock alerts:

  1. Go to Products → [Product] → Inventory
  2. Set "Low stock level" for each product — BigCommerce emails you when stock drops below this threshold
  3. This is a simple alert, not a forecast — use it as a backstop while you set up a proper forecasting tool

Step 3: Configure reorder points and safety stock

Reorder point = demand during lead time + safety stock buffer.

In Inventory Planner:

  1. Inventory Planner calculates this automatically based on your sales history and supplier lead times
  2. Review the recommendations in Inventory Planner → Replenishment — items are sorted by urgency (days of stock remaining vs. lead time)
  3. Adjust recommendations manually before creating purchase orders (e.g., if you know a supplier has extra lead time for a specific product)
  4. Export purchase orders directly from Inventory Planner to email to your suppliers

Manual calculation (if not using a forecasting tool):

  • Average daily demand = total units sold in last 30 days / 30
  • Safety stock = (maximum daily demand – average daily demand) × lead time in days
  • Reorder point = (average daily demand × lead time in days) + safety stock
  • Example: Average daily demand = 5 units, lead time = 14 days, max daily demand = 8 units

- Safety stock = (8–5) × 14 = 42 units - Reorder point = (5 × 14) + 42 = 112 units

Step 4: Plan for seasonal demand

Seasonality is the biggest cause of forecast errors. Plan for it explicitly.

In Inventory Planner:

  1. Go to Inventory Planner → Settings → Seasonality
  2. Inventory Planner detects seasonal patterns automatically from your sales history
  3. For first-year merchants (no prior year data): manually set seasonal multipliers — e.g., December = 3x normal demand for holiday products

Building a seasonal calendar manually:

  1. Export your sales by month for the past 2+ years from Shopify Reports / WooCommerce / BigCommerce
  2. Calculate the ratio of each month's sales to the annual average (December / average month = seasonal index)
  3. Apply the seasonal index to your daily demand forecast when placing orders for the upcoming peak season

Promotional calendar:

  • Flag planned promotions (flash sales, influencer campaigns) in your forecasting tool
  • Most forecasting tools allow manual demand overrides for specific date ranges
  • For Black Friday/Cyber Monday: increase your forecast by your historical BFCM lift percentage (typically 3–8x for e-commerce)

Step 5: Generate and approve replenishment recommendations

In Inventory Planner:

  1. Go to Inventory Planner → Replenishment → Review recommendations
  2. Filter by "Critical" (stock-out in fewer days than lead time) and "Warning" (stock-out within 2x lead time)
  3. Adjust quantities if you have market intelligence the model doesn't know (planned sales, anticipated supply issues)
  4. Click "Create Purchase Order" — Inventory Planner generates a PO to send to your supplier
  5. Track the PO status in Inventory Planner → Purchase Orders; when received, update actual receipt dates to improve future lead time estimates

Step 6: Custom / Headless — demand forecasting from sales data

// Compute average daily demand from your order database
async function computeAverageDailyDemand(
  productId: string,
  lookbackDays: number = 30
): Promise<number> {
  const since = new Date();
  since.setDate(since.getDate() - lookbackDays);

  const result = await db.raw(`
    SELECT COALESCE(SUM(ol.quantity), 0) AS total_units
    FROM order_lines ol
    JOIN orders o ON o.id = ol.order_id
    WHERE ol.product_id = ?
      AND o.status NOT IN ('cancelled', 'refunded')
      AND o.created_at >= ?
  `, [productId, since]);

  return result.rows[0].total_units / lookbackDays;
}

// Calculate reorder point with safety stock
function calculateReorderPoint(params: {
  avgDailyDemand: number;
  maxDailyDemand: number;   // observed peak daily demand
  leadTimeDays: number;
}): number {
  const safetyStock = (params.maxDailyDemand - params.avgDailyDemand) * params.leadTimeDays;
  return Math.ceil(params.avgDailyDemand * params.leadTimeDays + safetyStock);
}

// Generate replenishment recommendations for all active products
async function generateReplenishmentReport(): Promise<{
  productId: string;
  sku: string;
  currentStock: number;
  reorderPoint: number;
  daysOfSupply: number;
  urgency: 'critical' | 'warning' | 'ok';
}[]> {
  const products = await db.products.findAll({ is_active: true, track_inventory: true });
  const recommendations = [];

  for (const product of products) {
    const inventory = await db.inventory.findByProductId(product.id);
    const avgDemand = await computeAverageDailyDemand(product.id, 30);
    const maxDemand = await computeAverageDailyDemand(product.id, 7); // shorter window = more volatile
    const leadTimeDays = product.supplier_lead_time_days ?? 14;

    const reorderPoint = calculateReorderPoint({ avgDailyDemand: avgDemand, maxDailyDemand: maxDemand, leadTimeDays });
    const daysOfSupply = avgDemand > 0 ? Math.floor(inventory.quantity_on_hand / avgDemand) : 999;
    const urgency = daysOfSupply < leadTimeDays ? 'critical' : daysOfSupply < leadTimeDays * 2 ? 'warning' : 'ok';

    if (urgency !== 'ok') {
      recommendations.push({ productId: product.id, sku: product.sku, currentStock: inventory.quantity_on_hand, reorderPoint, daysOfSupply, urgency });
    }
  }

  return recommendations.sort((a, b) => a.daysOfSupply - b.daysOfSupply);
}

Best Practices

  • Start with a tool like Inventory Planner before building custom forecasting — $100–$300/month is far cheaper than engineering time, and the models are more accurate than a hand-rolled moving average
  • Set a minimum of 6 months of sales history before trusting any forecast; for new products, use a category-average demand rate as a proxy
  • Adjust forecasts for known events — planned promotions, seasonal campaigns, and supply chain disruptions should be entered as manual overrides in your forecasting tool
  • Track forecast accuracy monthly — compare forecast units to actual units sold; if you're off by more than 25% consistently, recalibrate your assumptions or look for a structural change in demand patterns
  • Account for pending purchase orders — subtract quantity on order from your recommended replenishment qty before placing a new PO; double-ordering is a common and expensive mistake

Common Pitfalls

ProblemSolution
New products have no history to forecast fromUse category average demand rate for the first 90 days; Inventory Planner has a "new product" mode that adjusts for this
Forecast doesn't account for supplier stockoutsTrack supplier fill rates in your vendor management system; if a supplier consistently ships 80% of ordered qty, order 25% more to compensate
Safety stock too low, stockouts still happenIncrease your service level setting in Inventory Planner from 90% to 95–98% for high-velocity SKUs
Replenishment recommendation ignores open POsAlways check "quantity on order" before creating a new PO; Inventory Planner shows this automatically, but manual calculations often miss it

Related Skills

  • @order-management-system
  • @vendor-management
  • @multi-channel-selling

平台分布

Codex

34.51%
按下载量换算81

Claude

30.73%
按下载量换算72

Cursor

19.04%
按下载量换算45

Gemini CLI

8.65%
按下载量换算20

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills