Agent skill · Data & Analytics

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.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
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.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Journal-of-Monetary-Economics-Skills/skills/jme-replication-and-data-policy/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

# 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

What's inside
Steps it walks through
  1. When to trigger
  2. What JME's policy actually is
  3. What to deposit
  4. What monetary-macro referees actually re-run
  5. Checklist
  6. Anti-patterns
  7. Reproducibility pass for Journal of Monetary Economics
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
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.

Keep going