Agent skill · Data & Analytics

restud-replication-package

Use when assembling the data and code deposit for an accepted empirical The Review of Economic Studies (REStud) manuscript, writing the README, or auditing reproducibility before the journal's Data Editor runs the pre-publication reproducibility check. Builds a deposit-ready package; does not run the analysis. Verify the current REStud/OUP data policy on the official page.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill restud-replication-package --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Review-of-Economic-Studies-Skills/skills/restud-replication-package/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# REStud Replication Package (restud-replication-package) ## When to trigger - A conditional acceptance arrived and the Data Editor's reproducibility check is coming - Drafting the README at any point (recommended: from day one of the project) - Auditing reproducibility before submitting the deposit - A prior deposit was returned for incomplete provenance or non-running code ## REStud's actual data & code availability policy REStud has a **Data Editor** (Miklós Koren; verified 2026-05-30) and follows the **AEA Data and Code Availability Standard (DCAS)**, the same standard the AEA journals and Econometric Society use. Its defining feature, which differs from journals that merely "encourage sharing": the Data Editor runs a **reproducibility check on the data and code before the paper is published** — the code is actually executed to confirm it reproduces the reported results, and publication is conditional on passing. Accepted papers' replication packages are **deposited at Zenodo** (the journal's / Society's Zenodo community), where the package receives a DOI; you may reserve the DOI in advance and finalize after the check. **Exemptions exist for confidential / proprietary / restri

What's inside
Steps it walks through
  1. When to trigger
  2. REStud's actual data & code availability policy
  3. Repository structure
  4. README required sections
  5. Coding discipline (adopt from day one)
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the restud-replication-package skill do?

Use when assembling the data and code deposit for an accepted empirical The Review of Economic Studies (REStud) manuscript, writing the README, or auditing reproducibility before the journal's Data Editor runs the pre-publication reproducibility check. Builds a deposit-ready package; does not run the analysis. Verify the current REStud/OUP data policy on the official page.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill restud-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.

Keep going