skforecast-ai

io.github.skforecastv0.4.0Updated Oct 9, 2026

Forecast time series in CSV files: deterministic skforecast workflows and the script that ran.

Overview

AI-generated overview

Lets an assistant forecast time series from CSV files with deterministic skforecast workflows and return the script that produced the result.

What it does
It profiles a time series, chooses a forecaster and estimator by fixed rules, builds a plan of lags, window and calendar features, then runs the forecast or backtest and returns predictions, metrics and the skforecast script that ran (R6, R34, R35, R36). Methods include profile, plan, refine_plan, create_cv, forecast, forecast_code, backtest, backtest_code, compare and ask (R54, R55, R56, R57, R58, R59, R60, R61). compare backtests several configurations and ranks them, and a seasonal naive baseline is included for a single series (R38, R39). The same input always gives the same profile, plan, script and predictions (R40).
When to use it
Use it when you want an assistant to forecast a CSV time series and show its work: every decision comes from a readable rule and every result comes with the script that produced it (R7). It suits coding agents such as Claude Code, Cursor or VS Code that should run the pipeline as tools (R30, R31, R42). The optional LLM layer is for explaining a result or refining a plan from domain knowledge (R46, R47).
Requirements
Local process run with uvx from the PyPI package skforecast-ai-mcp; requires Python 3.10 or newer (R14). No authentication, environment variables or headers are declared. The LLM layer is optional and needs an extra install plus provider credentials or a local model (R13, R27, R50).
Before you install
The optional LLM layer sends data to a third-party provider: a result shares only its own predictions and metrics, with a warning, and the dataset is never sent (R26). A prompt is always explicit, and nothing is sent to an LLM unless you ask for it (R52). LLM outputs are validated by a Pydantic model; invalid output falls back to the deterministic result with a warning (R49). Credentials for the chosen provider are configured separately (R27).

Installation

In SourceWeft

  1. Open skforecast-ai in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[skforecast-ai]

About skforecast-ai

The forecasting assistant that shows its work. Give skforecast-ai a time series: it profiles the data, chooses the model with deterministic rules, validates it and returns the forecast together with the skforecast script that produced it. Every decision comes from a rule you can read, the same data always gives the same result, and the script runs on its own with plain skforecast. An optional LLM explains every decision; it never makes them.

[skforecast-ai forecast of hourly bike sharing users with its 80% interval, and the ask() answer that explains the evaluation metrics]

36-hour LightGBM forecast of hourly bike sharing users, with its 80% prediction interval against the held-out hours, and the answer of ask() that explains its metrics. Real skforecast-ai outputs, from the animation on ai.skforecast.org.

Installation

bash
pip install skforecast-ai

The LLM layer is optional. To use it, install the extra ([bedrock] for AWS Bedrock):

bash
pip install "skforecast-ai[llm]"

Requires Python 3.10 or newer. More options in the installation guide; to install from source, see the Contribution Guide.

Quick example

python
from skforecast_ai import ForecastingAssistantfrom skforecast.datasets import load_demo_dataset
# Download demo dataset (monthly)data = load_demo_dataset(verbose=False)
# Profile the data, plan the model, generate the script and run it,# evaluated on the last 12 months. No LLM needed.assistant = ForecastingAssistant()result = assistant.forecast(data=data, target="y", steps=12, test_size=12)
result.predictions.head()#                 pred# 2007-07-01  0.851486# 2007-08-01  1.048000# 2007-09-01  0.998147# 2007-10-01  1.147577# 2007-11-01  1.110845
result.metrics#   series       MAE       MSE      MASE      MAPE# 0      y  0.078442  0.008933  0.802828  0.088608
print(result.code)  # the skforecast script that produced this result

That single call chose a ForecasterRecursive with a Ridge estimator, its lags and window features, and ran the script that result.code returns. result.profile and result.plan hold every decision and the rule behind it. Drop test_size to train on all the data and forecast the next 12 months.

Same pipeline from the terminal
bash
# End-to-end forecastskforecast-ai forecast data.csv --target y --date-column date --steps 12
# Only the standalone script, without running itskforecast-ai forecast-code data.csv --target y --date-column date --steps 12 --output forecast.py

The CLI covers the whole pipeline, including ask() and the prompts of refine_plan() and create_cv(). See Using the CLI.

Ask why (optional LLM)
python
# pip install "skforecast-ai[llm]"assistant = ForecastingAssistant(llm="openai:gpt-5.5")
answer = assistant.ask(    "Is the MASE good, and why was this estimator chosen?",    context=result,)

ask() reads the object you pass and explains it, grounded in the skforecast agent skills. It never changes the result. The dataset is never sent: a result shares only its own predictions and metrics, with a warning. Providers, credentials and local models are covered in Configuring the LLM.

From your coding agent (MCP server)

In Claude Code, install the server and its skill as a plugin:

text
/plugin marketplace add skforecast/skforecast-ai/plugin install skforecast-ai@skforecast-ai

Then ask in plain language: "Forecast the next 12 months of data/sales.csv and tell me how accurate it is." The agent brings the language model and calls skforecast-ai as tools; every decision still comes from the same deterministic rules, every result comes with the script that produced it, and responses never carry rows of your data. The setups for Cursor, VS Code, Codex and Claude Desktop are in MCP server for coding agents.

Features

A deterministic engine

  • Data profiling: frequency, missing values, exogenous and categorical variables, and the significant lags from the partial autocorrelation.
  • A plan with a rule for every decision: forecaster and estimator, lags, window and calendar features, prediction intervals, metric and cross-validation.
  • The code you see is the code that ran: forecast() and backtest() execute the same script that forecast_code() and backtest_code() return. Inspect it, version it or run it with plain skforecast.
  • Model selection with compare(): every candidate is backtested with the same data and cross-validation, and the ranking is a plain sort of the metric. For a single series, a seasonal naive baseline is ranked alongside them, so you also see whether a model beats the simplest reasonable forecast.
  • Reproducible: the same input always gives the same profile, plan, script and predictions.
  • Python or terminal: the CLI runs the same pipeline from a CSV file or URL.
  • Coding agents: an MCP server gives Claude Code, Cursor and other MCP clients the same pipeline as tools, with a skill that teaches them to use it. Responses never carry rows of your data.

The engine chooses among the forecasters of skforecast: recursive and direct, multi-series and multivariate, statistical (ARIMA) and foundation models.

An optional LLM layer

  • Explains a forecast, a backtest, a comparison, a plan or a script in plain language with ask(), or answers a general forecasting question.
  • Refines lags and window features from your domain knowledge with refine_plan(prompt=...).
  • Translates a deployment scenario into a backtesting strategy with create_cv(prompt=...).
  • Validated before it runs: every LLM output is checked by a Pydantic model; if it is not valid, you get the deterministic result and a warning.
  • Any provider through pydantic-ai: OpenAI, Anthropic, Google, Groq, AWS Bedrock, Ollama for local models, or any OpenAI-compatible endpoint.

Methods

All methods work without an LLM except ask(). A prompt is always explicit: nothing is sent to an LLM unless you ask for it.

MethodWhat it doesLLM
profile()Inspects the data and recommends a forecaster and an estimatorno
plan()Builds the plan: lags, window and calendar features, interval, metricno
refine_plan()Changes a plan with explicit overrides, or with a promptoptional
create_cv()Builds the cross-validation strategy, or translates a prompt into oneoptional
forecast(), forecast_code()Runs the forecast, or returns its script without running itno
backtest(), backtest_code()Runs the backtest, or returns its script without running itno
compare()Backtests several configurations and ranks themno
ask()Explains a profile, plan, script or result, or answers a questionrequired

How it works

skforecast-ai has two ways in, on the same engine. The fast path goes from data to a forecast or a backtest in one call. The step-by-step path returns each intermediate object (profile, plan, cross-validation) so you can inspect it, change it or refine it with the LLM before running anything. Both branch into forecasting and backtesting, compare() picks the best configuration from measured performance, and ask() explains any object along the way.

[How skforecast-ai works: the fast path runs profiling and planning inside forecast() or backtest(); the step-by-step path calls profile(), plan() and create_cv() so you can inspect each object. compare() ranks several configurations under the same cross-validation, and ask() explains any object at any moment.]

Read more in Agentic forecasting and Agentic forecasting step by step.

Documentation

The full documentation is available at https://ai.skforecast.org.

Documentation
Quick startInstall skforecast-ai, run your first forecast and ask the assistant
Agentic forecastingThe fast path: profile, forecast, backtest, compare and ask
Step by stepEvery intermediate object, and how to change it
Configuring the LLMProviders, credentials, local models and what is sent
Using the CLIThe same pipeline from the terminal
MCP server for coding agentsThe same pipeline as tools for Claude Code, Cursor and other MCP clients
API ReferenceForecastingAssistant, its results, schemas and the CLI
ReleasesWhat changed in each version

Part of the skforecast family

[Skforecast Docs] [GitHub] [Skforecast Studio]

  • skforecast: the forecasting library that runs every forecast of skforecast-ai. Machine learning, statistical and foundation models, backtesting and tuning.
  • Skforecast Studio: a no-code application to build forecasting models visually, which generates production-ready Python code.

Contributing

Bug reports, feature requests, code, tests and documentation are all welcome. Open an issue on GitHub Issues or read the Contribution Guide and the Code of Conduct to get started.

skforecast-ai is created and maintained by Joaquín Amat Rodrigo and Javier Escobar Ortiz, together with everyone who has contributed to it (about the project).

[skforecast-ai contributors]

Citation

If you use skforecast-ai in a scientific publication, please cite the version you used: each version has its own DOI and ready-made citations on Zenodo. To cite skforecast-ai in general, use the DOI that always resolves to the latest release.

APA:

Amat Rodrigo, J., & Escobar Ortiz, J. skforecast-ai [Computer software]. https://doi.org/10.5281/zenodo.21338159

BibTeX:

bibtex
@software{skforecast-ai,  author  = {Amat Rodrigo, Joaquin and Escobar Ortiz, Javier},  title   = {skforecast-ai},  license = {Apache-2.0},  url     = {https://ai.skforecast.org/},  doi     = {10.5281/zenodo.21338159}}

The citation metadata is also in CITATION.cff (GitHub's "Cite this repository" button).

Sponsorship and funding

skforecast-ai is built by the skforecast team. skforecast is free, open-source software supported by the Sovereign Tech Fund and by the organizations that sponsor it. If your company relies on skforecast or skforecast-ai, see Sponsorship and funding for sponsorship tiers, support agreements, feature sponsorship and training.

Individuals can support the project through Open Collective, Buy Me a Coffee, GitHub Sponsors (Joaquín Amat Rodrigo, Javier Escobar Ortiz) or PayPal.

[Support skforecast on Open Collective]  [Buy Me a Coffee]  [Sponsor skforecast on GitHub]

License

skforecast-ai software: Apache License 2.0. The underlying skforecast engine is distributed under its own BSD-3-Clause License.

skforecast-ai documentation: CC BY-NC-SA 4.0

Trademark: The trademark skforecast is registered with the European Union Intellectual Property Office (EUIPO) under the application number 019109684. Unauthorized use of this trademark, its logo, or any associated visual identity elements is strictly prohibited without the express consent of the owner.

Source: README.md at commit 1fb1c08

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.4.0LatestOct 9, 2026