hypothesis-testing
/hypothesis-testing
Take a user-stated hypothesis and test it against the data, producing a report stating whether the data supports, refutes, or is inconclusive about the claim. Use when the user has a specific question or claim they want to interrogate against a dataset.
- Author
- danielrosehill ↗
- Repository
- claude-data-analyst-plugin ↗
- Licence
- MIT
- Last repository change
- 15.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 15.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Take a user-stated hypothesis and test it against the data, producing a report stating whether the data supports, refutes, or is inconclusive about the claim. Use when the user has a specific question or claim they want to interrogate against a dataset.
Original author description
Take a user-stated hypothesis and test it against the data, producing a report stating whether the data supports, refutes, or is inconclusive about the claim. Use when the user has a specific question or claim they want to interrogate against a dataset.
How it works
- Inputs
- Step 1 — Formalise the hypothesis
- Step 2 — Select a test
- Step 3 — Execute
- Step 4 — Verdict
- Output
SKILL.md preview
--- name: hypothesis-testing description: Take a user-stated hypothesis and test it against the data, producing a report stating whether the data supports, refutes, or is inconclusive about the claim. Use when the user has a specific question or claim they want to interrogate against a dataset. --- # Hypothesis Testing Rigorous first-pass evaluation of a user hypothesis against a dataset. ## Inputs - Path to a dataset file or folder. - The **hypothesis**, stated in natural language (e.g. "customers in segment A spend more than those in segment B", "there's no difference in conversion by landing page"). - Optional: desired significance level α (default 0.05). ## Step 1 — Formalise the hypothesis Before testing, restate the user's claim as: - **H₀ (null)**: typically "no effect" / "no difference" / "no relationship". - **H₁ (alternative)**: the user's claim, one- or two-sided as appropriate. - **Variables involved**: identify which columns map to the hypothesis, with their dtypes. - **Test type** selected based on the data shape (see decision table below). Show this formalisation to the user and proceed unless they object. ## Step 2 — Select a test | User hypothesis shape | Variables | Default test | |---|---|---| | Group A mean ≠ Group B mean | 1 numeric + 1 binary categorical | Welch's t-test (unequal var) or Mann-Whitney if non-normal | | Difference across 3+ groups | 1 numeric + 1 categorical | One-way ANOVA or Kruskal-Wallis | | Association between two categoricals | 2 categoricals | Chi-square (or Fisher's exact if small cells) | | Correlation ≠ 0 | 2 numerics | Pearson (linear) or Spearman (monotonic) | | Proportion differs from value | 1 binary | One-sample proportion z-test | | Paired before/after | 1 numeric, paired | Paired t-test or Wilcoxon signed-rank | | Time trend | 1 numeric + time | Mann-Kendall or regression slope test | Check assumptions (normality via Shapiro-Wilk for small n or visual for large n; equal variance via Levene's) and fall back to the non-parametric counterpart when they fail. ## Step 3 — Execute Recommended: `uv run --with pandas --with scipy --with statsmodels python -c '...'`. Report: - Sample size(s) - Effect size (Cohen's d, r, Cramér's V, odds ratio — whichever fits) - Test statistic and p-value - 95% confidence interval for the effect ## Step 4 — Verdict Classify as one of: - **Supports** — p < α **and** effect size is non-trivial **and** sample size is adequate. - **Refutes** — p < α but in the opposite direction, or a tight CI around zero effect. - **Inconclusive** — p ≥ α, or underpowered (effect plausible but sample too small), or assumptions violated beyond repair. Do **not** equate "p > 0.05" with "no effect" — distinguish "evidence of no effect" (tight CI around zero) from "no evidence of effect" (wide CI). ## Output Write `<dataset>-hypothesis-<slug>.md`: 1. The hypothesis as stated by the user, verbatim. 2. Formalised H₀ / H₁. 3. Test chosen and why (including assumption checks). 4. Results table. 5. **Verdict** in bold: supports / refutes / inconclusive, with a plain-English explanation. 6. Caveats (confounders, selection effects, multiple-comparisons risk if this is one of many tests).
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · danielrosehill/claude-data-analyst-plugin | 100 | MIT |
| testland/qa-skills | 100 | MIT |
| poemswe/co-researcher | 100 | MIT |
| testland/qa | 100 | MIT |
| rohitg00/skillkit | 100 | Apache-2.0 |
| foryourhealth111-pixel/Vibe-Skills | 95 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version d746349afab7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90hypothesis-test
Run a hypothesis test with assumption checks, test selection, and plain-language interpretation. Use when comparing groups or testing a specific statistical claim. - 93hypogenic
Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing.… - 90product-ab-testing
Use this skill when designing and analyzing A/B tests: hypothesis formation, experiment design, statistical analysis, and decision framework. This skill enforces: hypothesis structure, sample size calculation, statistical significance, AA test validation. Do NOT use for:… - 100expectation-driven-science
Development guided by the scientific method and explicit expectations. Use when the user wants to build or validate an analysis/model test-first, states a "hypothesis", "expectation" or "assumption" about the data, or asks for a principled data-science workflow (hypothesis →… - 87hypothesys
Grill the user relentlessly about a data science or ML hypothesis until it is clear, falsifiable and tied to goal metrics: premises, baseline and success criteria. Use when starting an experiment, when the user wants to stress-test a hypothesis or idea, or says 'grill me',… - 96om-problem-solving
Hypothesis-driven, structured problem solving as top strategy firms practise it: problem statement, MECE issue and hypothesis trees, prioritization, workplan, analyses that prove or kill each hypothesis, synthesis and the so-what. Use at the start of any strategy, growth,…