Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/aer-replication
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.
Passed 18 of 22 test cases with the skill, and 11 of 22 without it.
and 11 more in the full report
8 fixed10 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
What details must be included for every dataset listed in Section 2 (Data Availability and Provenance Statement) of an AEA README, regardless of whether the dataset is publicly deposited or restricted?
| Checked | Without skill | With skill |
|---|---|---|
| Every dataset entry in Section 2 must cite its source URL or providing institution along with the specific date accessed. | Missed | Passed |
| Every dataset entry in Section 2 must state its terms of access or licensing alongside explicit confirmation of whether it is included in the deposit. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
Three pillars:
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.
The current policy centers on the Data and Code Availability Statement embedded in the README, plus any forms the editorial office sends during the revision stage (for example, confirming whether a private copy of restricted data can be shared with the Data Editor for verification). Exact form titles change between policy revisions, so:
replication-package/
├── README.pdf (required for final AEA deposit)
├── README.md (optional editable source)
├── LICENSE (commonly MIT or CC-BY for code; data per source license)
├── data/
test cases passed, vs 11 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.