Token导航 LogoToken导航

Agent Skill · 效率

inventory-risk-radar(库存风险雷达)

inventory-risk-radar 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

inventory-risk-radar 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为权限未标注;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 16,184。

总安装 2,920周安装 117GitHub Stars 公开资料未说明下载 945核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:inventory-risk-radar(库存风险雷达)
来源仓库:https://github.com/harrylabsj/inventory-risk-radar
安装命令:
openclaw skills install inventory-risk-radar
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install inventory-risk-radar

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

inventory-risk-radar 扫描库存数据,识别缺货、过剩、延迟入库等五类运营风险。适用于实时监控 SKU 健康状态,生成可执行的风险观察列表。支持 CSV 导入,自动分类问题类型并排序处理 urgency。结果需人工复核,尤其关注高价值商品与季节性品类差异。

可与 ERP 系统集成,但本技能独立运行,不修改底层业务系统。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install inventory-risk-radar;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

inventory-risk-radar 怎么安装?

在终端执行 openclaw skills install inventory-risk-radar。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

inventory-risk-radar 支持哪些 AI 工具?

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

inventory-risk-radar 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

inventory-risk-radar 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

inventory-risk-radar 用的人多吗?

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

inventory-risk-radar 安全吗?

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

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

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

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
inventory-risk-radar

库存风险雷达 · 本页

2,920—权限未标注MIT-0通过

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

SKILL.md 原文

name
inventory-risk-radar
description
Scan ecommerce inventory notes or CSV exports for stockout, overstock, aging, inbound-delay, and promo-readiness risk, then turn them into a ranked watchlist, days-of-cover summary, action ladder, scenario notes, and operator-ready meeting brief. Use when inventory planners, operations leads, finance-aware operators, founders, or marketplace teams need a lightweight risk-detection layer without live ERP, WMS, or demand-forecasting integrations.

Inventory Risk Radar

Overview

Use this skill to turn inventory, sales, and supplier notes into a practical risk brief. It helps teams prioritize which SKUs need immediate attention, what kind of risk is present, and which action path should be reviewed first.

This MVP is heuristic. It does not connect to live ERP, WMS, purchase-order systems, or forecasting engines. It relies on the user's provided stock position, velocity, lead-time, and business-context notes.

Trigger

Use this skill when the user wants to:

  • flag stockout, overstock, aging, or inbound-delay risk
  • prepare a daily, weekly, or pre-promo inventory watchlist
  • estimate where cash or revenue risk is likely building
  • turn rough inventory exports into an ops-ready action memo
  • align replenishment, markdown, and supplier follow-up priorities

Example prompts

  • "Create a daily inventory risk watchlist from these notes"
  • "Which SKUs look most exposed before our promotion?"
  • "Help me prioritize stockout versus overstock risk"
  • "Turn this inventory and lead-time export into an ops meeting brief"

Workflow

  1. Capture the review mode, such as daily watchlist, replenishment review, pre-promo scan, or cash-risk review.
  2. Normalize the likely inventory signals: on-hand, inbound, sales velocity, lead time, and aging pressure.
  3. Classify the major risk types and translate them into business exposure.
  4. Build the watchlist, action ladder, and scenario notes.
  5. Return a markdown brief that operators can use in review meetings.

Inputs

The user can provide any mix of:

  • on-hand, reserved, available, inbound, or backorder notes
  • recent sales velocity, sell-through, or promo assumptions
  • supplier lead time, PO status, inbound ETA, or vendor reliability notes
  • aging days, markdown history, or storage constraints
  • margin, cash sensitivity, or strategic-SKU context
  • review purpose such as daily monitoring, replenishment planning, or promo readiness

Outputs

Return a markdown risk brief with:

  • inventory risk dashboard
  • days-of-cover summary
  • critical, warning, and watch-tier notes
  • action ladder and scenario notes
  • owner-ready watchlist guidance
  • assumptions, confidence notes, and limits

Safety

  • Do not claim access to live ERP, WMS, or supplier systems.
  • Treat exposure estimates as directional unless the user provides complete inputs.
  • Do not auto-create POs, transfers, markdowns, or ad changes.
  • Keep replenishment, liquidation, and promo decisions human-approved.
  • Reduce confidence when lead time, velocity, or SKU mapping is incomplete.

Best-fit Scenarios

  • SMB and mid-market ecommerce teams managing recurring stock risk
  • weekly replenishment meetings or pre-promo reviews
  • brands balancing stockout loss against cash tied up in slow movers
  • operators who need a lighter decision layer than a full planning suite

Not Ideal For

  • manufacturing-grade MRP planning with BOM and production scheduling
  • highly automated warehouse orchestration or real-time fulfillment control
  • businesses with almost no sales, stock, or lead-time history
  • workflows that require automatic purchasing or system execution

Example Output Pattern

A strong response should:

  • separate stockout, overstock, aging, and inbound-delay logic clearly
  • show severity and likely action path, not only raw inventory commentary
  • connect revenue risk and cash risk in the same brief when relevant
  • include scenario thinking for promo uplift or inbound slippage
  • surface assumptions when data quality is weak

Acceptance Criteria

  • Return markdown text.
  • Include dashboard, watchlist, action, and limits sections.
  • Make advisory limits explicit.
  • Keep the brief practical for operations, purchasing, and finance-aware operators.

平台分布

OpenClaw

76.82%
按下载量换算726

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

继续浏览同类 Skills