jme-replication-and-data-policy
Use when assembling the supplementary-materials / replication deposit for a Journal of Monetary Economics (JME) manuscript — depositing data, code (Dynare/MATLAB/Stata/R), and appendices on ScienceDirect / Mendeley Data per JME's supplemental-materials policy, plus the Elsevier generative-AI declaration.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jme-replication-and-data-policy --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 & Data Policy (jme-replication-and-data-policy) ## When to trigger - The paper is empirical/quantitative and you must prepare a deposit - An editor has asked for supplemental materials as a condition of publication - You want to pre-empt referee replication concerns - You need to know exactly what JME's data policy does and does not require ## What JME's policy actually is JME maintains a **supplementary-materials / replication policy** rather than a one-size mandatory verification gate. Precisely: - An **editor may require provision of supplemental materials — proofs, data sets, and computational programs — as a condition of publication.** - Authors are **strongly advised to deposit appendices, computer programs, and data files on ScienceDirect** (and **Mendeley Data** is supported) to **enhance replication of and citation to the research.** - Authors must include the **declaration of any use of generative AI** in manuscript preparation, per Elsevier policy. Note what is **待核实**: a separately *enforced*, AEA/Econometrica-style **mandatory pre-publication data-and-code-availability verification** workflow could **not** be confirmed from an official JME page. The confi
- When to trigger
- What JME's policy actually is
- What to deposit
- What monetary-macro referees actually re-run
- Checklist
- Anti-patterns
- Reproducibility pass for Journal of Monetary Economics
- Output format
What does the jme-replication-and-data-policy skill do?
Use when assembling the supplementary-materials / replication deposit for a Journal of Monetary Economics (JME) manuscript — depositing data, code (Dynare/MATLAB/Stata/R), and appendices on ScienceDirect / Mendeley Data per JME's supplemental-materials policy, plus the Elsevier generative-AI declaration.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jme-replication-and-data-policy --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.