agentleFS
genspark-aigenspark-ai/genoffice/skills/recommended/sales-forecast/SKILL.md

sales-forecast

Skill11k starsChanged 3 months agoApache-2.0View on GitHub

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

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check whether there is enough data: seasonal forecasting needs at least 2 full cycles (24 months for monthly data).

    line 15
  2. Distinctive:

    Ask about the forecast horizon, granularity, basis (units or revenue, tax-inclusive or not, returns included or not) and known future …

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about genspark-ai/genoffice

The biggest 5 of 66 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 66

Talked about on GitHub, YouTube, Bluesky, the web and Hacker News (66 times).

On GitHub · 31

26 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On the web · 4

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.