Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Statistical Modeling

ASecurity

Build statistical models properly — choosing models, checking assumptions, quantifying uncertainty, and avoiding common inferential traps. Use when moving beyond descriptives to inference or prediction with statistics.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgogitperformance

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill statistical-modeling --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Statistical Modeling?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Statistical Modeling
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-statistical-modeling/badge)](https://www.skillsdirectory.com/skills/aicodedecode-statistical-modeling)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: statistical-modeling
description: Build statistical models properly — choosing models, checking assumptions, quantifying uncertainty, and avoiding common inferential traps. Use when moving beyond descriptives to inference or prediction with statistics.
category: ai-research
---

# Statistical Modeling

Statistical models turn data into quantified claims: effects with uncertainty, predictions with 
intervals. The craft is choosing the right model, checking that its assumptions hold, and reporting 
honestly — including what the model can't tell you.

## Overview

Model selection follows the question and the data: continuous outcomes → regression family; 
counts → Poisson/negative binomial; binary → logistic; hierarchical structure → mixed models; 
time dependence → time series. Every model makes assumptions — check them with diagnostics, not 
faith. Report estimates with uncertainty (intervals, not just points), and distinguish what the 
data shows from what you wish it showed.

## When to use

- Estimating effects: "how much does X change Y, and how sure are we?"
- Predicting outcomes with quantified uncertainty.
- Accounting for structure: repeated measures, groups, time, space.
- Reviewing analyses: checking whether the model fits the question.

## Core concepts

- **Model-data match**: the model must respect the outcome type and data structure. Linear 
regression on counts or ignoring clustering produces confident nonsense.
- **Assumptions and diagnostics**: linearity, independence, homoscedasticity, distributional shape 
— checked with residual plots and tests, not assumed. Violations get fixed (transform, different 
model) not ignored.
- **Uncertainty quantification**: confidence/credible intervals, standard errors, prediction 
intervals. A point estimate without uncertainty is half a result.
- **Regularization**: shrinkage (ridge/lasso) and priors tame overfitting when predictors are many 
or collinear. Complexity needs justification.
- **Model comparison**: AIC/BIC, cross-validation, posterior predictive checks — principled ways 
to choose among models. Fit alone never justifies complexity.
- **Causation boundaries**: most models describe association. Causal claims need design 
(experiments, quasi-experiments) or explicit causal assumptions — the model alone doesn't provide 
them.

## Practical workflow

1. State the question, outcome type, and data structure; choose the model family that matches.
2. Explore the data first: distributions, relationships, missingness, outliers — the model should 
fit the data you have.
3. Fit simply first; check diagnostics (residuals, influence, convergence). Fix violations before 
adding complexity.
4. Quantify uncertainty: intervals for key estimates; prediction intervals if predicting.
5. Compare candidate models with cross-validation or information criteria; prefer the simpler model 
when performance ties.
6. Report: estimates with intervals, assumption checks, sensitivity analyses, and plain-language 
limits on interpretation.

```text
Modeling checklist:
[ ] Model family matches outcome type + data structure
[ ] Assumptions checked with diagnostics (not assumed)
[ ] Uncertainty reported (intervals, not just points)
[ ] Compared against simpler alternatives
[ ] Sensitivity to key choices tested
[ ] Causal language only where design supports it
```

## Common pitfalls

- **p-value theater**: reporting significance without effect sizes or intervals. "Significant" tiny 
effects mislead.
- **Ignoring structure**: treating clustered/longitudinal data as independent. Standard errors 
collapse; false precision follows.
- **Overfitting**: complex models fitting noise. Regularize, validate, prefer simplicity.
- **Assumption blindness**: never looking at residuals. The diagnostics are where model failures 
announce themselves.
- **Causal language from observational fits**: "X increases Y" from a regression without causal 
design. Say "associated."
- **Researcher degrees of freedom**: trying models until one "works." Pre-specify the primary 
model; report the garden of forking paths.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →