← LeaderboardThe Skill Leaderboard

power-analysis

Compute statistical power, required sample size, and minimum detectable effect (MDE) for a study design, then write a registry-ready power section. Handles two-arm RCTs (with clustering / ICC and unequal allocation), multiple-arm corrections, and a simulation-based power option for non-standard designs (DiD/event-study, IV, panel). Use when user says "power analysis", "power calculation", "MDE", "minimum detectable effect", "how big a sample do I need", "is my study powered", "power for an RCT", or when /preregister needs a power section for an experiment. Produces a power/MDE table, power cur

Published by pedrohcgs ↗pedrohcgs/claude-code-my-workflow

Try your first task

A source-grounded starter task has not been verified for this skill yet.

SKILL.md

name: power-analysisdescription: Compute statistical power, required sample size, and minimum detectable effect (MDE) for a study design, then write a registry-ready power section. Handles two-arm RCTs (with clustering / ICC and unequal allocation), multiple-arm corrections, and a simulation-based power option for non-standard designs (DiD/event-study, IV, panel). Use when user says "power analysis", "power calculation", "MDE", "minimum detectable effect", "how big a sample do I need", "is my study powered", "power for an RCT", or when /preregister needs a power section for an experiment. Produces a power/MDE table, power curves, and a methods paragraph to paste into a preregistration.

power-analysis

This skill's instructions live in .claude/skills/power-analysis/SKILL.md. Read that file now and follow it, with the files it points to. Read AGENTS.md first if you have not already.

It was written for Claude Code. Running it from Codex, Antigravity or another agent:

Arguments. Where it says $ARGUMENTS, use what the user asked for.
Claude Code agents. Where a step hands work to an agent in .claude/agents/ (through the Agent or Task tool), do that step where it appears in the procedure: never later, and never skip it. A step that gates what follows still gates it (/commit runs its verifier before it commits). Read the agent's file for what the step checks.
Fresh context. If the step needs a context that has not seen your work, for example a claim verifier that must never see the draft, run it in a separate session or worker that has not seen the draft, if your tool can start one, and give it only what the step says to pass. If it cannot, do the step yourself, mark every result it produced not independently verified, and tell the user to repeat that check in Claude Code (/verify-claims for citations) before relying on it.
Claude Code settings. allowed-tools, model, effort, argument-hint and disable-model-invocation in the source's frontmatter configure Claude Code. Ignore them.
Guards. Claude Code's guard hooks do not run for you. Follow the rules in AGENTS.md yourself; the git pre-commit gate and CI still apply to your commits.