Skip to main content
skill CX Codex

sales-forecast — Claude Code skill: sales forecasting

sales-forecast turns historical sales data into an Excel forecast with scenarios and sensitivity analysis. Use it to examine seasonality or plan sales for a chosen horizon.

Apache-2.0 ★ 12,746 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add genspark-ai/genoffice --skill sales-forecast -a claude-code
Open on GitHub

What sales-forecast does

The skill checks the sales history for missing periods and anomalies, then calculates a trend and seasonal factors. You can set the forecast horizon and data granularity, and supply known future changes such as a price increase or a new product. Seasonal decomposition requires two complete cycles; with less history, the forecast uses trend only.

The Excel workbook has five sheets: History, Assumptions, Forecast, Sensitivity, and Notes. Forecast values come from worksheet formulas, while adjustable assumptions and scenario settings are recorded separately. The Forecast sheet includes a chart of actuals, the forecast, and its interval.

The interval is statistical, not a commitment, and the user sets sales targets separately. You decide how anomalies should be treated; if keeping and excluding them produce materially different results, the skill calculates both. For product or regional forecasts, it forecasts each series before aggregating them.

What it helps with

  • forecast sales from historical data
  • inspect seasonality in monthly sales
  • compare optimistic, base, and pessimistic scenarios
  • measure how assumptions affect the yearly total
  • compare forecasts with and without anomalies

Example prompts for the agent

  • Forecast next year from this monthly sales data and create the Excel workbook.
  • Create optimistic, base, and pessimistic scenarios for this sales history.
  • Check for seasonality, flag anomalies, and show how assumptions affect the full-year total.

How to install sales-forecast

1Skills CLI (Vercel)

npx skills add genspark-ai/genoffice --skill sales-forecast -a claude-code

2Manually: put the files in place

~/.claude/skills/sales-forecast/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/sales-forecast/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about sales-forecast

How do I install sales-forecast in Claude Code?

Run npx skills add genspark-ai/genoffice --skill sales-forecast -a claude-code. The skill file is at ~/.claude/skills/sales-forecast/SKILL.md.

What does sales-forecast do?

It analyzes historical sales and produces an Excel workbook with a forecast, scenarios, bounds, and sensitivity analysis. The workbook also records assumptions and notes about the method.

How much history does seasonal forecasting require?

Monthly data needs at least two complete cycles, or 24 months. With less data, the skill forecasts the trend without seasonal decomposition.

Source text

SKILL.md · Apache-2.0
---
name: sales-forecast
description: Forecast sales from historical data using trend and seasonality, with confidence bands, scenarios, sensitivity analysis and an assumptions note, delivered as an Excel workbook
category: data
scenarios: Sales forecasting | Seasonality analysis | Target setting
quickPrompts: Forecast next year from these two years of monthly sales | Give this forecast optimistic, base and pessimistic scenarios
metadata:
  version: 1.0.0
---

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.
- Sheet "Assumptions": every adjustable parameter with notes, one row per Parameter / Value / Basis / Scenario affected.
- Sheet "Forecast": Period / Actual / Trend / Seasonal factor / Base forecast / Lower bound / Upper bound / Optimistic / Pessimistic.
- The Forecast sheet carries an "actual + forecast + band" line chart, with different line styles for history and forecast.
- Sheet "Sensitivity": assumption x change x effect on full-year total.
- Sheet "Notes": method, data range, exclusions, limitations, how to update.

## Rules

- Forecast values must come from formulas, never typed.
- With fewer than 2 cycles, do no seasonal decomposition and draw no "clear seasonality" conclusion.
- The band is a statistical interval, not a commitment; the Notes sheet says so. A forecast is not a target; targets are set separately by the user.
- Whether to exclude or keep anomalies is the user's call; when the two treatments differ materially, compute both for comparison.
- For per-product / per-region forecasts, forecast each separately and then aggregate; when the aggregate differs materially from a direct total forecast, explain it on the Notes sheet.
- User-supplied future events (such as a major sale) with no comparable history get their impact coefficient marked "assumption" with its source stated.

## Output

One Excel workbook (History / Assumptions / Forecast / Sensitivity / Notes, five sheets). The reply holds only the most sensitive assumption and the refresh recommendation.

© genspark-ai · Apache-2.0 · genspark-ai/genoffice

Similar skills

All skills for Data and databases →

From the same set65

The whole set →
executive-deck executive-deck is a Claude Code skill that builds executive presentations with a conclusion in each slide title. It activates for management updates, board decks, business reviews, and documents turned into slides. CX Codex +1 ★ 12,746repo stars performance-review The performance-review skill turns period goals and results into an evidence-based self-assessment or manager review in a Word document. Use it for goal retrospectives. CX Codex +1 ★ 12,746repo stars data-cleaning data-cleaning audits a messy spreadsheet, agrees cleaning rules with you, then returns an Excel workbook with the clean table, a row-by-row log and the duplicates it would not merge on its own. CX Codex +1 ★ 12,746repo stars onboarding-plan onboarding-plan generates structured 30/60/90-day onboarding spreadsheets with milestones, resources, and manager checkpoints in Excel. CX Codex +1 ★ 12,746repo stars survey-analyst survey-analyst turns a raw survey export into a cleaned Excel workbook and a Word findings report, cross-tabs and charts included. CX Codex +1 ★ 12,746repo stars swot-strategy swot-strategy conducts SWOT and PEST reviews for a company or product, benchmarks competitors, and compiles an actionable Word document with prioritized initiatives. CX Codex +1 ★ 12,746repo stars business-report This skill turns notes and source files into a structured Word business report. Use it for memos, reviews, or analysis that need sourced figures and a consistent voice. CX Codex +1 ★ 12,746repo stars sop-writer sop-writer turns how the work happens today into an SOP or policy document in Word, with roles, steps, checkpoints and version history. CX Codex +1 ★ 12,746repo stars

Project sponsors

Companies that keep this analytics open