Use when assembling the data and code deposit for an AEJ: Economic Policy manuscript to satisfy the AEA Data and Code Availability Policy and the AEA Data Editor's pre-publication reproducibility check. Builds the openICPSR deposit, README, and restricted-data access paths; it does not run the analysis or write the paper.
SkillScore100Maintained
Automatic
◆Research pack
Last verified 8/15/2026
What it changes
Passed 22 of 22 test cases with the skill, and 20 of 22 without it.
Without skill91%
With skill100%
Checks it passed that the model alone missed
Instructs submitting the package to the AEA Data Editor
States that code must generate all reported in-text numerical claims
2 fixed20 passed either way0 still failing0 broke
Pass-rate lift
+9 pp
Tokens
+28%
Agent turns
0%
Response time
-37%
Model gemini-3.6-flashMeasured 8/15/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
I am finalizing our replication materials for an AEJ: Policy submission after receiving an R&R. We have a master run file, pinned Stata ado files, and synthetic extracts for our confidential hospital records. Could you audit our package against the AEA reproducibility standards and return a structured report detailing: data availability classifications, master script capability, README section completeness (software, runtime, file mapping), version/seed locks, restricted dataset instructions, repository target, and follow-up actions?
What was checked, without and with the skill
Checked
Without skill
With skill
Requires specifying exact software version numbers in the README
Passed
Passed
Requires setting explicit random seeds for stochastic procedures
Passed
Passed
Instructs submitting the package to the AEA Data Editor
Missed
Passed
case-02 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md73 linessingle file
Replication Package — AEA Data Editor Compliance (aejpol-replication-package)
When to trigger
A conditional acceptance / R&R asks for the data and code deposit
You want to build the replication package as you go (recommended — the check is before publication)
Some data are proprietary or restricted and you need a compliant access path
The AEA Data Editor returned the package with required changes
The AEA reproducibility regime (检索于 2026-06；以官网为准)
AEJ: Policy is an AEA journal and follows the AEA Data and Code Availability Policy. For accepted papers, authors deposit data, code, and documentation in the AEA Data and Code Repository at openICPSR, and the AEA Data Editor (Lars Vilhuber) runs a reproducibility check before the paper is published, not after. A Data and Code Availability Statement is required. Build the deposit to pass on the first pass.
What the deposit must contain
All code that produces every table, figure, and in-text number, organized so a single master script (run_all) regenerates the results from the analysis data.
Data that can be shared, in the repository; for data that cannot, the exact provenance and access instructions (see restricted-data path below).
A README following the AEA Data Editor's template: data sources and citations, data-availability statement, computational requirements (software + versions + packages), runtime, the map from code files to exhibits, and instructions to reproduce.
Dependencies pinned: Stata .ado versions, R renv.lock, Python requirements.txt/conda env; seeds set and reported for any simulation/bootstrap/randomization inference.
Restricted / proprietary data path
State the Data Availability Statement clearly: which data are public, which are restricted, and how a replicator obtains the restricted parts (provider, application process, cost, approximate wait).
Provide everything that can be shared (cleaning and analysis code, derived public extracts, synthetic or example data) so the Data Editor can verify the pipeline even without the raw restricted file.
Confirm the access path is real and current — the Data Editor verifies it.
Note any partial-reproducibility scope (e.g., one table from confidential data) in the README.
Code posting during review
Review is single-blind, so the submission need not be anonymized; the openICPSR deposit is prepared at acceptance. Posting a working-paper code repository earlier is fine and does not conflict with the review process.
Checklist
Data and Code Availability Statement drafted (public vs. restricted, sources cited)
One master script regenerates every exhibit and in-text number from analysis data
README follows the AEA Data Editor template (sources, requirements, runtime, code→exhibit map)
Software, package, and .ado versions pinned; seeds set and reported
Use when assembling the data and code deposit for an American Economic Review: Insights (AER: Insights) short-format manuscript to pass the AEA Data and Code Availability Policy and the AEA Data Editor's pre-publication reproducibility check. Builds the package and README; it does not run the analysis.