Sales Forecast logo

Sales Forecast

OrganizationPopular
genspark-ai
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

Overview

Publishergenspark-ai
Repositorygenoffice
Skill namesales-forecast
Stars
11.3K
Forks
1.6K
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by genspark-ai on GitHub. Read the source before you install it.

Installation

Install the Sales Forecast AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/genspark-ai/genoffice/tree/main/skills/recommended/sales-forecast
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/genspark-ai/genoffice.git /tmp/genoffice
mkdir -p .claude/skills
cp -r /tmp/genoffice/skills/recommended/sales-forecast .claude/skills/sales-forecast
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Sales Forecast in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Sales Forecast on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Sales Forecast is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Frequently asked questions

What does the Sales Forecast AI skill do?

Forecast sales from historical data using trend and seasonality, with confidence bands, scenarios, sensitivity analysis and an assumptions note, delivered as an Excel workbook

Why use Sales Forecast on TypingMind?

Because you install it once and use it with any model. Sales Forecast is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Sales Forecast in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/genspark-ai/genoffice/tree/main/skills/recommended/sales-forecast. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Sales Forecast?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Sales Forecast?

As many as you like. As long as a model supports skills, you can use Sales Forecast with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Sales Forecast AI skill free?

Yes. It is published on GitHub by genspark-ai under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇