Climate Analysis logo

Climate Analysis

Community
SteadfastAsArt
climate-analysis

Analyse labelled climate time series and gridded or station observations with checked calendars, aggregation, climatological baselines and spatial validation. Use for climate anomalies, regional summaries or station-to-grid analysis; distinguish descriptive analysis from future-time prediction.

Overview

PublisherSteadfastAsArt
Repositorygeoscience-skills
Skill nameclimate-analysis
Stars
75
Forks
9
Bundled files
2
LicenseMIT
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.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by SteadfastAsArt on GitHub. Read the source before you install it.

Installation

Install the Climate Analysis 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/SteadfastAsArt/geoscience-skills/tree/main/workflows/climate-analysis
  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/SteadfastAsArt/geoscience-skills.git /tmp/geoscience-skills
mkdir -p .claude/skills
cp -r /tmp/geoscience-skills/workflows/climate-analysis .claude/skills/climate-analysis
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Climate Analysis 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 Climate Analysis 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 Climate Analysis 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.

Climate Analysis

Use xarray for labelled climate arrays and verde only when scattered spatial observations need interpolation. Existing regular grids do not require a new interpolation stage. Run the relevant stages in one agent; companion skills are helpful references rather than mandatory registrations.

Define the data contract

Identify the variable, physical units, spatial support, timestamp meaning, calendar, time bounds, missing-value encoding and source/version before combining files. Check coordinate uniqueness and order, longitude convention, latitude direction, projection, vertical level and ensemble/member dimensions. Preserve non-Gregorian calendars; do not silently coerce them into ordinary timestamps.

Distinguish an instantaneous value, interval mean, accumulated amount and rate. For precipitation or energy fluxes, use the time bounds and unit definition to decide integration or summation. Do not apply the same resampling operation to temperature means and accumulated rainfall. Record source URLs, licences and checksums; use the pooch skill only when downloading is actually requested.

Select the analysis

DeliverableMain stepsValidation partition
Climatology/anomaliesSpecify baseline years, calendar grouping, coverage and weightsDocument baseline overlap; no forecasting claim from descriptive anomalies
Regional averagesUse cell areas or justified spatial weights and a fixed maskCheck missing coverage and area/weight normalisation for each period
Station-to-grid productProject coordinates appropriately, fit a spatial model, mask unsupported regionsWithhold spatial blocks or stations before fitting any preprocessing
Forecast/downscaling evaluationDefine issue time, lead time and predictor availability, then fitWithhold future time periods and unseen locations as required by deployment

Aggregate without losing meaning

Choose an explicit coverage rule for incomplete months/seasons and retain a coverage/count variable. Weight monthly means by represented duration, respecting the dataset's calendar; the xarray seasonal-mean example illustrates calendar-aware weighting. Renormalise over valid support only when that matches the stated estimand; never turn an entirely missing region or period into a zero observation.

Use supplied cell areas for irregular/projected grids. Cosine-latitude weights are an approximation for suitable regular longitude/latitude grids, not a general area calculation. Define whether December belongs to the following winter year before grouping DJF; a long-term seasonal climatology and a sequence of individual seasonal means are different outputs.

For anomalies, record baseline years and grouping. In prediction experiments, estimate climatology, trends, scaling, missing-value models and bias corrections using training data only. Do not allow centred windows, filled gaps or target aggregation windows to reach into future observations unavailable at issue time.

Spatial modelling and validation

For station observations, retain station identifiers and repeated-observation groups. Use a distance-appropriate CRS for a regional planar model; do not feed unqualified geographic degrees into metre-scale block sizes. Fit trends, normalisation, hyperparameters and interpolation within each training fold.

Use Verde spatial block validation when evaluating interpolation away from measured stations. Choose block size and any buffer from spatial support/dependence and the intended deployment; randomly splitting neighbouring samples can overstate performance. For future predictions, also hold out contiguous time periods. A station appearing in both sets may still be valid for a same-station forecast, but does not test an unseen location; state which question the split answers.

Outputs and uncertainty

Export a labelled dataset retaining units, calendar, CRS, baseline, masks and coverage, plus a record of processing choices and package versions. Reopen the output and check coordinates, dimensions and selected analytical summaries. Report errors by location/season and against a suitable climatology or persistence baseline. Account for temporal/spatial dependence when estimating uncertainty; model spread is not automatically a calibrated predictive interval, and trend significance is not causal attribution.

Executed station case

The NOAA station example executes the workflow from real daily maximum temperatures through QC, calendar-aware means, short-reference anomalies, spatial holdout and a labelled NetCDF export. Its offline script requires the recorded source and provenance files and preserves existing output directories.

The example separates each station's descriptive anomaly from a spatial model relative to a station-network reference. Every spatial fold learns that reference from training stations alone; the held-out station's past values are also excluded. The final grid contains model estimates, with a recorded support mask and spherical cell areas. A regional model mean is not a measured regional climate change.

Tests also cover synthetic 360_day/noleap calendars, missing coverage and all-NaN periods/regions. This verification does not establish forecasts, 30-year climate normals, homogenization, precipitation integration or arbitrary regridding accuracy. Use a data-specific validation for those branches.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Climate Analysis AI skill do?

Analyse labelled climate time series and gridded or station observations with checked calendars, aggregation, climatological baselines and spatial validation. Use for climate anomalies, regional summaries or station-to-grid analysis; distinguish descriptive analysis from future-time prediction.

Why use Climate Analysis on TypingMind?

Because you install it once and use it with any model. Climate Analysis 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 Climate Analysis in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/SteadfastAsArt/geoscience-skills/tree/main/workflows/climate-analysis. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Climate Analysis?

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 Climate Analysis?

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

Is the Climate Analysis AI skill free?

Yes. It is published on GitHub by SteadfastAsArt under the MIT 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 👇