stats-checklisted

# Stats Check ## Core Rule Every statistical claim must report **effect size + uncertainty (a CI), N, the named test, and whether its assumptions hold**. "Significant" means *statistically* significant — never "large" or "important". **Association is not causation**: correlational/observational designs license "associated with / predicts", never "causes / drives / improves". And no p-hacking / HARKing / selective reporting — the analysis you report is the analysis you pre-specified, with exploratory results labeled exploratory. A bare p-value, a missing N, a causal verb on an ablation, or a number that disagrees between the abstract and Table 2 are the failures this skill exists to catch. This is the deterministic, numbers-and-design half of verification, operationalizing `agent_docs/statistics.md`. It **flags and proposes fixes — it does not change a reported quantity** (a Protected Claim per `CLAUDE.md`); recomputing a number to reconcile text and table is fine, *altering what was measured or which test was run* is not. ## When to Use Invoke with `/stats-check` when: - A Results section with statistics is "done" and you want it Reviewer-2-proof. - A revision added or changed a number, test, or comparison. - Before submission, on Results + the abstract + every table — the consistency check needs all three open at once. - The prompt-router flagged the task `[Statistics]` or `[Causation]`. Scope it: `/stats-check sections/results.tex`. Run the whole Results section *w