Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
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

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Cc Statistics

ASecurity

Use when defining n, choosing statistical tests, correcting for multiple comparisons, and reporting error bars for a Cancer Cell (Cell Press) manuscript. Focuses on biological statistics and avoiding pseudo-replication; it does not design experiments or build figures.

1,052 stars
0 votes
0 copies
1 views
Added 6/4/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill cc-statistics --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cc Statistics?

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

Security grade badge for Cc Statistics
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-cc-statistics/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-cc-statistics)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: cc-statistics
description: Use when defining n, choosing statistical tests, correcting for multiple comparisons, and reporting error bars for a Cancer Cell (Cell Press) manuscript. Focuses on biological statistics and avoiding pseudo-replication; it does not design experiments or build figures.
---

# Biological Statistics (cc-statistics)

## When to trigger

- `n` is ambiguous, or you suspect pseudo-replication
- Unsure which test fits the data and design
- Many comparisons without multiplicity correction
- Error bars / variability are unlabeled in figures or legends

## Defining `n` (the core issue)

- `n` = number of **independent biological replicates** (separate mice, independent cultures/passages, distinct patients).
- Technical replicates (duplicate wells, repeat reads) describe measurement precision and **do not** count toward `n`.
- State `n` for **every** panel in the legend, with what one unit is ("n = 5 mice per group", "n = 3 independent experiments").
- Pooling cells from many wells of one experiment and calling it n=many is **pseudo-replication** — a classic Cancer Cell reviewer catch.

## Choosing the test

| Design | Typical test |
|--------|--------------|
| Two groups, continuous, ~normal | Unpaired t-test (Welch if unequal variance) |
| Two paired conditions | Paired t-test |
| Two groups, non-normal / small n | Mann-Whitney U |
| >2 groups, one factor | One-way ANOVA + post-hoc (Tukey/Dunnett) |
| Two factors (e.g., genotype × treatment) | Two-way ANOVA + correction |
| Tumor growth over time | Mixed-effects / repeated-measures ANOVA (not many t-tests per timepoint) |
| Survival / time-to-event | Kaplan-Meier + log-rank; Cox for covariates |
| Categorical / proportions | Fisher's exact / chi-square |
| Correlation | Pearson (normal) / Spearman (ranked) |
| High-dimensional omics | Model-based (DESeq2/edgeR/limma) with FDR |

Check assumptions (normality, equal variance) and report how. Prefer non-parametric or Welch corrections for small/uneven bench-scale data.

## Multiple comparisons

- Few planned comparisons → Tukey / Dunnett / Holm / Bonferroni.
- Genome-wide / omics → control the **false discovery rate** (Benjamini-Hochberg); report adjusted p / q-values.
- Do not run many pairwise t-tests across groups or timepoints without correction.

## Error bars and reporting

- Define **what every error bar is**: SD, SEM, or 95% CI — in the legend.
- Show data points (dot plots / superplots) rather than bar-only charts when `n` is small.
- Report exact p-values (not just asterisks) where feasible, plus the test and `n`.
- Distinguish biological-replicate variability from technical noise in plots.
- For survival, give hazard ratios with CIs, not p-value alone.

## Checklist

- [ ] `n` defined per panel as biological replicates; one unit specified
- [ ] No pseudo-replication (technical reps not counted as `n`)
- [ ] Test choice matches design; assumptions checked
- [ ] Repeated/longitudinal data analyzed with appropriate model, not serial t-tests
- [ ] Multiple comparisons corrected; FDR for omics
- [ ] Error bars defined (SD/SEM/CI) in every legend
- [ ] Exact p-values, test name, and `n` reported
- [ ] Data points shown for small-n comparisons
- [ ] Statistical software + versions stated (in STAR Methods)

## Anti-patterns

- "n=3" meaning three technical wells of one experiment
- SEM used to make tiny error bars without saying so
- Bar charts hiding 2–3 underlying points
- Multiple t-tests across timepoints/groups, uncorrected
- Asterisks with no test, no `n`, no exact p
- Treating omics features as independent without FDR control

## Output format

```
【n definition】biological unit = ...; per-panel n stated? Y/N
【Pseudo-replication risk】none / fix: [...]
【Tests】per analysis: ...
【Multiplicity】correction used: ...
【Error bars】SD/SEM/CI defined in legends? Y/N
【Reporting gaps】exact p / data points / software version
【Next step】cc-figures-tables
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 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', ...

693161 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.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, 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.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →