[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718C7GYKCA1T5GVD14V6DM5":3,"skill-same:01M718C7GYKCA1T5GVD14V6DM5":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M718C7GYKCA1T5GVD14V6DM5","reorder-policy",null,"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.","anthropics\u002Fcwc-workshops","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M718C167JSRVRHKR28E40JYN",2309,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fagent-decomposition\u002F.claude\u002Fskills\u002Freorder-policy\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"policy","reorder policy","restock","how","recommendations","questions","decide","purchase","how to","load","orders","task","2026-11-10 10:12:30",false,"---\nname: reorder-policy\ndescription: 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.\n---\n\u003C!-- Copyright 2026 Anthropic PBC -->\n\u003C!-- SPDX-License-Identifier: Apache-2.0 -->\n\n\n# Reorder Policy\n\nThis skill encodes StockPilot's reorder rules. Use it whenever you need to decide **whether** to reorder a SKU and **how many units** to order.\n\n## Inputs you need\n\n| Value | Where to get it |\n|---|---|\n| `on_hand` | Latest row for the SKU in `\u002Fmnt\u002Fuser\u002Fdata\u002Fstock_levels.csv` (sum across warehouses unless the task is warehouse-specific) |\n| `reorder_point` | `\u002Fmnt\u002Fuser\u002Fdata\u002Fproducts.csv` |\n| `avg_daily_sales` | Mean of `units_sold` over the last 14 days in `\u002Fmnt\u002Fuser\u002Fdata\u002Fsales_history.csv` |\n| `lead_time_days` | From the chosen supplier (see the supplier-selection skill) |\n| `forecast_qty`, `confidence`, `flags` | From the forecasting skill, **only if** the task looks forward more than 14 days or mentions a promo\u002Fseason |\n\n## Decision rules\n\n1. **Do we reorder at all?** Reorder if `on_hand \u003C reorder_point`. If `on_hand ≥ reorder_point`, the answer is \"no reorder needed\" — stop here.\n\n2. **How much?** The target order quantity is **30 days of cover** plus safety stock, minus what's already on hand:\n\n   ```\n   safety_stock = 1.5 × avg_daily_sales × lead_time_days\n   order_qty    = (avg_daily_sales × 30) + safety_stock − on_hand\n   ```\n\n   Round up to the supplier's `min_order_qty` multiple.\n\n3. **Confidence guard.** If you obtained a forecast and `confidence \u003C 0.6`, **do not place a PO automatically.** Instead:\n   - Write an escalation to `\u002Fmnt\u002Fuser\u002Fsinks\u002Foutbox.jsonl` using the notify-templates skill (escalation template), including the `flags` from the forecast.\n   - In your final answer, state the recommended quantity and that it requires human review, with the reason.\n\n4. **Expedite?** If `on_hand \u002F avg_daily_sales \u003C 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.\n\n## Worked example\n\nSKU-0057: `on_hand = 38`, `reorder_point = 120`, `avg_daily_sales = 18.2`, chosen supplier `lead_time_days = 7`, `min_order_qty = 50`.\n\n- 38 \u003C 120 → reorder.\n- safety_stock = 1.5 × 18.2 × 7 = **191.1**\n- order_qty = (18.2 × 30) + 191.1 − 38 = 546 + 191.1 − 38 = **699.1** → round up to next 50 → **700**\n- 38 \u002F 18.2 = 2.1 days of cover, lead time is 7 → **expedite**.\n\n## Prioritization (when many SKUs are at risk)\n\nSort by tier, then by days-of-cover ascending within a tier:\n\n1. **Stockouts** — `on_hand = 0` at any warehouse. Always first.\n2. **Will stock out before PO arrives** — `days_of_cover \u003C lead_time_days`. Expedite or transfer.\n3. **High-velocity below reorder** — top-100 sellers below reorder point.\n4. **Routine replenishment** — everything else below reorder point.\n5. **Trending toward reorder** — note only, no action.\n\nIf you can't action every SKU in one pass, say how many you handled, how many\nremain, and list the remaining SKU IDs so the next run picks them up.\n\n## Transfer vs reorder\n\nWhen one warehouse is low and another has surplus:\n\n- **Transfer** when the surplus warehouse has >30 days cover for itself, the\n  3–5 day transfer beats the best supplier lead, and the qty needed is ≲200\n  units. WH-CENTRAL is the default source.\n- **Reorder** when no warehouse has surplus, the qty is large, or supplier lead\n  is comparable to transfer lead anyway.\n- **Both** when the shortage is urgent and large — transfer a bridge qty now,\n  PO the remainder.\n\nState which path you chose and why.\n\n## Compliance\n\n- Any single PO over **$10,000** needs a one-line rationale included with the\n  PO so ops can copy it into the ERP.\n- If you place **more than five POs** in one task, end with a one-line total\n  committed spend.\n- Do not place a second PO for a SKU that already has an open PO covering the\n  need.\n\n## Output\n\nWhen you act, append to `\u002Fmnt\u002Fuser\u002Fsinks\u002Fpurchase_orders.jsonl`:\n```json\n{\"sku\": \"SKU-0057\", \"supplier_id\": \"SUP-03\", \"qty\": 700, \"expedite\": true, \"reason\": \"below reorder point; 2.1d cover\"}\n```\n\nWhen you only recommend (no side-effect requested), return a structured `ReorderDecision`:\n```json\n{\"sku\": \"...\", \"reorder\": true, \"qty\": 700, \"supplier_id\": \"SUP-03\", \"expedite\": true, \"confidence\": 0.85, \"notes\": \"...\"}\n```\n","\u003C!-- Copyright 2026 Anthropic PBC -->\n\u003C!-- SPDX-License-Identifier: Apache-2.0 -->\n\n\n# Reorder Policy\n\nThis skill encodes StockPilot's reorder rules. Use it whenever you need to decide **whether** to reorder a SKU and **how many units** to order.\n\n## Inputs you need\n\n| Value | Where to get it |\n|---|---|\n| `on_hand` | Latest row for the SKU in `\u002Fmnt\u002Fuser\u002Fdata\u002Fstock_levels.csv` (sum across warehouses unless the task is warehouse-specific) |\n| `reorder_point` | `\u002Fmnt\u002Fuser\u002Fdata\u002Fproducts.csv` |\n| `avg_daily_sales` | Mean of `units_sold` over the last 14 days in `\u002Fmnt\u002Fuser\u002Fdata\u002Fsales_history.csv` |\n| `lead_time_days` | From the chosen supplier (see the supplier-selection skill) |\n| `forecast_qty`, `confidence`, `flags` | From the forecasting skill, **only if** the task looks forward more than 14 days or mentions a promo\u002Fseason |\n\n## Decision rules\n\n1. **Do we reorder at all?** Reorder if `on_hand \u003C reorder_point`. If `on_hand ≥ reorder_point`, the answer is \"no reorder needed\" — stop here.\n\n2. **How much?** The target order quantity is **30 days of cover** plus safety stock, minus what's already on hand:\n\n   ```\n   safety_stock = 1.5 × avg_daily_sales × lead_time_days\n   order_qty    = (avg_daily_sales × 30) + safety_stock − on_hand\n   ```\n\n   Round up to the supplier's `min_order_qty` multiple.\n\n3. **Confidence guard.** If you obtained a forecast and `confidence \u003C 0.6`, **do not place a PO automatically.** Instead:\n   - Write an escalation to `\u002Fmnt\u002Fuser\u002Fsinks\u002Foutbox.jsonl` using the notify-templates skill (escalation template), including the `flags` from the forecast.\n   - In your final answer, state the recommended quantity and that it requires human review, with the reason.\n\n4. **Expedite?** If `on_hand \u002F avg_daily_sales \u003C 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.\n\n## Worked example\n\nSKU-0057: `on_hand = 38`, `reorder_point = 120`, `avg_daily_sales = 18.2`, chosen supplier `lead_time_days = 7`, `min_order_qty = 50`.\n\n- 38 \u003C 120 → reorder.\n- safety_stock = 1.5 × 18.2 × 7 = **191.1**\n- order_qty = (18.2 × 30) + 191.1 − 38 = 546 + 191.1 − 38 = **699.1** → round up to next 50 → **700**\n- 38 \u002F 18.2 = 2.1 days of cover, lead time is 7 → **expedite**.\n\n## Prioritization (when many SKUs are at risk)\n\nSort by tier, then by days-of-cover ascending within a tier:\n\n1. **Stockouts** — `on_hand = 0` at any warehouse. Always first.\n2. **Will stock out before PO arrives** — `days_of_cover \u003C lead_time_days`. Expedite or transfer.\n3. **High-velocity below reorder** — top-100 sellers below reorder point.\n4. **Routine replenishment** — everything else below reorder point.\n5. **Trending toward reorder** — note only, no action.\n\nIf you can't action every SKU in one pass, say how many you handled, how many\nremain, and list the remaining SKU IDs so the next run picks them up.\n\n## Transfer vs reorder\n\nWhen one warehouse is low and another has surplus:\n\n- **Transfer** when the surplus warehouse has >30 days cover for itself, the\n  3–5 day transfer beats the best supplier lead, and the qty needed is ≲200\n  units. WH-CENTRAL is the default source.\n- **Reorder** when no warehouse has surplus, the qty is large, or supplier lead\n  is comparable to transfer lead anyway.\n- **Both** when the shortage is urgent and large — transfer a bridge qty now,\n  PO the remainder.\n\nState which path you chose and why.\n\n## Compliance\n\n- Any single PO over **$10,000** needs a one-line rationale included with the\n  PO so ops can copy it into the ERP.\n- If you place **more than five POs** in one task, end with a one-line total\n  committed spend.\n- Do not place a second PO for a SKU that already has an open PO covering the\n  need.\n\n## Output\n\nWhen you act, append to `\u002Fmnt\u002Fuser\u002Fsinks\u002Fpurchase_orders.jsonl`:\n```json\n{\"sku\": \"SKU-0057\", \"supplier_id\": \"SUP-03\", \"qty\": 700, \"expedite\": true, \"reason\": \"below reorder point; 2.1d cover\"}\n```\n\nWhen you only recommend (no side-effect requested), return a structured `ReorderDecision`:\n```json\n{\"sku\": \"...\", \"reorder\": true, \"qty\": 700, \"supplier_id\": \"SUP-03\", \"expedite\": true, \"confidence\": 0.85, \"notes\": \"...\"}\n```\n",{"name":5,"description":7},"main","2c65d16c6de16f8f24117d539a712ea706b5dee7","agent-decomposition\u002F.claude\u002Fskills\u002Freorder-policy",713,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-05 02:53:17",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add anthropics\u002Fcwc-workshops --skill reorder-policy",{"tool":50,"command":51},"bunx","bunx skills add anthropics\u002Fcwc-workshops --skill reorder-policy",{"tool":53,"command":54},"pnpm","pnpm dlx skills add anthropics\u002Fcwc-workshops --skill reorder-policy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fagent-decomposition\u002F.claude\u002Fskills\u002Freorder-policy\u002FSKILL.md",true,[],[59,90,110,121,147,166],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":75,"publishedAt":31},"01M718CS4VJNEW3SRN5S3MG35W","postmortem-report","How the SRE team writes a postmortem PDF. Use this whenever asked for a postmortem, an incident report, a write-up to share, or a PDF of what happened.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fship-your-first-managed-agent\u002Fskills\u002Fpostmortem-report\u002FSKILL.md",[65,70],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[76,77,78,79,80,81,82,83,84,85,86,87,22,88,89],"postmortem report","postmortem","report","share","what happened","team","use","incident report","up","write","incident","for","PDF","sre",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":31},"01M718CPE2QT7TQMYAG56R19JW","incident-triage-runbook","The SRE team's runbook for triaging production latency and error-rate incidents. Use this whenever investigating an incident, a latency spike, elevated error rates, or when asked \"what caused X\" about a production service.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fship-your-first-managed-agent\u002Fskills\u002Fincident-triage-runbook\u002FSKILL.md",[],[97,98,99,86,100,101,89,102,87,103,104,81,105,82,106,107,108,109],"runbook","triage","incident triage","incident triage runbook","error","latency","about","incidents","when","service","spike","Production","rate",{"skillNo":111,"name":112,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":31},"01M718CMK6R22RHEBDN1VW1YB5","eval-audit-and-sweep","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Frightmodel\u002F.claude\u002Fskills\u002Feval-audit-and-sweep\u002FSKILL.md",[],[116,117,118,119,120],"sweep","audit","eval audit and sweep","eval audit","eval",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":130,"publishedAt":31},"01M718CJ7RTEG518SSEJMH3H8H","edgartools-sec-data","How to pull SEC EDGAR data with the edgartools Python package — company lookup, filings, XBRL financial statements, and filing sections like Item 1A risk factors. Use whenever a task involves SEC filings, 10-K\u002F10-Q data, or company financials.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fresearch-desk\u002Fskills\u002Fedgartools\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000033","数据分析师",[131,132,133,134,135,136,22,137,30,82,138,27,139,140,141,142,143,144,145,146],"edgartools","edgartools sec data","data","lookup","filing","financial statements","with","package","python","company","company lookup","filings","risk","sec edgar","financials","pull",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":156,"publishedAt":31},"01M718CF9KPNBKPWFJN27XDN6A","workshop","Workshop coach for the Research Desk (SEC agents) workshop. Use when the user types \u002Fworkshop, asks for a workshop act or module (\"act 2\", \"next act\", \"where am I\"), wants a TODO(workshop-N) implemented or explained, or asks for help following WORKSHOP.md.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fresearch-desk\u002F.claude\u002Fskills\u002Fworkshop\u002FSKILL.md",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":68,"taxonomyTypeDesc":69},"01JBSEEDCAT000000000000021","资料检索与研究",[149,157,105,82,158,159,87,160,161,162,163,164,165],"todo","module","coach","types","research","user","act","help","next",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"publishedAt":31},"01M718CD3EBG31CBH0KSPVX0YR","weekly-report","Structure and data sources for the weekly inventory report. Load this when the task is \"weekly report\", \"Monday report\", or \"summarize inventory status\".","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fagent-decomposition\u002F.claude\u002Fskills\u002Fweekly-report\u002FSKILL.md",[172],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},[174,175,78,105,176,30,28,133,177,178,87,179,180,181,182],"Weekly Report","weekly","summarize","status","inventory","data sources","monday","structure","sources"]