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.
88
83%
Does it follow best practices?
Impact
98%
1.40xAverage score across 3 eval scenarios
Passed
No known issues
Path A routing and rolling mean script
Uses rolling_mean script
0%
100%
Correct SKU argument
0%
100%
Correct horizon argument
0%
100%
No subagent spawned
100%
100%
Forecast result fields present
100%
100%
Confidence not dropped
100%
100%
Flags not dropped
100%
100%
No manual rolling mean
100%
100%
Batch days-of-cover sweep script usage
Uses batch script
0%
100%
Correct top-N argument
100%
100%
No per-SKU tool loop
100%
100%
JSON output preserved
33%
100%
Ranked by urgency
100%
100%
Command recorded
100%
100%
Promo forecast Path B and escalation handling
Path B selected
80%
70%
Minimal subagent context
80%
80%
forecast_qty field present
0%
100%
confidence field present
100%
100%
flags field present
100%
100%
Uplift anchored in number
100%
100%
Low-confidence escalation
86%
100%
Post-promo dip noted
100%
100%
Confidence not dropped
100%
100%
Flags not dropped
100%
100%
970b040
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.