statistical-reporting
Statistical test selection, assumption checking, and APA-formatted reporting. Use when analyzing experimental results or writing results sections.
pinned to #ea77ec1updated 2 weeks ago
Ask your AI client: “install skills/statistical-reporting”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/statistical-reportingmetahub onboarded this repo on the author's behalf.
If you own github.com/aiming-lab/AutoResearchClaw on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
13,760
Last commit
2 weeks ago
Latest release
published
- #autonomous-research
- #citation-verification
- #llm-agents
- #metaclaw
- #multi-agent-debate
- #openclaw
- #paper-generation
- #scientific-discovery
- #self-evolving
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.ea77ec1· 2 weeks ago
Kind-specific
31Skill: SKILL.md present
found at .claude/skills/statistical-reporting/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
380 words · 2,533 chars · 6 sections
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrentea77ec1warn2 weeks ago
Contents
Statistical Reporting Best Practice
Test Selection Quick Reference
- Comparing two groups (independent, normal): Independent t-test
- Comparing two groups (independent, non-normal): Mann-Whitney U test
- Comparing two groups (paired, normal): Paired t-test
- Comparing two groups (paired, non-normal): Wilcoxon signed-rank test
- Comparing 3+ groups (independent, normal): One-way ANOVA + post-hoc
- Comparing 3+ groups (non-normal): Kruskal-Wallis test
- Relationship between continuous variables: Pearson or Spearman correlation
- Categorical outcomes: Chi-square or Fisher's exact test
- Predicting continuous outcome: Linear regression
- Predicting binary outcome: Logistic regression
Assumption Checking
- Normality: Shapiro-Wilk test (n < 50) or visual Q-Q plots
- Homogeneity of variance: Levene's test before t-tests and ANOVA
- Independence: Verify study design ensures independent observations
- Linearity: Scatter plots and residual plots for regression
- Multicollinearity: VIF < 5 for multiple regression predictors
- When assumptions are violated, use non-parametric alternatives or robust methods
APA Reporting Format
- t-test: t(df) = X.XX, p = .XXX, d = X.XX
- ANOVA: F(df_between, df_within) = X.XX, p = .XXX, eta-squared = .XX
- Correlation: r(df) = .XX, p = .XXX [95% CI: .XX, .XX]
- Chi-square: chi-square(df, N = XXX) = X.XX, p = .XXX
- Regression: beta = X.XX, SE = X.XX, t = X.XX, p = .XXX
- Always report exact p-values (not "p < .05") unless p < .001
- Use leading zero for values that can exceed 1 (e.g., t = 0.50) but not for those bounded by 1 (e.g., p = .032, r = .45)
Effect Sizes
- ALWAYS report effect sizes alongside p-values
- Cohen's d for group comparisons: small = 0.2, medium = 0.5, large = 0.8
- Eta-squared for ANOVA: small = .01, medium = .06, large = .14
- R-squared for regression: report adjusted R-squared for multiple predictors
- Odds ratios for logistic regression with 95% confidence intervals
- Distinguish statistical significance from practical significance
Common Mistakes to Avoid
- Never say "the results were not significant, therefore there is no effect"
- Do not confuse correlation with causation in observational data
- Apply multiple comparison corrections (Bonferroni, FDR) when running many tests
- Report confidence intervals, not just point estimates
- State whether tests are one-tailed or two-tailed and justify the choice
Reviews
No reviews yet. Be the first.
Related
Planning With Files
Claude Code skill implementing Manus-style persistent markdown planning — the workflow pattern behind the $2B acquisition.
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
mh install skills/statistical-reporting