size-and-justify-samples

Determines research sample sizes and blocks claims that exceed what the n supports.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill size-and-justify-samples-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: size-and-justify-samples
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/size-and-justify-samples
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill size-and-justify-samples-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Researchers routinely guess at participant counts or dress up tiny qualitative samples as percentages ("60% of users" from 6 people), producing deliverables that collapse under the first "out of how many?" question. This Skill is the canonical reference for how many participants a study needs and whether a given n can carry the claim being made. ## Core Features & Use Cases - Pick-your-number table: Fast defaults per situation — 5–6 for generative discovery, 5 per round for formative usability, ~40 for quant metrics, ~385 for a ±5% survey rate — each with its stop-rule. - Saturation and precision logic: Per-segment saturation stop-rules for qualitative work, and margin-of-error formulas (Adjusted-Wald intervals, effect-size sizing) for quantitative studies. - The hard gate: A four-step check that refuses percentages on qual n, demands confidence intervals on every rate, and offers small-n defenses (counts + severity, or triangulation to analytics) when stakeholders demand numbers. - Use Case: Before reporting "4 of 6 beta testers failed to find reschedule" as "60% of users," run the gate — it rewrites the claim as a count with High severity and routes the rate request to product analytics that actually have the n. ## Quick Start Ask the AI to justify the sample size for your planned usability study and check whether your drafted finding's percentage is defensible at your current n.

Frequently Asked Questions about size-and-justify-samples

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How many participants do I need for a usability study?

For formative usability testing to find problems, use 5 users per round per persona and iterate across rounds. For quantitative metrics like success rates or SUS scores, plan for roughly 40 participants to get about ±15% margin at 95% confidence.

How many interviews are enough for qualitative research?

Qualitative studies are sized by saturation, not a fixed number. Expect about 5–6 for a narrow homogeneous segment and 8–12 for a broader one, stopping when two consecutive sessions surface no new themes, tracked per segment.

Can I report a percentage from a small qualitative sample?

No. Below roughly 30 participants, report counts (X of Y) plus severity instead of percentages, because a rate like 4 of 6 carries a confidence interval spanning roughly 30%–90%. If a decision needs a real rate, triangulate with analytics or a larger survey.

What sample size do I need for a survey with 5% margin of error?

About 385 respondents gives ±5% at 95% confidence for a large population at worst-case p=0.5, computed as n ≈ 0.96/m². A ±10% margin needs only about 100 respondents.

When is the 5-user rule not enough?

Five users works for finding problems in one persona but not for measuring anything. Quantitative metrics need ~40, eyetracking ~39, card sorts ~15, tree tests 30–50, and divergent user groups need 3–4 participants per segment rather than 5 total.

Does a bigger sample size fix a biased sample?

No. Sample size controls precision, not bias — a large biased sample is precisely wrong at scale. Composition problems like self-selection and survivorship bias are handled separately from sizing, and both checks are needed before trusting a finding.