Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/time-series-analysis

@9449d36
Run it yourself

Temporal pattern detection and forecasting. Use when analyzing trends over time, detecting seasonality, identifying anomalies in time series, or building simple forecasting models for planning.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/time-series-analysis

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈54 tokens for metadata: the name and description. ≈654 when used: this file. ≈1.5k more on demand in 2 files.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈216 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Time Series Analysis

When to use

  • Building a forecast for operational planning (staffing, inventory, infrastructure capacity)
  • Identifying whether a trend is genuine or driven by seasonality
  • Detecting anomalies in a metric stream (traffic spikes, revenue dips, error rate surges)
  • Providing a "what would have happened" baseline for measuring initiative impact
  • Presenting year-over-year growth in a way that accounts for seasonal patterns

Process

  1. Load and inspect the time series — confirm regular intervals (fill gaps if needed), check for obvious data quality issues (negative values, zeros in non-zero series), and identify the natural granularity (daily, weekly, monthly).
  2. Test for stationarity — run an ADF test. If non-stationary (trend or seasonality present), note this — it informs decomposition and model choice rather than blocking analysis. See references/ts_patterns_guide.md.
  3. Decompose into components — separate the time series into trend, seasonal, and residual using additive or multiplicative decomposition. Measure the strength of each component (0–1). Strong seasonality (>0.6) means raw values are misleading without seasonal adjustment.
  4. Detect anomalies — flag points more than 3 standard deviations from the rolling median. Investigate the top 5 anomalies against the event log (product releases, campaigns, incidents). Use scripts/ts_analyzer.py --detect-anomalies.
  5. Fit a forecast model — fit an ARIMA model (or simpler moving average if data is short). Validate on a held-out 20% test set and report MAPE. Generate point estimates and 95% confidence intervals for the forecast horizon.
  6. Produce the analysis report — summarise trend direction and strength, seasonal patterns and their business implications, anomaly findings, and the forecast with uncertainty. Use assets/ts_report_template.md.

Inputs the skill needs

  • Time series data: date column + one numeric metric column, minimum 2 full seasonal cycles
  • Granularity of the data (daily, weekly, monthly)
  • Forecast horizon required (days, weeks, months ahead)
  • Event log or change log for anomaly investigation
  • Business context: what drives this metric, known seasonal patterns

Output

  • scripts/ts_analyzer.py — decomposes, detects anomalies, and fits an ARIMA forecast; outputs charts and CSV
  • references/ts_patterns_guide.md — stationarity, seasonality types, model selection guide, and common pitfalls
  • assets/ts_report_template.md — report template: characteristics, decomposition summary, anomaly list, forecast table, insights

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is designed for time series analysis and appears safe for general use, using only standard libraries for statistical calculations. A minor security consideration is identified regarding indirect prompt injection, as the skill processes external CSV data and incorporates non-numeric fields into generated reports without sanitization.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/time-series-analysis