reorder-policy
How to decide whether and how much to reorder a SKU. Load this whenever a task involves reorder recommendations, purchase orders, or "should we restock" questions.
- Installs
- 58
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/anthropics/cwc-workshops --skill reorder-policy- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads reorder-policy automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Reorder Policy
This skill encodes StockPilot's reorder rules. Use it whenever you need to decide whether to reorder a SKU and how many units to order.
Inputs you need
| Value | Where to get it |
|---|---|
on_hand | Latest row for the SKU in /mnt/user/data/stock_levels.csv (sum across warehouses unless the task is warehouse-specific) |
reorder_point | /mnt/user/data/products.csv |
avg_daily_sales | Mean of units_sold over the last 14 days in /mnt/user/data/sales_history.csv |
lead_time_days | From the chosen supplier (see the supplier-selection skill) |
forecast_qty, confidence, flags | From the forecasting skill, only if the task looks forward more than 14 days or mentions a promo/season |
Decision rules
-
Do we reorder at all? Reorder if
on_hand < reorder_point. Ifon_hand ≥ reorder_point, the answer is "no reorder needed" — stop here. -
How much? The target order quantity is 30 days of cover plus safety stock, minus what's already on hand:
safety_stock = 1.5 × avg_daily_sales × lead_time_days order_qty = (avg_daily_sales × 30) + safety_stock − on_handRound up to the supplier's
min_order_qtymultiple. -
Confidence guard. If you obtained a forecast and
confidence < 0.6, do not place a PO automatically. Instead:- Write an escalation to
/mnt/user/sinks/outbox.jsonlusing the notify-templates skill (escalation template), including theflagsfrom the forecast. - In your final answer, state the recommended quantity and that it requires human review, with the reason.
- Write an escalation to
-
Expedite? If
on_hand / avg_daily_sales < lead_time_days(you'll stock out before the order arrives), pick the supplier with the shortest lead time even if it's not the cheapest, and note "expedited" in the PO.
Worked example
SKU-0057: on_hand = 38, reorder_point = 120, avg_daily_sales = 18.2, chosen supplier lead_time_days = 7, min_order_qty = 50.
- 38 < 120 → reorder.
- safety_stock = 1.5 × 18.2 × 7 = 191.1
- order_qty = (18.2 × 30) + 191.1 − 38 = 546 + 191.1 − 38 = 699.1 → round up to next 50 → 700
- 38 / 18.2 = 2.1 days of cover, lead time is 7 → expedite.
Prioritization (when many SKUs are at risk)
Sort by tier, then by days-of-cover ascending within a tier:
- Stockouts —
on_hand = 0at any warehouse. Always first. - Will stock out before PO arrives —
days_of_cover < lead_time_days. Expedite or transfer. - High-velocity below reorder — top-100 sellers below reorder point.
- Routine replenishment — everything else below reorder point.
- Trending toward reorder — note only, no action.
If you can't action every SKU in one pass, say how many you handled, how many remain, and list the remaining SKU IDs so the next run picks them up.
Transfer vs reorder
When one warehouse is low and another has surplus:
- Transfer when the surplus warehouse has >30 days cover for itself, the 3–5 day transfer beats the best supplier lead, and the qty needed is ≲200 units. WH-CENTRAL is the default source.
- Reorder when no warehouse has surplus, the qty is large, or supplier lead is comparable to transfer lead anyway.
- Both when the shortage is urgent and large — transfer a bridge qty now, PO the remainder.
State which path you chose and why.
Compliance
- Any single PO over $10,000 needs a one-line rationale included with the PO so ops can copy it into the ERP.
- If you place more than five POs in one task, end with a one-line total committed spend.
- Do not place a second PO for a SKU that already has an open PO covering the need.
Output
When you act, append to /mnt/user/sinks/purchase_orders.jsonl:
{"sku": "SKU-0057", "supplier_id": "SUP-03", "qty": 700, "expedite": true, "reason": "below reorder point; 2.1d cover"}
When you only recommend (no side-effect requested), return a structured ReorderDecision:
{"sku": "...", "reorder": true, "qty": 700, "supplier_id": "SUP-03", "expedite": true, "confidence": 0.85, "notes": "..."}
FAQ
What does the reorder-policy skill do?
How to decide whether and how much to reorder a SKU. Load this whenever a task involves reorder recommendations, purchase orders, or "should we restock" questions.
How do I install reorder-policy?
Run npx skills add https://github.com/anthropics/cwc-workshops --skill reorder-policy in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/reorder-policy/ (personal) or .claude/skills/reorder-policy/ (project).
Which AI agents can use reorder-policy?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is reorder-policy safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains reorder-policy?
It is published by anthropics in anthropics/cwc-workshops, and it is an official skill from the maker of the technology it covers. It has 58 recorded installs.
More from anthropics/cwc-workshops
supplier-selection
anthropics/cwc-workshops
How to rank and pick a supplier for a SKU. Load this whenever a task involves choosing a supplier, comparing quotes, or creating a purchase order.
weekly-report
anthropics/cwc-workshops
Structure and data sources for the weekly inventory report. Load this when the task is "weekly report", "Monday report", or "summarize inventory status".
forecasting
anthropics/cwc-workshops
How to produce a demand forecast for a SKU, and when to delegate that to a subagent vs. compute it yourself. Load this for any task involving "forecast", "how much will we sell", "next month", promos, or seasonal SKUs.
submit-solution
anthropics/cwc-workshops
Guide a workshop attendee through committing their starter-agent decomposition and opening a PR with their solution + workshop feedback. Invoke when the user says "submit", "I'm done", "open a PR", or asks how to share their solution.
notify-templates
anthropics/cwc-workshops
Fixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops".
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由；/page/ 是妙搭应用，非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用；doubao.com 云空间 URL/token 也按资源路径和 token 路由，不回退 WebFetch。不负责：文档内容编辑（走 lark-doc）、表格/Base 表内数据操作（走 lark-sheets/lark-base）、知识空间节点/成员管理（走 lark-wiki）、原生 Markdown 文件读写/patch/diff（走 lark-markdown）。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。