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

Biostatistics

ASecurity

Statistical methods for biology and medicine — study design, hypothesis testing, regression, and survival analysis.

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

Works with

cliapi

Security Analysis

A100/100

Scanned 9/29/2026

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

Installs into .claude/skills of the current project.

Are you the author of Biostatistics?

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

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

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: biostatistics
description: Statistical methods for biology and medicine — study design, hypothesis testing, regression, and survival analysis.
category: scientific
---

## Overview

biostatistics is the application of statistical reasoning to biological and medical data. It covers
study design (how to collect data that can answer the question), inference (hypothesis tests and
confidence intervals that respect the data's structure), and modeling (regression, mixed models,
survival analysis) for messy, real-world biomedical datasets with missing values, confounding, and
small samples.

The emphasis is on correct application, not mathematical derivation: choosing the right test for the
data type, checking assumptions, handling multiplicity, and reporting effect sizes with uncertainty —
the things that separate a defensible analysis from a p-value lottery.

## When to use

- Designing a study: sample-size/power calculation, randomization scheme, primary vs secondary
  endpoints.
- Choosing a test: t-test vs Mann-Whitney, chi-square vs Fisher, ANOVA vs Kruskal-Wallis, paired
  vs unpaired designs.
- Modeling: linear/logistic regression, mixed-effects models for repeated measures or clustered
  data, Cox proportional hazards for time-to-event.
- Survival analysis: Kaplan-Meier curves, log-rank tests, competing risks.
- Diagnostic studies: sensitivity/specificity, ROC/AUC, predictive values, likelihood ratios.
- Meta-analysis: pooling effect sizes, heterogeneity (I²), fixed vs random effects.
- Reviewing a paper: checking whether the statistics support the conclusions.

## Core concepts

- **Power and sample size.** Power = probability of detecting a real effect. Calculate n from the
  minimum clinically/biologically meaningful effect, expected variance, alpha (usually 0.05), and
  target power (usually 0.80). Underpowered studies waste resources and produce false negatives;
  they also inflate the false-positive rate among "significant" findings.
- **Data types drive test choice.** Continuous normal → parametric (t-test, ANOVA, Pearson);
  continuous non-normal or ordinal → non-parametric (Mann-Whitney, Kruskal-Wallis, Spearman);
  categorical → chi-square/Fisher; counts → Poisson/negative binomial; time-to-event → survival
  methods. A test on the wrong data type is invalid regardless of the p-value.
- **Assumptions are checkable.** Normality (Q-Q plots, Shapiro-Wilk), equal variance (Levene),
  linearity, independence of observations. Document the checks; switch methods when they fail.
- **Confounding vs mediation vs effect modification.** Confounders distort the exposure-outcome
  association and must be adjusted for; mediators lie on the causal path and adjusting for them
  can erase the real effect; effect modifiers mean the effect differs by subgroup (test with
  interaction terms, not by fishing through subgroups).
- **Multiple testing.** Every extra test inflates the false-positive rate. Use Bonferroni/Holm
  for confirmatory families, FDR (Benjamini-Hochberg) for exploratory screening like omics, and
  prespecify primary endpoints so one cannot shop for significance.
- **Effect sizes with uncertainty.** A p-value says nothing about magnitude. Report mean differences,
  odds ratios, hazard ratios, or risk differences with 95% confidence intervals. A "significant"
  effect of trivial size is usually not actionable.
- **Missing data.** Classify as MCAR/MAR/MNAR. Complete-case analysis is only valid under MCAR.
  Prefer multiple imputation or likelihood-based methods under MAR; MNAR needs sensitivity analyses.
- **Survival analysis specifics.** Censoring must be non-informative; check proportional hazards
  (Schoenfeld residuals); Kaplan-Meier for description, Cox for adjustment; competing risks need
  Fine-Gray, not naive Kaplan-Meier.

## Practical workflow

1. **Define the question and estimand.** What population, what comparison, what outcome, what time
   horizon? Write the primary analysis plan before seeing the data.
2. **Power calculation.** Use the smallest meaningful effect size; add 10-20% for dropout. Record
   the assumptions — they will be audited.
3. **Data audit.** Distributions, missingness patterns, outliers, impossible values. Clean
   reproducibly (scripted, never by hand in a spreadsheet).
4. **Exploratory plots.** Histograms, boxplots by group, scatterplots, survival curves. Choose the
   model family from what you see, not from habit.
5. **Primary analysis.** Prespecified model, assumption checks, adjusted estimates with CIs.
6. **Sensitivity analyses.** Alternative missing-data handling, per-protocol vs intention-to-treat,
   subgroup checks with interaction tests.
7. **Report.** CONSORT/STROBE-style flow of participants, baseline table, primary result with
   effect size + CI, then secondary/exploratory clearly labeled.

Example (R sketch):
```r
power.t.test(delta = 5, sd = 10, power = 0.8)          # sample size
wilcox.test(outcome ~ group, data = d)                 # non-normal comparison
fit <- coxph(Surv(time, event) ~ treatment + age, data = d)
cox.zph(fit)                                            # proportional-hazards check
```

## Common pitfalls

- p-hacking: running many unplanned analyses until something is "significant."
- Treating ordinal scales (e.g. pain scores) as continuous without checking.
- Ignoring clustering (patients within hospitals, repeated measures) — standard errors collapse.
- Survivor bias / immortal-time bias in observational survival comparisons.
- Interpreting a non-significant result as "no effect" rather than "insufficient evidence."
- Overfitting: more predictors than events (rule of thumb: ≥10 events per variable in logistic/Cox).
- Reporting relative risk without absolute risk — a 50% relative reduction can be clinically trivial.

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 →