Quantitative Analysis logo

Quantitative Analysis

CommunityPopular
cbrock84
quantitative-analysis

Answers a business question with data without fooling yourself — framing the question so an answer would change something, choosing the right comparison, checking the data before trusting it, recognizing the traps that produce confident wrong answers (aggregation reversals, survivorship, regression to the mean, multiple comparisons), and reporting uncertainty honestly. Use this to run an analysis, review one before acting on it, or work out why two people looking at the same data reached opposite conclusions.

Overview

Publishercbrock84
Repositoryheadcount
Skill namequantitative-analysis
Stars
1.6K
Forks
237
Bundled files
1
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.

  • 1 bundled files

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

  • Open source

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

Installation

Install the Quantitative 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.
  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/cbrock84/headcount.git /tmp/headcount
mkdir -p .claude/skills
cp -r /tmp/headcount/plugins/data-analytics/skills/quantitative-analysis .claude/skills/quantitative-analysis
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Quantitative 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 Quantitative 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 Quantitative 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.

Quantitative analysis

A wrong answer here is rarely an arithmetic error. It is a correct calculation on the wrong comparison, or on data that does not mean what the field name suggests.

Frame the question so that an answer changes something

Start from the decision. "How is retention doing" has no answer; "is the cohort we changed onboarding for retaining better than the one before it, enough to justify rolling it out" does.

Write down what you expect to find and what you would do in each case before you look. If every possible result leads to the same action, the analysis is not worth running — and knowing that in advance is worth more than the analysis would have been.

Choose the comparison before the metric

Almost every meaningful number is a comparison, and the choice of what to compare against does more work than the calculation.

  • Against what it was — needs a period long enough to see through seasonality and noise.
  • Against what it would have been — the strongest comparison and the hardest to construct. A holdout group, a matched segment, a pre-trend extended forward.
  • Against a peer or a benchmark — only useful if the definitions genuinely match, which they usually do not.

Name the counterfactual explicitly. "Revenue rose after the campaign" is a comparison against nothing, and it is the single most common way credit is claimed for a trend that was already happening.

Interrogate the data before you trust it

Look at the raw rows. Check when collection started and whether the definition changed partway. Check null rates, duplicates, and test or internal accounts still in the set. Check whether recent periods are still filling in — partial data at the tail is what produces the "sudden decline" that resolves itself a week later.

A field's name is not its definition. Find out what actually writes it and under what conditions, especially for anything named status, type, active, or created.

Know the traps that produce confident wrong answers

  • Aggregation reversals. A rate can improve in every segment and worsen overall if the mix shifted. Always check whether the segments agree with the total, and where they disagree, the segments are the truth.
  • Survivorship. Analyzing only accounts still present answers a question about survivors. The ones that left are usually the ones the question was about.
  • Regression to the mean. Anything selected for being extreme moves back toward average on its own. Interventions aimed at the worst performers get credited with this routinely.
  • Multiple comparisons. Test twenty segments at the usual threshold and one will look significant by chance. Decide what you are testing before you slice.
  • Denominator drift. A ratio moves when either half moves. Show both.
  • Correlation with an obvious common cause. Two things driven by the same seasonality will track each other beautifully and explain nothing.

Segment before concluding, and stop before you overfit

Blended numbers hide the finding almost every time — one segment moving hard while the rest sit still. Split by the two or three dimensions that plausibly matter and check whether the effect is general or local.

Then stop. Slicing until something looks interesting finds noise, reliably, and the result will not replicate.

Report the uncertainty rather than burying it

Give the estimate, the range around it, and what would change the answer. State the sample size and the period. Say plainly what the analysis cannot determine — an analysis honest about its limits gets trusted on the things it can determine.

Distinguish what the data shows from what you infer. Both belong in the report; conflating them is how a plausible interpretation becomes a fact by the third time it is repeated.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Run an analysis that leads to the same action whatever it finds.
  • Report a change without naming what it is being compared against.
  • Conclude from a total when the segments disagree with it.
  • Slice until something is significant and report the slice that was.

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 Quantitative Analysis AI skill do?

Answers a business question with data without fooling yourself — framing the question so an answer would change something, choosing the right comparison, checking the data before trusting it, recognizing the traps that produce confident wrong answers (aggregation reversals, survivorship, regression to the mean, multiple comparisons), and reporting uncertainty honestly. Use this to run an analysis, review one before acting on it, or work out why two people looking at the same data reached opposite conclusions.

Why use Quantitative Analysis on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cbrock84/headcount/tree/main/plugins/data-analytics/skills/quantitative-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 Quantitative 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 Quantitative Analysis?

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

Is the Quantitative Analysis AI skill free?

Yes. It is published on GitHub by cbrock84 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 👇