← ClaudeAtlas

aer-replicationlisted

Use when assembling the AEA Data and Code Availability deposit for an AER, AER:Insights, or AEJ acceptance, writing the README, or auditing a replication package before the AEA Data Editor review. Implements the current AEA policy, including the February 2026 Data and Code Availability Policy.
brycewang-stanford/AER-skills · ★ 0 · Code & Development · score 72
Install: claude install-skill brycewang-stanford/AER-skills
# AER Replication ## Overview Prior to acceptance, every empirical, simulation, or experimental paper submitted to an AEA journal must provide data, code, and a complete README sufficient for an independent researcher to reproduce every reported result. The AEA Data Editor's Office now performs a **computational reproducibility check** before final acceptance, and a failed check delays publication by weeks or months. This skill produces an AEA-compliant deposit on the first try. ## When to Use - A conditional acceptance arrived and the deposit deadline is set - Drafting the README at any point in the project (recommended: from day one) - An AEA Data Editor report flagged the deposit - Preparing a deposit for openICPSR ## Current AEA Data and Code Availability Policy (February 2026) Three pillars: 1. **Data deposit** — all data the paper uses, or full provenance documentation for data that cannot be public 2. **Code deposit** — all code that produces every reported number, table, and figure 3. **README** — a single document instructing a replicator on how to run everything Materials must be deposited in an **openly accessible trusted repository**. The strongly encouraged repository is the **AEA Data and Code Repository at openICPSR**, which gives the Data Editor automatic access to draft deposits. ### Forms Required - **Data and Code Information Form** - **Data and Code Availability Form** (signed) - **Data and Code Archive Agreement Form** (signed) These forms are