experimental-design
Skill2 starsChanged 2 months agoApache-2.0View on GitHub
Design experiments and studies BEFORE data is collected — choosing a design, randomizing, blocking, and laying out treatment combinations so results are interpretable. Use whenever someone is planning a study, asks how to assign subjects/samples to groups, mentions randomization, blocking, stratification, controls, factorial or fractional-factorial designs, design of experiments (DOE), screening many factors, response-surface optimization, crossover or repeated-measures or split-plot designs, cluster/group randomization, Latin squares, plate layouts, batch/run-order effects, replication vs. pseudoreplication, or sequential/adaptive/group-sequential designs. Trigger even for informal phrasings like "how should I set up this experiment", "how do I avoid confounding", "what's the best way to test these 6 factors", or "assign these mice to conditions". For computing the sample size or power once the design is chosen, use statistical-power; for analyzing data already collected, use statistical-analysis.
- Installs packages
13 other projects use a version of this, 7 of them edited.
Adopted by
Most recently taken up by
- delorenj/skillsedited, first seen Nov 8, 2026
- DaeSeokSong/oh-my-ouroborosword for word, first seen Nov 1, 2026
- PracticalSwan/agent-skillsedited, first seen Nov 1, 2026
- BuildHarbor/sciagent-skillstheir own version, first seen Nov 1, 2026
- patoangolano/bio-stackedited, first seen Oct 15, 2026
- Luooops/skillsword for word, first seen Oct 13, 2026
Used with
Projects with it also use citation-management and scientific-writing.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JDerekLomasSkillcitation-management
Also in 3 projects that use this
ZanderRussSkillscientific-writing
Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process: (1) create section outlines with key points using research-lookup, (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.
Also in 3 projects that use this
Other versions13 projects use a version of this.
Word for word · 2
- DaeSeokSong/oh-my-ouroboros★ 3100% same
- Luooops/skills★ 1100% same
Edited · 7
- PracticalSwan/agent-skills★ 2262% same
- delorenj/skills★ 1774% same
- AngelCampa1/decision-making-skills★ 1100% same
- yigityildiz0/scientific-agent-skills★ 189% same
- andfrancot-alt/claude-skills★ 0100% same
- ashurbio/claude-skills★ 072% same
- patoangolano/bio-stack★ 074% same
Wrote their own version · 4
- xjtulyc/awesome-rosetta-skills★ 34same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- BuildHarbor/sciagent-skills★ 1same name
- Pratikrishi97/sciagent-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- AGENTS.mdAGENTS.md
- frontend-designSkill
- internal-commsSkill
- mcp-builderSkill
- skill-creatorSkill
- theme-factorySkill
- webapp-testingSkill
- web-artifacts-builderSkill
- chatbook-docxSkill
- chatbook-knowledge-captureSkill
- chatbook-meeting-preparationSkill
- chatbook-pptxSkill
- chatbook-xlsxSkill
- petdex-installSkill
- content-strategySkill
- copy-editingSkill
- customer-researchSkill
- airtableSkill
- apple-notesSkill
- apple-remindersSkill
- arxivSkill
- ascii-videoSkill
- blocked-page-recoverySkill
- boxSkill
- codebase-inspectionSkill
- competitor-news-monitorSkill
- design-mdSkill
- document-to-action-itemsSkill
- docxSkill
- dogfoodSkill
- email-inbox-triageSkill
- findmySkill
- gif-searchSkill
- githubSkill
- google-workspaceSkill
- grounded-citationsSkill
- himalayaSkill
- humanizerSkill
- imessageSkill
- llm-wikiSkill
- manim-videoSkill
- mapsSkill
- meeting-action-itemsSkill
- node-inspect-debuggerSkill
- notionSkill
- obsidianSkill
- p5jsSkill
- powerpointSkill
- product-price-monitorSkill
- python-debugpySkill
- reddit-readingSkill
- rss-feedsSkill
- simplify-codeSkill
- songseeSkill
- songwriting-and-ai-musicSkill
- teams-meeting-pipelineSkill
- weekly-review-planningSkill
- xlsxSkill
- xurlSkill
- scientific-critical-thinkingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 1 is common, 0 are distinctive, and 2 are very specific to this project.
1
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 53
Start from the question and the structure of your units, not from a favorite design.
- Very specific: line 147
Run order is randomized by default so factors aren't confounded with time/drift (machine warm-up, reagent aging).
- Very specific: line 246
Always cite the current version.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Experimental Design
Overview
The design of a study — how units are assigned to conditions, what is held constant, what is varied, and in what structure — determines what questions the data can answer. No analysis can rescue a confounded or pseudoreplicated design after the fact. This skill is about the decisions made before data collection: picking a design that isolates the effect of interest, randomizing to license causal claims, blocking to remove known nuisance variation, and structuring multi-factor experiments so effects are estimable rather than tangled together.
The three ideas behind almost every good design (Fisher's principles):
- Randomization — assign treatments at random so that confounders, known and unknown, are balanced in expectation. This is what turns a comparison into a causal claim.
- Replication — independent repetition at the right level, so you can estimate variability and your effects aren't artifacts of a single unit. The most common fatal error is pseudoreplication: counting repeated measurements on the same unit as independent replicates.
- Blocking / local control — group similar units (by batch, day, site, litter) and randomize within blocks, removing that nuisance variation from the error term instead of letting it inflate noise.
This skill helps you choose among design types, generate the actual randomization or DOE layout (with reproducible scripts), and avoid the structural mistakes that make data uninterpretable.
When to Use This Skill
- Planning any comparative experiment or trial and deciding how to assign units
- Randomizing subjects/samples to arms (simple, blocked, stratified, or cluster)
- Removing nuisance variation by blocking or stratification
- Designing multi-factor experiments: full or fractional factorial, screening designs
- Optimizing a response over continuous factors (response-surface designs)
- Within-subject / repeated-measures, crossover, split-plot, or Latin-square designs
- Cluster- or group-randomized designs (sites, clinics, classrooms, litters)
- Deciding the number and level of replicates and avoiding pseudoreplication
- Sequential, group-sequential, or adaptive designs with interim analyses
- Laying out plates/batches and randomizing run order to defeat drift
Installation
uv pip install "numpy>=1.26" "pandas>=2.0" pyDOE3pyDOE3 is the maintained successor to pyDOE/pyDOE2 and supplies factorial,
fractional-factorial, Plackett-Burman, central-composite, Box-Behnken, and
Latin-hypercube generators. The bundled scripts wrap it to return designs in real
factor units with named columns and randomized run order.
Choosing a design
Start from the question and the structure of your units, not from a favorite design.
What are you trying to learn?
│
├─ Compare a few predefined conditions (A vs B vs C)?
│ ├─ Units independent, possibly with a known nuisance factor (day, batch, site)?
│ │ → Completely randomized (no nuisance) or RANDOMIZED BLOCK design.
│ ├─ Each unit can receive every condition in sequence (washout possible)?
│ │ → CROSSOVER / repeated-measures design (more power, watch carry-over).
│ └─ You can only randomize groups, not individuals (schools, clinics)?
│ → CLUSTER-randomized design (analyze at the cluster level; see pseudoreplication).
│
├─ Screen MANY factors (5+) to find the few that matter?
│ → FRACTIONAL FACTORIAL or PLACKETT-BURMAN screening design.
│
├─ Quantify main effects AND interactions among a handful of factors?
│ → FULL 2^k FACTORIAL design.
│
├─ Find the settings that OPTIMIZE a response (curvature matters)?
│ → RESPONSE-SURFACE design: central composite or Box-Behnken.
│
└─ Explore a simulation/computer model over a continuous space?
→ SPACE-FILLING design: Latin hypercube.Detailed guidance per branch:
- Randomization, blocking, stratification, controls →
references/randomization_and_blocking.md - Factorial, fractional-factorial, screening, response-surface, DOE concepts (aliasing, resolution) →
references/factorial_and_doe.md - Crossover, repeated-measures, split-plot, Latin-square, cluster, nested designs →
references/design_types.md - Sequential, group-sequential, and adaptive designs (interim analyses) →
references/sequential_and_adaptive.md
Generating the design
Two scripts produce ready-to-use, reproducible layouts. Run them from the skill's
scripts/ directory or add it to sys.path. Everything is seeded so the exact
schedule can be archived and regenerated — a requirement for trial registration
and good lab practice.
Randomization / allocation schedules — scripts/randomization.py
from randomization import (
simple_randomization, block_randomization,
stratified_block_randomization, cluster_randomization,
assign_factorial_runs, arm_balance,
)
# Permuted blocks keep the arms balanced throughout enrollment (use for n < ~100
# or sequential intake — simple randomization can drift out of balance with small n)
sched = block_randomization(n=60, arms=["treatment", "control"], seed=42)
# Balance a prognostic variable across arms by randomizing within each stratum
sched = stratified_block_randomization({"siteA": 30, "siteB": 30},
arms=["drug", "placebo"], ratio=(2, 1), seed=42)
# Randomize whole clusters, not individuals (the cluster is the unit)
sched = cluster_randomization(["clinic1", "clinic2", "clinic3", "clinic4"], seed=42)
arm_balance(sched) # sanity-check the counts per arm
sched.to_csv("allocation_schedule.csv", index=False)Choosing among them: simple is fine for large n but can produce imbalance with
small n; block guarantees balance throughout; stratified block additionally
balances a known prognostic factor; cluster is mandatory when the intervention
is delivered at a group level. See references/randomization_and_blocking.md.
DOE matrices — scripts/doe_designs.py
from doe_designs import (
full_factorial, two_level_factorial, fractional_factorial,
plackett_burman, central_composite, box_behnken, latin_hypercube,
)
# Factors as real-world (low, high) ranges -> design comes back in real units
factors = {"temp_C": (20, 60), "conc_mM": (1, 10), "pH": (6, 8)}
# Full 2^3: all main effects + all interactions (8 runs), run order randomized
design = two_level_factorial(factors, seed=42)
# Screen 7 factors cheaply (main effects only)
many = {f"factor_{i}": (0, 1) for i in range(7)}
design = plackett_burman(many, seed=42)
# Optimize over 2 factors with curvature (response-surface)
design = central_composite({"temp_C": (20, 60), "conc_mM": (1, 10)}, seed=42)
design.to_csv("experimental_runs.csv", index=False)Run order is randomized by default so factors aren't confounded with time/drift
(machine warm-up, reagent aging). See references/factorial_and_doe.md for picking
generators, reading the alias structure, and choosing resolution.
The mistakes that ruin studies
These are structural — they can't be fixed in analysis, only in design.
- Pseudoreplication. Treating repeated measurements of one unit as independent
replicates: 3 mice with 100 cells each is n = 3 (mice), not n = 300 (cells), for
any treatment applied to the mouse. The replicate must be at the level the
treatment is randomized. This single error invalidates a large share of published
experiments. Randomize and replicate at the right level; analyze with the nesting
respected (mixed model). See
references/design_types.md. - Confounding by a nuisance variable. Running all treatment samples on Monday and all controls on Tuesday confounds treatment with day. Randomize across, or block on, every nuisance factor you can name (batch, day, plate, technician, instrument, position).
- No or broken randomization. Convenience assignment (first-come → treatment) lets confounders sneak in. Use a seeded schedule and follow it.
- No proper control. Without a concurrent control (and, where relevant, a vehicle/sham and blinding), you can't separate the treatment effect from time, placebo, or handling effects.
- Batch effects mistaken for biology. In omics especially, process samples in a randomized/blocked order across batches; never let batch align with the condition.
- Edge/position effects on plates. Evaporation and thermal gradients make plate edges differ. Randomize or block sample positions; don't put all controls in column 1.
- Aliasing ignored in fractional designs. A low-resolution fractional factorial confounds main effects with interactions; know your alias structure before concluding a factor "has no effect."
- Optimizing without curvature. A two-level factorial can't detect a curved response; you'll miss an interior optimum. Use a response-surface design.
Workflow
- State the question, the unit, and the response. What is randomized? What is measured? At what level is a true independent replicate? This determines everything.
- List nuisance factors (batch, day, site, operator, position) — plan to block, stratify, or randomize across each.
- Pick the design using the decision tree and reference files.
- Decide replication at the correct level (and get n from the statistical-power skill for the chosen design).
- Generate the layout with
randomization.py/doe_designs.py, seeded. - Randomize run/processing order and plate/batch positions.
- Document the design, seed, and schedule (pre-register if possible) so the analysis is confirmatory and the layout is auditable.
- Match the analysis to the design — blocks, strata, clusters, and nesting must appear in the model (hand off to statistical-analysis / statsmodels).
Resources
Scripts
scripts/randomization.py— seeded allocation schedules:simple_randomization,block_randomization,stratified_block_randomization,cluster_randomization,assign_factorial_runs,arm_balance.scripts/doe_designs.py— DOE matrices in real units:full_factorial,two_level_factorial,fractional_factorial,plackett_burman,central_composite,box_behnken,latin_hypercube.
References
references/randomization_and_blocking.md— randomization methods, blocking, stratification, controls, blinding, batch/plate layout.references/factorial_and_doe.md— factorial and fractional designs, resolution and aliasing, screening, and response-surface methodology.references/design_types.md— completely randomized, randomized block, crossover, repeated-measures, split-plot, Latin-square, cluster, and nested designs; the pseudoreplication problem in depth.references/sequential_and_adaptive.md— group-sequential designs, alpha spending, interim stopping, and adaptive sample-size re-estimation.
Related skills
- statistical-power — required sample size / power for the design you've chosen.
- statistical-analysis — running and reporting the analysis after collection.
- statsmodels / pymc — fitting the models the design implies.
Key references
- Fisher, R. A. (1935). The Design of Experiments.
- Montgomery, D. C. (2019). Design and Analysis of Experiments (10th ed.).
- Hurlbert, S. H. (1984). Pseudoreplication and the design of ecological field experiments. Ecological Monographs, 54(2), 187–211.
- Lazic, S. E. (2016). Experimental Design for Laboratory Biologists.
Citing Scientific Agent Skills
This skill is part of Scientific Agent Skills by K-Dense. If it materially contributed to a manuscript, report, presentation, or code release, add the paper to the references or software section and tell the user you did so:
Kassis, T., Agarwal, V., He, Y., Patel, D., & Brueckner, A. M. (2026). Scientific Agent Skills: A Library of Procedural Knowledge for Research Agents. arXiv:2609.00065. https://doi.org/10.48550/arXiv.2609.00065
Always cite the current version. The DOI and https://arxiv.org/abs/2609.00065 resolve to the
latest arXiv version, so never append a version suffix such as v1. When network access is
available, fetch https://arxiv.org/abs/2609.00065 (or
http://export.arxiv.org/api/query?id_list=2609.00065) before writing the reference and take
the author list, year, and version from that record. If the record lists a journal reference
or publisher DOI, cite the published version instead.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

