ier-replication-package
Use when assembling the data/code deposit and proof appendix for an International Economic Review (IER) manuscript under its AER-style data availability policy. Covers the deposit, README, data availability statement, and self-contained proofs; it does not write the analysis code.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ier-replication-package --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Replication Package and Proof Appendix (ier-replication-package) ## When to trigger - The paper has empirical, simulation, or experimental work and acceptance will hinge on a compliant deposit - You are at conditional acceptance and the letter asks for data, programs, and a README - Key proofs are scattered in the body, in footnotes, or assumed — and the appendix is not self-contained - A referee questions whether the results can be reproduced from what you provide - You need to know exactly what IER's data policy requires vs. what is optional ## IER's policy, precisely IER **adopted the American Economic Review (AER) data availability policy effective January 1, 2022** (检索于 2026-06；以官网为准). The operative facts: - It is journal policy to publish a paper only if its data are **clearly documented and readily available to any researcher for replication**. - On **conditional acceptance**, authors deposit data, programs, and enough detail to permit replication in **electronic form at a standard public repository** the acceptance letter names, and include a **data availability statement with a link to the repository** in the final paper. - If data are **proprietary** or the requirement
- When to trigger
- IER's policy, precisely
- What the deposit must contain, by paper type
- The proof appendix (the theory/structural obligation)
- Why the deposit is also a mid-review asset
- Worked example (illustrative)
- The proprietary-data trap (flag it at submission, not acceptance)
- README discipline that actually permits replication
- Checklist
- Anti-patterns
- Output format
What does the ier-replication-package skill do?
Use when assembling the data/code deposit and proof appendix for an International Economic Review (IER) manuscript under its AER-style data availability policy. Covers the deposit, README, data availability statement, and self-contained proofs; it does not write the analysis code.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ier-replication-package --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.