eer-replication-package
Use when assembling the data and code deposit for a European Economic Review (EER) manuscript under Elsevier's mandatory replication policy. Builds a reproducible package and README; it does not run the analysis or write the paper.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eer-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 (eer-replication-package) ## When to trigger - The paper contains empirical work, simulations, or experiments - Results are stabilizing and the deposit should be assembled (not at the last minute) - Preparing for acceptance, when the replication materials must be provided - A referee or editor asks about data/code availability ## The EER replication bar EER operates a **mandatory replication policy**: authors of accepted papers with empirical, simulation, or experimental content must provide, **prior to publication**, the **data, programs, and computational details sufficient to permit replication** of the reported results (检索于 2026-06；以官网为准). Elsevier's data-and-code availability framework applies; deposits typically go to a repository (e.g., **Mendeley Data** / Zenodo) and are linked from the article. Re-confirm on the official EER policy page whether there is **pre-acceptance verification by a data editor**, the exact deposit location, and the handling of restricted data — do **not** assert a verification step or repository that the current policy does not state. Build the package **as you go** so the deposit is not a scramble at acceptance. ## What to asse
- When to trigger
- The EER replication bar
- What to assemble
- Data
- Code
- Documentation (README)
- Checklist
- Anti-patterns
- Worked vignette (illustrative)
- Output format
What does the eer-replication-package skill do?
Use when assembling the data and code deposit for a European Economic Review (EER) manuscript under Elsevier's mandatory replication policy. Builds a reproducible package and README; it does not run the analysis or write the paper.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eer-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.