aer-preregistration

Solid

Use when the project collects primary data or runs a field, lab, or survey experiment, before the intervention begins — write the pre-analysis plan, size the sample from a power calculation, and register with the AEA RCT Registry. Apply after the design is chosen in aer-identification and before any outcome data are seen.

Code & Development 34 stars 6 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
51
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# AER Pre-Registration ## Overview For experimental and prospective-data AER-track work, credibility is bought **before** the data exist. This skill writes the pre-analysis plan (PAP), sizes the sample from a power calculation, and registers the study. Its job is to make the eventual results un-p-hackable: a referee who sees a public PAP timestamp predating data collection cannot accuse you of specification search. Registration is not optional at AEA journals for RCTs. If the design is observational, skip to `aer-robustness`; there is nothing to pre-register. ## When to Use - The paper runs a randomized controlled trial (field, lab, or survey experiment) - The project collects primary data whose analysis should be pre-committed - A referee or editor asks for the trial registration number or the PAP - Reviewers suspect the reported specification was chosen after seeing outcomes - You must justify the sample size, or explain why an effect was "not detected" ## Register-or-Not Decision ``` Is treatment assigned by the researcher (randomization)? ├── Yes → register with the AEA RCT Registry BEFORE the intervention; write a PAP ├── No, but you collect new primary data → post a PAP for the pre-committed analysis └── No, secondary/observational data already realized → do NOT pre-register (a PAP written after the outcomes exist is theater); go to aer-robustness ``` ## Pre-Analysis Plan Contents Pre-specify, in order, and timestamp before unblinding: 1. **Hypotheses** ...

Details

Author
brycewang-stanford
Repository
brycewang-stanford/AER-Skills
Created
2 months ago
Last Updated
1 weeks ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

preregister

Draft a registry-ready preregistration or preanalysis plan (AsPredicted, OSF, or AEA RCT Registry) from a study spec or a free-form description, with MUST/SHOULD/MAY flags on every field, [CLARIFY:] placeholders instead of invented content, a stated target N with power basis and stopping rule, and an explicit falsification criterion. TRIGGER on "preregister", "draft a preregistration", "AsPredicted form", "OSF prereg", "AEA RCT registry", "PAP", "preanalysis plan", or before launching a vignette, conjoint, eye-tracking, MTurk/Prolific, or field experiment. Refuses to write a preregistration for analyses already run on data already seen. Writes Markdown for pasting into the web forms, .tex on request.

5 Updated today
ericluo04
Code & Development Listed

pre-register-trial

Run BEFORE any new signal, strategy, factor, overlay, or hypothesis starts accruing data or gets evaluated. Creates the tamper-evident commitment (hypothesis + primary metric + decision rule + earliest decision date) in docs/TRIALS/ and the experiment registry. If it isn't pre-registered, it didn't happen (CANON §6).

1 Updated today
Murathanx12
Code & Development Solid

aer-identification

Use when selecting, implementing, or stress-testing the causal identification strategy for an empirical economics manuscript — difference-in-differences (including staggered designs), instrumental variables (including weak-IV-robust inference), regression discontinuity, synthetic control, or shift-share / Bartik. Apply before writing the introduction or results.

34 Updated 1 weeks ago
brycewang-stanford