Calibration Check logo

Calibration Check

Community
WalrusQuant
calibration-check

Evaluate whether sports-model probabilities match observed frequencies. Use for Brier score, log loss, reliability bins, ECE, segment checks, and recalibration decisions.

Overview

PublisherWalrusQuant
Repositorysports-analytic-skills
Skill namecalibration-check
Stars
53
Forks
4
Bundled files
5
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.

  • 5 bundled files

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

  • Open source

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

Installation

Install the Calibration Check 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/WalrusQuant/sports-analytic-skills/tree/main/skills/calibration-check
  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/WalrusQuant/sports-analytic-skills.git /tmp/sports-analytic-skills
mkdir -p .claude/skills
cp -r /tmp/sports-analytic-skills/skills/calibration-check .claude/skills/calibration-check
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Calibration Check 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 Calibration Check 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 Calibration Check 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.

Calibration Check (Sports)

Overview

A model can rank teams well and still be miscalibrated. If the model says 30%, about 30% of those cases should hit.

This skill measures probability reliability for sports models and supports a human-reviewed verdict grounded in evaluation provenance, uncertainty, and segment stability.

Discrimination metrics (AUC, accuracy) do not replace calibration.


When to Use This Skill

Use when:

  • Model outputs win/event probabilities
  • User asks how confident / how reliable the probs are
  • After walk-forward evaluation of a probability model
  • Before writing results that quote probability levels
  • Comparing raw vs recalibrated probabilities
  • sport- and competition-specific probability artifacts

Do not use when:

NeedGo instead
Pure ranking tasks with no probabilistic interpretationranking/eval skills
Hard labels only with no probability outputsclassification metrics only
Designing splits from scratchvalidation-design
Feature legality reviewleakage-audit
Margin-only models without probsMAE/RMSE reporting

Installation

The bundled scripts require pandas:

bash
python -m pip install pandas

Parquet input also needs pyarrow or fastparquet. Both scripts accept CSV, Parquet, JSON, JSONL, and NDJSON and expose --help without importing pandas.


What to Measure

  1. Reliability / calibration curve — bin predicted prob vs observed rate
  2. Expected Calibration Error (ECE)
  3. Brier score (+ reliability/resolution decomposition when useful)
  4. Log-loss — discrimination + calibration together; not a substitute for ECE
  5. Segment calibration — by season, home/away, probability tail
  6. Sharpness — are probs informative, not all ~0.5?

Read calibration_metrics.md when interpreting ECE, Brier score, log loss, or sharpness. Read binning.md before choosing bin edges or minimum counts. Read recalibration.md before fitting Platt, isotonic, or another probability correction.


Workflow

  1. Confirm predictions come from time-safe / walk-forward folds.
  2. Validate probabilities in [0, 1]; account for every excluded row.
  3. Pre-declare binning (fixed-width or quantile).
  4. Compute curve, ECE, Brier, log-loss.
  5. Slice by season and by probability tails.
  6. Issue a verdict (table below).
  7. If recalibrating, only with nested/train-proper methods — never fit isotonic on the final test fold and call it validated.
  8. Write the calibration report into experiment log / results writeup.

Verdict Scale

VerdictMeaning
well-calibratedReliability acceptable for quoting probabilities
usable-with-caveatsSome miscalibration; disclose and/or recalibrate properly
poorly-calibratedProbability numbers not trustworthy as probabilities
invalid-evalLeakage/split issues block judgment

These verdicts belong to the full methodology, not to a single ECE threshold. Before issuing one, verify that predictions are genuinely held out and walk-forward, inspect uncertainty and populated-bin counts, compare seasons or folds, check decision-relevant segments, and document the prediction source. No universal ECE cutoff establishes that probabilities are trustworthy.


Run on Held-Out Prediction Artifacts

The input must contain one row per evaluated decision, a binary outcome, and a probability in [0, 1].

Preferred portable names from this pack's baseline helper:

  • outcome: y_true
  • probability: p_pred (also emitted as logistic_probability)
bash
# After baseline-models/scripts/run_baselines.py --predictions-out ...
python /path/to/calibration-check/scripts/calibration_report.py \
  --input baseline-predictions.csv --target y_true --probability p_pred \
  --group-col season --bins 10 --out calibration.json

python /path/to/calibration-check/scripts/calibration_report.py \
  --input predictions.csv --target won --probability win_probability \
  --group-col season --bins 10 --out calibration.json

python /path/to/calibration-check/scripts/segment_calibration.py \
  --input predictions.csv --target won --probability win_probability \
  --segment-col is_home

Use --filter-col is_home --filter-value 1 for a symmetric team-game artifact when one home perspective per game is the actual evaluation unit. Do not double-count both sides of one event.

calibration_report.py returns Brier score, log loss, ECE, reliability-bin counts, row accounting, optional group metrics, and a conservative manual-review-required helper verdict. The script cannot prove held-out provenance or turn a favorable pooled ECE into well-calibrated; the analyst must apply the verdict scale above. segment_calibration.py prints all-row, categorical-segment, probability-tail metrics, and sparse-bin counts.


Binning Guidance

StrategyUse when
Equal-width (10 bins 0–1)default sports win probs
Quantile binsprobs clump in a narrow range
Tail focus (0–0.2, 0.8–1.0)decisions live in extremes

Always report bin counts. Empty bins are not evidence.


Recalibration Rules

Allowed

  • Platt scaling / isotonic fit inside training folds only, applied to test fold
  • Nested walk-forward recalibration

Not allowed

  • Fit isotonic on final test labels and call it validated
  • Hand-edit probabilities after seeing outcomes

After recalibration, re-report ECE/Brier on true forward folds.


Hard Constraints

  1. Never evaluate calibration on training rows used to fit the same model without nested disclosure.
  2. Never present raw scores as probabilities without checking calibration.
  3. Never hide segment failures behind a pooled “looks fine.”
  4. If sample per bin is tiny, say so — widen bins or reduce claim strength.
  5. Accuracy is not calibration.
  6. Leakage-invalid evaluations cannot be “well-calibrated.”

Anti-Patterns

  • “56% correct, so calibrated”
  • One reliability plot with no sample sizes
  • Holdout isotonic theater
  • Average prob ≈ base rate therefore calibrated (necessary, not sufficient)
  • Ignoring 0.05 and 0.95 tails
  • Quoting NBA/MLB percents without sport-specific calibration

Reporting Template

text
Calibration report
Sport/model:
Eval: walk-forward seasons …
n:
Brier:
ECE (bins=…):
Log-loss:
Notes by season:
Tail behavior:
Verdict: well-calibrated | usable-with-caveats | poorly-calibrated | invalid-eval
Actions:
Reproduce:

Output Contract

Done means:

  • Walk-forward probs used
  • ECE/Brier/log-loss reported
  • Bin counts or segment notes present
  • Verdict issued
  • Actions stated

Worked Example

bash
python /path/to/calibration-check/scripts/calibration_report.py \
  --input held-out-predictions.csv --target y_true \
  --probability logistic_probability --group-col season \
  --bins 10 --out calibration.json

python /path/to/calibration-check/scripts/segment_calibration.py \
  --input held-out-predictions.csv --target y_true \
  --probability logistic_probability --segment-col is_home

Example finding: predictions near 0.70 occur in sparse bins and realize near 0.60. Label the tail unstable or overconfident according to its uncertainty; do not infer a durable defect from a handful of rows.


Bundled Resources

references/

FileContents
calibration_metrics.mdECE/Brier/log-loss definitions
binning.mdbin strategy notes
recalibration.mdallowed recalibration patterns

scripts/

FileContents
calibration_report.pydescriptive calibration JSON for supplied prediction rows; provenance must be verified externally
segment_calibration.pyhome/away and tail slices

Related Skills

NeedSkill
Validation designvalidation-design
Predictive modelspredictive-modeling
Statistical modelsstatistical-modeling
Results writeupresults-reporting
Model cardmodel-card

Quick Command Card

bash
python /path/to/calibration-check/scripts/calibration_report.py \
  --input predictions.csv --target won --probability win_probability \
  --group-col season --bins 10 --out calibration.json

python /path/to/calibration-check/scripts/segment_calibration.py \
  --input predictions.csv --target won --probability win_probability \
  --segment-col is_home

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 Calibration Check AI skill do?

Evaluate whether sports-model probabilities match observed frequencies. Use for Brier score, log loss, reliability bins, ECE, segment checks, and recalibration decisions.

Why use Calibration Check on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/WalrusQuant/sports-analytic-skills/tree/main/skills/calibration-check. 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 Calibration Check?

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 Calibration Check?

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

Is the Calibration Check AI skill free?

It is published on GitHub by WalrusQuant. Check the repository for licensing terms. 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 👇