statistical-analysis
Skill1 starsChanged 7 months agoMITView on GitHub
Apply statistical methods including descriptive stats, trend analysis, outlier detection, and hypothesis testing. Use when analyzing distributions, testing for significance, detecting anomalies, computing correlations, or interpreting statistical results. Trigger phrases: "is this statistically significant", "run a hypothesis test", "detect outliers", "what's the correlation", "trend analysis", "confidence interval", "p-value", "regression analysis", "A/B test results", "statistical summary", "distribution analysis"
46 other projects use a version of this.
Adopted by
Most recently taken up by
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- AxlZero21/Skillstheir own version, first seen Nov 8, 2026
- TerryFYL/ai-research-armytheir own version, first seen Nov 8, 2026
- SWEStash/swe-workflow-skillstheir own version, first seen Nov 8, 2026
- DaeSeokSong/oh-my-ouroborostheir own version, first seen Nov 1, 2026
- MarieLynneBlock/arcanum-artifextheir own version, first seen Nov 1, 2026
Used with
Projects with it also use evidence-driven-writing, experiment-results-planning and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Norman-burySkillevidence-driven-writing
Use when writing or revising Introduction, Related Work, background, literature synthesis, or any section where references must drive claims
Also in 3 projects that use this
Norman-burySkillexperiment-results-planning
Use when designing experiments, result tables, mock planning data, evaluation protocols, or results sections before real data are final
Also in 3 projects that use this
- +10 more from Norman-bury
Other versions46 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 46
- anthropics/knowledge-work-plugins★ 35ksame name
- Norman-bury/research-writing-skill★ 3.4ksame name
- Norman-bury/articlewriting-skill★ 3.4ksame name
- wu-yc/LabClaw★ 1.1ksame name
- LeonChaoX/qinyan-academic-skills★ 910same name
- jaechang-hits/SciAgent-Skills★ 386same name
- qinyan-ai/qinyan-academic-skills★ 80same name
- Barrios88/barrios-skills★ 63same name
- Chanw-research/claude-code-paper-writing★ 42same name
- TashanGKD/tashan-research-skills★ 19same name
36 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- incident-responseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 39 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Before applying any method, verify its assumptions:
- Distinctive: line 212
Always provide interpretation in business terms:
- Distinctive: line 233
Every statistical analysis should include:
- Distinctive: line 246
Correct for multiple comparisons: If running many tests, apply Bonferroni or FDR correction.
- Distinctive: line 250
Report sample sizes: Always include N for each group.
“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Statistical Analysis Skill
Apply rigorous statistical methods to data questions. Cover descriptive statistics, hypothesis testing, correlation, regression, outlier detection, and trend analysis with proper interpretation.
Workflow
Step 1: Identify the Statistical Question
Map the business question to a statistical framework:
| Business Question | Statistical Method |
| "What does the data look like?" | Descriptive statistics, distribution analysis |
| "Is this change real or noise?" | Hypothesis testing (t-test, chi-square) |
| "Are these two things related?" | Correlation, regression |
| "Is this data point unusual?" | Outlier detection (IQR, z-score, Grubbs) |
| "What's the trend?" | Time series decomposition, regression |
| "Did our experiment work?" | A/B test analysis (proportions or means) |
| "Can we predict this?" | Regression, forecasting |
| "Are these groups different?" | ANOVA, Mann-Whitney, Kruskal-Wallis |
Step 2: Check Assumptions
Before applying any method, verify its assumptions:
import scipy.stats as stats
import numpy as np
# Normality check
stat, p = stats.shapiro(data)
print(f"Shapiro-Wilk: W={stat:.4f}, p={p:.4f}")
print(f"Normal: {'Yes' if p > 0.05 else 'No -- use non-parametric methods'}")
# Variance equality (for t-tests, ANOVA)
stat, p = stats.levene(group_a, group_b)
print(f"Levene's test: F={stat:.4f}, p={p:.4f}")
print(f"Equal variance: {'Yes' if p > 0.05 else 'No -- use Welch t-test'}")
# Sample size check
print(f"Sample sizes: n1={len(group_a)}, n2={len(group_b)}")
print(f"Sufficient for parametric test: {'Yes' if min(len(group_a), len(group_b)) >= 30 else 'Consider non-parametric'}")Step 3: Apply the Method
Descriptive Statistics
def describe_distribution(series, name="Variable"):
"""Comprehensive descriptive statistics."""
print(f"\n=== {name} ===")
print(f"N: {len(series):,}")
print(f"Mean: {series.mean():.4f}")
print(f"Median: {series.median():.4f}")
print(f"Std Dev: {series.std():.4f}")
print(f"Skewness: {series.skew():.4f}")
print(f"Kurtosis: {series.kurtosis():.4f}")
print(f"IQR: {series.quantile(0.75) - series.quantile(0.25):.4f}")
print(f"\nPercentiles:")
for p in [1, 5, 10, 25, 50, 75, 90, 95, 99]:
print(f" P{p:2d}: {series.quantile(p/100):.4f}")Hypothesis Testing: Two-Sample Comparison
def compare_groups(group_a, group_b, alpha=0.05):
"""Compare two groups with appropriate test selection."""
# Check normality
_, p_norm_a = stats.shapiro(group_a[:5000]) # Shapiro limited to 5000
_, p_norm_b = stats.shapiro(group_b[:5000])
normal = p_norm_a > 0.05 and p_norm_b > 0.05
if normal and len(group_a) >= 30 and len(group_b) >= 30:
# Parametric: Welch's t-test (does not assume equal variance)
stat, p = stats.ttest_ind(group_a, group_b, equal_var=False)
test_name = "Welch's t-test"
else:
# Non-parametric: Mann-Whitney U
stat, p = stats.mannwhitneyu(group_a, group_b, alternative='two-sided')
test_name = "Mann-Whitney U"
# Effect size (Cohen's d)
pooled_std = np.sqrt((group_a.std()**2 + group_b.std()**2) / 2)
cohens_d = (group_a.mean() - group_b.mean()) / pooled_std
print(f"Test: {test_name}")
print(f"Statistic: {stat:.4f}")
print(f"p-value: {p:.6f}")
print(f"Significant at alpha={alpha}: {'Yes' if p < alpha else 'No'}")
print(f"Cohen's d: {cohens_d:.4f} ({'small' if abs(cohens_d) < 0.5 else 'medium' if abs(cohens_d) < 0.8 else 'large'})")
print(f"Mean A: {group_a.mean():.4f}, Mean B: {group_b.mean():.4f}")
print(f"Difference: {group_a.mean() - group_b.mean():.4f} ({(group_a.mean() - group_b.mean()) / group_b.mean():.2%})")A/B Test Analysis (Proportions)
def ab_test_proportions(conversions_a, total_a, conversions_b, total_b, alpha=0.05):
"""Analyze an A/B test with conversion rate as the metric."""
rate_a = conversions_a / total_a
rate_b = conversions_b / total_b
# Z-test for proportions
pooled_p = (conversions_a + conversions_b) / (total_a + total_b)
se = np.sqrt(pooled_p * (1 - pooled_p) * (1/total_a + 1/total_b))
z = (rate_b - rate_a) / se
p_value = 2 * (1 - stats.norm.cdf(abs(z)))
# Confidence interval for the difference
se_diff = np.sqrt(rate_a*(1-rate_a)/total_a + rate_b*(1-rate_b)/total_b)
ci_lower = (rate_b - rate_a) - 1.96 * se_diff
ci_upper = (rate_b - rate_a) + 1.96 * se_diff
print(f"Control: {rate_a:.4%} ({conversions_a}/{total_a})")
print(f"Treatment: {rate_b:.4%} ({conversions_b}/{total_b})")
print(f"Lift: {(rate_b - rate_a) / rate_a:.2%}")
print(f"95% CI for difference: [{ci_lower:.4%}, {ci_upper:.4%}]")
print(f"p-value: {p_value:.6f}")
print(f"Significant: {'Yes' if p_value < alpha else 'No'}")Outlier Detection
def detect_outliers(series, method='iqr'):
"""Detect outliers using IQR or Z-score method."""
if method == 'iqr':
q1 = series.quantile(0.25)
q3 = series.quantile(0.75)
iqr = q3 - q1
lower = q1 - 1.5 * iqr
upper = q3 + 1.5 * iqr
outliers = series[(series < lower) | (series > upper)]
elif method == 'zscore':
z_scores = np.abs(stats.zscore(series.dropna()))
outliers = series[z_scores > 3]
print(f"Method: {method.upper()}")
print(f"Outliers found: {len(outliers)} ({len(outliers)/len(series):.2%})")
if len(outliers) > 0:
print(f"Range: {outliers.min():.4f} to {outliers.max():.4f}")
return outliersCorrelation Analysis
def correlation_analysis(df, method='pearson'):
"""Compute and interpret correlations."""
corr_matrix = df.corr(method=method)
# Find strong correlations
pairs = []
for i in range(len(corr_matrix.columns)):
for j in range(i+1, len(corr_matrix.columns)):
r = corr_matrix.iloc[i, j]
col_a, col_b = corr_matrix.columns[i], corr_matrix.columns[j]
# Statistical significance
n = df[[col_a, col_b]].dropna().shape[0]
t_stat = r * np.sqrt((n - 2) / (1 - r**2))
p_val = 2 * (1 - stats.t.cdf(abs(t_stat), n - 2))
pairs.append((col_a, col_b, r, p_val))
pairs.sort(key=lambda x: abs(x[2]), reverse=True)
print("Correlations (sorted by strength):")
for col_a, col_b, r, p in pairs[:15]:
sig = "*" if p < 0.05 else ""
print(f" {col_a} <-> {col_b}: r={r:.3f}{sig} (p={p:.4f})")Trend Analysis
from sklearn.linear_model import LinearRegression
def trend_analysis(dates, values):
"""Fit a linear trend and test significance."""
x = np.arange(len(dates)).reshape(-1, 1)
y = np.array(values)
model = LinearRegression().fit(x, y)
slope = model.coef_[0]
r_squared = model.score(x, y)
# Significance of the slope
n = len(values)
se = np.sqrt(np.sum((y - model.predict(x))**2) / (n - 2) / np.sum((x - x.mean())**2))
t_stat = slope / se
p_value = 2 * (1 - stats.t.cdf(abs(t_stat), n - 2))
print(f"Trend slope: {slope:.4f} per period")
print(f"R-squared: {r_squared:.4f}")
print(f"p-value: {p_value:.6f}")
print(f"Significant trend: {'Yes' if p_value < 0.05 else 'No'}")Step 4: Interpret Results
Always provide interpretation in business terms:
## Statistical Summary
**Test**: [Name of test applied]
**Result**: [Statistically significant / not significant] at alpha = 0.05
**What this means**: [Plain language interpretation]
- The observed difference of [X%] is [likely real / could be due to chance].
- We are [95%] confident the true difference is between [CI lower] and [CI upper].
- The effect size is [small/medium/large], meaning [practical significance].
**Caveats**:
- [Assumption violations, if any]
- [Sample size limitations]
- [Multiple comparison concerns]Output Format
Every statistical analysis should include:
- The question being answered
- The method chosen and why
- Assumption checks and results
- The test results with exact numbers (test statistic, p-value, CI, effect size)
- Plain-language interpretation of what the numbers mean
- Caveats and limitations
Best Practices
- Report effect sizes, not just p-values. A statistically significant result may not be practically meaningful.
- Use confidence intervals. They convey more information than binary significant/not-significant.
- Check assumptions first. Using a parametric test on non-normal data can give misleading results.
- Correct for multiple comparisons. If running many tests, apply Bonferroni or FDR correction.
- State the alpha level upfront. Decide on 0.05, 0.01, or 0.10 before seeing the data.
- Beware of large-sample significance. With millions of rows, even trivial differences become statistically significant. Focus on practical significance.
- Never confuse correlation with causation. State explicitly that observational data shows association, not causation.
- Report sample sizes. Always include N for each group. Small samples require different methods.
- Use non-parametric methods when in doubt. They make fewer assumptions and are more robust.
- Visualize alongside statistics. A histogram or box plot often reveals more than a p-value.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

