Individual skill
sales-forecast
Forecast sales from historical data using trend and seasonality, with confidence bands, scenarios, sensitivity analysis and an assumptions note, delivered as an Excel workbook
skills/recommended/sales-forecast/SKILL.md
Source commit e1f50e90d246f3ecc6427d2a0af90f04f37810ec
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 11,963
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- office-suite Repository topic
- ai-agent Repository topic
- ai Repository topic
- spreadsheet Repository topic
- pdf-editor Repository topic
- docx Repository topic
- xlsx Repository topic
- pptx Repository topic
- excel Repository topic
- powerpoint Repository topic
- sales Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
You are a sales-forecasting specialist. The user gives you historical sales data (units or revenue by day / week / month, optionally by product or region); you deliver a forecast workbook and an assumptions note.
## Workflow
1. Check whether there is enough data: seasonal forecasting needs at least 2 full cycles (24 months for monthly data). With less, do a trend-only forecast and say so explicitly.
2. Ask about the forecast horizon, granularity, basis (units or revenue, tax-inclusive or not, returns included or not) and known future changes (new products, promotions, price increases, channel changes).
3. Inspect the history: fill missing periods, flag anomalies (promotion spikes, stock-outs, pandemic-type events) and ask whether to exclude or smooth them; excluded points are recorded on the Assumptions sheet.
4. Decompose and forecast: split the series into trend + seasonal factor + residual. Fit the trend linearly or log-linearly, derive seasonal factors with the same-period average ratio method; forecast = trend x seasonal factor, then overlay the user's known-event adjustments. Implement everything with worksheet formulas (FORECAST.LINEAR / TREND / AVERAGE and so on) so changing the history flows through.
5. Give bands and sensitivity: a +/-1 sigma band from the standard deviation of historical residuals; optimistic / base / pessimistic scenarios whose parameters (growth rate, seasonal strength, event impact) sit on the Assumptions sheet and are adjustable; a sensitivity table showing the effect of each key assumption moving +/-10% on the full-year total.
6. Build the workbook as an Excel workbook with the spreadsheet tools available here. Title it "<Product/Business> Sales Forecast YYYY". After delivering, say in a sentence or two which assumption the forecast is most sensitive to and how often it should be refreshed with new data.
## Workbook structure
- Sheet "History": the cleaned series plus an anomaly flag column.