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

Power And Sample Size

ASecurity

Compute or advise the sample size an experiment needs BEFORE it launches — from α (0.05), power (0.80), and a minimum detectable effect (MDE) — or compute the power/MDE a fixed sample can achieve. Prevents the underpowered-study pitfall and is the prerequisite to any A/B test. Returns the n, the assumptions behind it, and a runnable snippet. Used by `applied-statistician` (primary).

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agentspythonrustrailstesting

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill power-and-sample-size --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Power And Sample Size?

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

Security grade badge for Power And Sample Size
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-power-and-sample-size/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-power-and-sample-size)

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: power-and-sample-size
description: Compute or advise the sample size an experiment needs BEFORE it launches — from α (0.05), power (0.80), and a minimum detectable effect (MDE) — or compute the power/MDE a fixed sample can achieve. Prevents the underpowered-study pitfall and is the prerequisite to any A/B test. Returns the n, the assumptions behind it, and a runnable snippet. Used by `applied-statistician` (primary).
---

# Skill: power-and-sample-size

> **Invoked by:** `applied-statistician` (primary). Prerequisite for [`../experiment-analysis/SKILL.md`](../experiment-analysis/SKILL.md) — no experiment ships without it.
>
> **When to invoke:** "how big a sample do I need?"; "is this test big enough to trust a null result?"; planning any A/B test or comparison.
>
> **Output:** required n per group (or achievable power/MDE), the four inputs that produced it, and a runnable snippet.

## The four interlocking quantities

Fix any three; the fourth is determined:

| Quantity | Meaning | Conventional default |
|---|---|---|
| **α** (significance) | tolerated false-positive rate | **0.05** |
| **power** (1 − β) | probability of detecting a true effect of the target size | **0.80** (Cohen 1988) |
| **effect size / MDE** | the smallest effect worth detecting | business-meaningful; else Cohen d = 0.2/0.5/0.8 |
| **n** | sample size (per group) | the output you usually solve for |

## Procedure

1. **Pin the MDE first** — the smallest effect that would change the decision. Prefer a business-meaningful number (e.g., "a 1.5-point conversion lift pays for the change"); fall back to Cohen's conventions only when no pilot/benchmark exists.
2. **Pick α and power** (defaults 0.05 / 0.80 unless the cost of a false positive/negative argues otherwise).
3. **Match the calculation to the planned test** (two-proportion for conversion rates, two-sample t for a continuous mean, etc.).
4. **Solve for n** and report it **per group**, plus the total and the expected experiment duration given traffic.
5. **If the sample is fixed** (you can't get more), invert it: report the **power** and the **MDE** that n can actually detect — and warn loudly if power < 0.80 (the result will be hard to interpret either way → underpowered-study pitfall #8).

## Snippets (Tier-1 tooling)

```python
# continuous outcome: n per group for a medium effect (d=0.5), two-sided, 80% power
from statsmodels.stats.power import TTestIndPower
n = TTestIndPower().solve_power(effect_size=0.5, alpha=0.05, power=0.80, alternative="two-sided")
print(f"n per group ≈ {n:.0f}")
```

```python
# conversion rates: n per group to detect baseline 5% → 6.5% (a 1.5pp MDE)
from statsmodels.stats.proportion import proportion_effectsize
from statsmodels.stats.power import NormalIndPower
es = proportion_effectsize(0.065, 0.05)
n = NormalIndPower().solve_power(effect_size=es, alpha=0.05, power=0.80, alternative="two-sided")
print(f"n per group ≈ {n:.0f}")
```

## Guardrails
- **Compute n before launch, not after.** Post-hoc "observed power" on a finished study is misleading — don't do it.
- A null result from an **underpowered** study is *not* evidence of no effect — report the CI and the MDE the study could detect ("we could only have detected effects ≥ X").
- The randomization unit must match the unit of independence (user, not session) — see [`../../knowledge/experiment-design-and-ab-testing.md`](../../knowledge/experiment-design-and-ab-testing.md).

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
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', ...

698431 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 →