Structure and data sources for the weekly inventory report. Load this when the task is "weekly report", "Monday report", or "summarize inventory status".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Generate the report by writing one Python script via code execution that reads the CSVs and emits markdown. Do not make per-SKU tool calls.
# Inventory Report — {{warehouse or "All Warehouses"}} — week of {{date}}
## Stockouts (on_hand = 0)
| SKU | Product | Warehouse | Days out |
...
## Low Stock (below reorder point)
| SKU | On hand | Reorder pt | Days cover | Action |
...top 15 by urgency (lowest days_cover first)...
## Open POs
| PO | SKU | Qty | Supplier | ETA |
...from /mnt/user/sinks/purchase_orders.jsonl...
## Forecast Risk
SKUs where promo_next_month=1 or is_seasonal=1 and on_hand < 14d cover.
One line each: SKU, reason, recommended action.
| Cadence | Trigger phrasing | Contents |
|---|---|---|
| Daily | "run the check", "the sweep" | Low-stock list with action taken per SKU; one summary notification at the end. |
| Weekly (Mon) | "the report", "weekly review" | Per-warehouse: top concerns, open POs aging past their lead time, SKUs below reorder for >5 business days. |
| Monthly | "supplier review" | Suppliers whose on-time rate slipped; SKUs whose primary supplier may need changing. |
| Ad hoc | anything else | Scope to what was asked. |
If the request doesn't say which, infer from wording. The structure below is the weekly format; for daily, drop the Open-POs and Forecast-Risk sections and lead with the actions taken.
For each open PO, compare days-since-placed to the supplier's lead_time_days.
List any PO where elapsed > lead_time as aging and include supplier + days
overdue so ops can follow up.
/mnt/user/data/stock_levels.csv joined with /mnt/user/data/products.csvon_hand / avg_daily_sales (last 14d from /mnt/user/data/sales_history.csv)/mnt/user/sinks/purchase_orders.jsonl/mnt/user/data/products.csv flags + days-of-cover from aboveThe CSVs are large (stock_levels is ~67k rows). Write a single script that loads them once, computes everything, and prints the markdown. Don't page through the data with tool calls — that's exactly the pattern this skill replaces.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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/10-Q data, or company financials.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Where diamonds spawn in Minecraft 1.20.
The English summary is being prepared. Showing the original description.
Fixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops".
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.