Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Ai Ml Timeseries

ASecurity

Time series forecasting — LightGBM, Transformers, temporal validation, feature engineering, and production deployment. Use when building TS models.

3 stars
0 votes
0 copies
0 views
Added 9/20/2026
ai-agentsgosqltestingdebuggingperformance

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add joaoguirunas/team-os --skill ai-ml-timeseries --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ai Ml Timeseries?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Ai Ml Timeseries
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/joaoguirunas-ai-ml-timeseries/badge)](https://www.skillsdirectory.com/skills/joaoguirunas-ai-ml-timeseries)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: ai-ml-timeseries
description: "Time series forecasting — LightGBM, Transformers, temporal validation, feature engineering, and production deployment. Use when building TS models."
version: "1.0"
updated: "2026-09-04"
---

# Time Series Forecasting — Modern Patterns & Production Best Practices

**Modern Best Practices (January 2026)**:

- Treat **time** as a first-class axis: temporal splits, rolling backtests, and point-in-time correctness.
- Default to **strong baselines** (naive/seasonal naive) before complex models.
- Prevent leakage: feature windows and aggregations must use only information available at prediction time.
- Evaluate by **horizon** and **segment**; a single aggregate metric hides failures.
- Prefer **probabilistic** forecasts when decisions are risk-sensitive (quantiles/intervals); evaluate calibration (coverage) and use pinball/CRPS.
- For many related series, consider **global + hierarchical** approaches (shared models + reconciliation); validate across levels and key segments.
- Treat **time zones/DST** as first-class; validate timestamp alignment before feature generation.
- Define retraining cadence and degraded modes (fallback model, last-known-good forecast).

This skill provides **operational, copy-paste-ready workflows** for forecasting with recent advances: TS-specific EDA, temporal validation, lag/rolling features, model selection, multi-step forecasting, backtesting, generative AI (Chronos, TimesFM), and production deployment with drift monitoring.

It focuses on **hands-on forecasting execution**, not theory.

---

## When to Use This Skill

Claude should invoke this skill when the user asks for **hands-on time series forecasting**, e.g.:

- "Build a time series model for X."
- "Create lag features / rolling windows."
- "Help design a forecasting backtest."
- "Pick the right forecasting model for my data."
- "Fix leakage in forecasting."
- "Evaluate multi-horizon forecasts."
- "Use LLMs or generative models for TS."
- "Set up monitoring for a forecast system."
- "Implement LightGBM for time series."
- "Use transformer models (TimesFM, Chronos) for forecasting."
- "Apply temporal classification/survival modelling for event prediction."

If the user is asking about **general ML modelling, deployment, or infrastructure**, prefer:

- [ai-ml-data-science](../ai-ml-data-science/SKILL.md) - General data science workflows, EDA, feature engineering, evaluation
- For deployment, monitoring, drift detection, and retraining: [references/production-deployment-patterns.md](references/production-deployment-patterns.md) in this skill

LLM/RAG/search topics are out of scope here; for LLMs applied to time series (Chronos, TimesFM), see [references/ts-llm-patterns.md](references/ts-llm-patterns.md).

---

## Quick Reference

| Task | Tool/Framework | Command | When to Use |
|------|----------------|---------|-------------|
| TS EDA & Decomposition | Pandas, statsmodels | `seasonal_decompose()`, `df.plot()` | Identifying trend, seasonality, outliers |
| Lag/Rolling Features | Pandas, NumPy | `df.shift()`, `df.rolling()` | Creating temporal features for ML models |
| Model Training (Tree-based) | LightGBM, XGBoost | `lgb.train()`, `xgb.train()` | Tabular TS with seasonality, covariates |
| Deep Learning (Sequence models) | Transformers, RNNs | `model.forecast()` | Long-term dependencies, complex patterns |
| Event forecasting | Binary/time-to-event models | Temporal labeling + rolling validation | Sparse events and alerts |
| Backtesting | Custom rolling windows | `for window in windows: train(), test()` | Temporal validation without leakage |
| Metrics Evaluation | scikit-learn, custom | `mean_absolute_error()`, MAPE, MASE | Multi-horizon forecast accuracy |
| Production Deployment | MLflow, Airflow | Scheduled pipelines | Automated retraining, drift monitoring |

---

## Decision Tree: Choosing Time Series Approach

```text
User needs time series forecasting for: [Data Type]
    ├─ Strong Seasonality?
    │   ├─ Simple patterns? → LightGBM with seasonal features
    │   ├─ Complex patterns? → LightGBM + Prophet comparison
    │   └─ Multiple seasonalities? → Prophet or TBATS
    │
    ├─ Long-term Dependencies (>50 steps)?
    │   ├─ Transformers (TimesFM, Chronos) → Best for complex patterns
    │   └─ RNNs/LSTMs → Good for sequential dependencies
    │
    ├─ Event Forecasting (binary outcomes)?
    │   └─ Temporal classification / survival modelling → validate with time-based splits
    │
    ├─ Intermittent/Sparse Data (many zeros)?
    │   ├─ Croston/SBA → Classical intermittent methods
    │   └─ LightGBM with zero-inflation features → Modern approach
    │
    ├─ Multiple Covariates?
    │   ├─ LightGBM → Best with many features
    │   └─ TFT/DeepAR → If deep learning needed
    │
    └─ Explainability Required (healthcare, finance)?
        ├─ LightGBM → SHAP values, feature importance
        └─ Linear models → Most interpretable
```

---

## Core Concepts (Vendor-Agnostic)

- **Time axis**: splits, features, and labels must respect time ordering and availability.
- **Non-stationarity**: seasonality, trend, and regime shifts are normal; monitor and retrain intentionally.
- **Evaluation**: rolling/expanding backtests; report horizon-wise and segment-wise performance.
- **Operationalization**: define retraining cadence, fallback models, and data freshness contracts.
- **Data governance**: treat time series as potentially sensitive; enforce access control, retention, and PII scrubbing in logs.

## Implementation Practices (Tooling Examples)

- Build features with explicit time windows; store cutoff timestamps with each training run.
- Backtest with a standardized harness (rolling/expanding windows, horizon-wise metrics).
- Log production forecasts with metadata (model version, horizon, data cut) to enable debugging.
- Implement fallbacks (baseline model, last-known-good, “insufficient data” handling) for outages and anomalies.

## Do / Avoid

**Do**
- Do start with naive/seasonal naive baselines and compare against learned models (Forecasting: Principles and Practice: https://otexts.com/fpp3/).
- Do backtest with rolling windows and preserve point-in-time correctness.
- Do monitor for data pipeline changes (missing timestamps, level shifts, calendar changes).
- Do align metrics/loss to the decision: asymmetric costs, service levels, and probabilistic targets (quantiles/intervals) when needed.

**Avoid**
- Avoid random splits for forecasting problems.
- Avoid features that use future information (future aggregates, leakage via target encoding).
- Avoid optimizing only aggregate metrics; always inspect horizon-wise errors and worst segments.
- Avoid MAPE when the target can be 0 or near-0; prefer MASE/WAPE/sMAPE and horizon-wise reporting.

## Navigation: Core Patterns

### Time Series EDA & Data Preparation

- **[TS EDA Best Practices](references/ts-eda-best-practices.md)**
  - Frequency detection, missing timestamps, decomposition
  - Outlier detection, level shifts, seasonality analysis
  - Granularity selection and stability checks

### Feature Engineering

- **[Lag & Rolling Patterns](references/lag-rolling-patterns.md)**
  - Lag features (lag_1, lag_7, lag_28 for daily data)
  - Rolling windows (mean, std, min, max, EWM)
  - Avoiding leakage, seasonal lags, datetime features

### Model Selection

- **[Model Selection Guide](references/model-selection-guide.md)**
  - Decision rules: Strong seasonality → LightGBM, Long-term → Transformers
  - Benchmark comparison: LightGBM vs Prophet vs Transformers vs RNNs
  - Explainability considerations for mission-critical domains

- **[LightGBM TS Patterns](references/lightgbm-ts-patterns.md)** *(feature-based forecasting best practices)*
  - Why LightGBM excels: performance + efficiency + explainability
  - Feature engineering for tree-based models
  - Hyperparameter tuning for time series

### Forecasting Strategies

- **[Multi-Step Forecasting Patterns](references/multistep-forecasting-patterns.md)**
  - Direct strategy (separate models per horizon)
  - Recursive strategy (feed predictions back)
  - Seq2Seq strategy (Transformers, RNNs for long horizons)

- **[Intermittent Demand Patterns](references/intermittent-demand-patterns.md)**
  - Croston, SBA, ADIDA for sparse data
  - LightGBM with zero-inflation features (modern approach)
  - Two-stage hurdle models, hierarchical Bayesian

### Validation & Evaluation

- **[Backtesting Patterns](references/backtesting-patterns.md)**
  - Rolling window backtest, expanding window
  - Temporal train/validation split (no IID splits!)
  - Horizon-wise metrics, segment-level evaluation

### Generative & Advanced Models

- **[TS-LLM Patterns](references/ts-llm-patterns.md)**
  - Chronos, TimesFM, Lag-Llama (Transformer models)
  - Event forecasting patterns (temporal classification, survival modelling)
  - Tokenization, discretization, trajectory sampling

### Production Deployment

- **[Production Deployment Patterns](references/production-deployment-patterns.md)**
  - Feature pipelines (same code for train/serve)
  - Retraining strategies (time-based, drift-triggered)
  - Monitoring (error drift, feature drift, volume drift)
  - Fallback strategies, streaming ingestion, data governance

### Advanced Forecasting

- **[Anomaly Detection Patterns](references/anomaly-detection-patterns.md)**
  - Statistical, ML, and deep learning anomaly detectors for time series
  - Threshold tuning, alert fatigue reduction, seasonal adjustment

- **[Hierarchical Forecasting](references/hierarchical-forecasting.md)**
  - Bottom-up, top-down, and reconciliation methods
  - Cross-level coherence, grouped series, MinT/WLS approaches

- **[Probabilistic Forecasting](references/probabilistic-forecasting.md)**
  - Quantile regression, conformal prediction, prediction intervals
  - Calibration metrics (CRPS, pinball loss, coverage), decision-making under uncertainty

---

## Navigation: Templates (Copy-Paste Ready)

### Data Preparation

- **[TS EDA Template](assets/timeseries/template-ts-eda.md)** - Reproducible structure for time series analysis
- **[Resample & Fill Template](assets/timeseries/template-resample-fill.md)** - Handle missing timestamps and resampling

### Feature Templates

- **[Lag & Rolling Features](assets/timeseries/template-lag-rolling.md)** - Create temporal features for ML models
- **[Calendar Features](assets/timeseries/template-calendar-features.md)** - Business calendars, holidays, events

### Model Templates

- **[Forecast Model Template](assets/timeseries/template-forecast-model.md)** - End-to-end forecasting pipeline (LightGBM, transformers, RNNs)
- **[Multi-Step Strategy](assets/timeseries/template-multistep-strategy.md)** - Direct, recursive, and seq2seq approaches

### Evaluation Templates

- **[Backtest Template](assets/timeseries/template-backtest.md)** - Rolling window validation setup
- **[TS Metrics Template](assets/timeseries/template-ts-metrics.md)** - MAPE, MAE, RMSE, MASE, pinball loss

### Advanced Templates

- **[TS-LLM Template](assets/timeseries/template-ts-llm.md)** - Time series foundation model patterns and experimental approaches

---

## Related Skills

For adjacent topics, reference these skills:

- **[ai-ml-data-science](../ai-ml-data-science/SKILL.md)** - EDA workflows, feature engineering patterns, model evaluation, SQLMesh transformations
- **[data-sql-optimization](../data-sql-optimization/SKILL.md)** - SQL optimization for time series data storage and retrieval

Production deployment, monitoring, and retraining pipelines: [references/production-deployment-patterns.md](references/production-deployment-patterns.md). Time series LLMs (fine-tuning and prompting for Chronos/TimesFM): [references/ts-llm-patterns.md](references/ts-llm-patterns.md).

---

## External Resources

See [data/sources.json](data/sources.json) for curated web resources including:

- Classical methods (statsmodels, Prophet, ARIMA)
- Deep learning frameworks (PyTorch Forecasting, GluonTS, Darts, NeuralProphet)
- Transformer models (TimesFM, Chronos, Lag-Llama, Informer, Autoformer)
- Anomaly detection tools (PyOD, STUMPY, Isolation Forest)
- Feature engineering libraries (tsfresh, TSFuse, Featuretools)
- Production deployment (Kats, MLflow, sktime)
- Benchmarks and datasets (M5 Competition, Monash Time Series, UCI)

---

## Usage Notes

**For Claude:**

- Activate this skill for hands-on forecasting tasks, feature engineering, backtesting, or production setup
- Start with [Quick Reference](#quick-reference) and [Decision Tree](#decision-tree-choosing-time-series-approach) for fast guidance
- Drill into references/ for detailed implementation patterns
- Use assets/ for copy-paste ready code
- Always check for temporal leakage (future data in training)
- Start with strong baselines; choose model family based on horizon, covariates, and latency/cost constraints
- Emphasize explainability for healthcare/finance domains
- Monitor for data distribution shifts in production

**Key Principle:** Time series forecasting is about temporal structure, not IID assumptions. Use temporal validation, avoid future leakage, and choose models based on horizon length and data characteristics.

## Fact-Checking

- Use web search/web fetch to verify current external facts, versions, pricing, deadlines, regulations, or platform behavior before final answers.
- Prefer primary sources; report source links and dates for volatile information.
- If web access is unavailable, state the limitation and mark guidance as unverified.

Attribution

joaoguirunasjoaoguirunas
View sourceMore from joaoguirunas →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

1023331 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3331 votes

catchup

Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.

611 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →